A Cloudflare Pages alternative that is one product, not a platform

Moving a site from Cloudflare Pages

What your configuration maps to, what has no equivalent at all, and the order to do it in. The middle one is the part that decides whether this is an afternoon.

What maps to what

What has no equivalent

Handle these before you move DNS, not after. Pages serves files: it has an SPA fallback, custom error pages and an exclude list, and it has no redirect table and no custom response headers.

• _redirects beyond the SPA line, and _headers. Cloudflare Pages supports both properly; we support neither. This is the most likely thing to break on this particular move, so read your files before you start.
• functions/ and _routes.json. Pages Functions are Workers. There is no runtime here for them to become.
• Everything else in the account. Access policies, Workers bindings, D1, R2, KV. If the site depends on any of them, it is not a static site being hosted — it is an application, and it should stay.

The order to do it in

1. STEP 01

   Read _redirects and _headers line by line

   Start here, because this is the step that decides whether the move works at all. Cloudflare Pages supports both files properly and we support neither — only the catch-all SPA line has an equivalent. Anything else needs somewhere to go before you continue.

2. STEP 02

   Check for functions/ and _routes.json

   Pages Functions are Workers. There is no runtime here for them to become, so if either is doing real work, the site is an application rather than a static site and it belongs where the runtime is.

3. STEP 03

   Create the site and a CI token

   A site has to exist before anything can deploy to it — the action will not create one, so a typo fails instead of quietly publishing to a new address. Do both from the dashboard if you prefer.
   once

   $ one9x pages create mysite
   ✓ created mysite → https://mysite.one9x.app/
   $ one9x tokens create "github actions"
   one9x_tok_7Kd…  (shown once)

4. STEP 04

   Deploy the build output

   Same output directory your Pages project builds. Add --spa if _redirects had the catch-all line. Nothing on your live site moves — this stages.
   first deploy

   $ one9x pages release ./dist --site mysite --spa
   ✓ v1 staged → https://v1--mysite.one9x.app/

5. STEP 05

   Swap the deploy step in CI

   If your Pages project builds from the Git integration, you are writing your first workflow and GitHub Actions has it in full. If you already deploy with Wrangler from Actions, it is the same workflow with one step swapped.
   before

   - uses: cloudflare/wrangler-action@v3
     with:
       apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
       accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
       command: pages deploy dist --project-name=mysite

   after

   - uses: one9x/pages-deploy@v1
     with:
       site: mysite
       dir: dist
       token: ${{ secrets.ONE9X_TOKEN }}
       deploy: ${{ github.ref == 'refs/heads/main' }}
       comment: true

6. STEP 06

   Repoint the domain — DNS-only, not proxied

   If you keep Cloudflare for DNS, set the record to DNS-only (grey cloud) rather than proxied. Proxied, the certificate challenge cannot reach us and issuance silently never completes. Lower the TTL a day ahead as usual.

7. STEP 07

   Delete the Pages project

   Once traffic has moved, so two builds are not racing to serve the same name, and remove _redirects, _headers and _routes.json from the repo in the same commit.

Your live site on Cloudflare Pages keeps serving throughout — nothing here touches it until you move DNS, and the free plan is enough to do the whole rehearsal first.