Spache

How to put your site in Spache

Start with a preview. You can check that Spache can render your site before changing where your public domain points.

1. Add your site

  1. Open Sites and choose Add site.
  2. Enter a name and the full URL where your app is currently hosted, including https://.
  3. Save the site. Keep your origin online; Spache needs to fetch it to render and refresh pages.

2. Open the preview

After saving, Spache gives the site a preview URL. Open it from your Sites list. The first visit may need to fetch and render the page; later visits can use the cached HTML.

  • Check the homepage and a few important deep links.
  • Try the interactions that matter, including pages that load data from your APIs.
  • Review the site Overview, Routes, and route details for render results or errors.

Your existing origin and its DNS are unchanged while you use the preview URL.

3. Add your public domain

When the preview looks right, open the site’s Settings → Domains. Add the hostname visitors should use, such as www.example.com. Enter only the hostname—no protocol, path, or trailing slash.

Connecting a public domain may require an active paid plan. The app will show the account requirement before provisioning.

4. Verify DNS and wait for HTTPS

  1. Copy the DNS verification record Spache provides into your DNS provider. It is usually an _acme-challenge CNAME.
  2. Leave the existing traffic record in place for now. Wait for Spache to confirm the verification record and issue the HTTPS certificate.
  3. Use Refresh certificate status in Domains if you have added the record but the status has not updated yet.

5. Point traffic to Spache

Only after the certificate is active, replace the hostname’s existing A record with the Spache edge IP shown in Domains. Keep the _acme-challenge CNAME in place.

Visit the hostname over HTTPS, then use Test domain in the Domains section. The site Overview also reports whether Spache has received traffic for the connected domain.

What happens after cutover?

Visitors keep using your domain. Spache receives the request, serves a prepared page when it has a valid cached render, and fetches from your origin when needed. Your app bundle still runs in the visitor’s browser; Spache prepares and serves the rendered HTML so useful content can arrive earlier and be read by crawlers.

Learn more about how Spache works or configure cache invalidation after deployments.