Integration Guide

Custom Integration

Run a custom stack? fast.site works with any framework, language or static site. Set your own caching rules.

Setup Steps

  1. 1

    Add your domain in fast.site

    Log in to your fast.site dashboard and add your domain (e.g. Example.com or app.example.com).

  2. 2

    Pick your platform (or Custom)

    fast.site tries to detect your stack. If it's something less common, just pick "Custom" on the platform step (or the closest match). We'll apply sensible defaults; you can refine the rules later in cache settings.

  3. 3

    Update your nameservers

    Change your domain's nameservers at your registrar to the two fast.site nameservers shown in your dashboard. Propagation usually takes a few minutes.

  4. 4

    Configure caching headers (optional)

    Set Cache-Control headers on your responses to control how long content is cached.

  5. Done!

    Your app now runs through fast.site. Cacheable responses serve from the edge globally.

Cache-Control Headers

Control caching behavior with standard Cache-Control headers:

Cache-Control: public, max-age=3600

Cache for 1 hour, serve to all users

Cache-Control: private, no-cache

Don't cache (for user-specific pages)

Cache-Control: public, max-age=31536000, immutable

Cache for 1 year (for versioned assets like app.v2.js)

What's cached by default

  • Static files: CSS, JavaScript, fonts, images
  • HTML pages with cacheable headers
  • API responses with cacheable headers

What's never cached

  • POST, PUT, DELETE requests
  • Requests with session cookies
  • Responses with Set-Cookie headers
  • Responses with Cache-Control: private or no-cache

Verify it's working

Check that caching is active by looking for fs-cache: HIT in your response headers.

Learn how to check if cache is working →