How 2nth ships
to the edge

Pages and Workers are two generations of the same idea: put your site on Cloudflare's network. Pages came first as a static-site host with bolt-on functions. Workers is the general compute platform — and since it learned to serve static assets natively, it does everything Pages does, plus everything Pages can't (Durable Objects, cron triggers, queues, real observability).

Cloudflare has effectively frozen Pages. New platform features land on Workers only, and the docs point anyone hosting many sites at Workers.

Every new project follows one path. Repo in the 2nth-ai GitHub org, config pinned to the 2nth Cloudflare account, built by Workers Builds on every push.

Escape hatch: npm run deploy ships from a laptop through the same config — useful for a first deploy or an emergency, and exactly what the pinned account_id makes safe.

The whole deployment is one config file and one small Worker. This is the entire wrangler.jsonc:

{
  "name": "deploy-2nth",                // = repo name = project name, always
  "account_id": "aa0c1ccd…129e39",   // pinned: the 2nth account, never imbila
  "main": "src/index.ts",             // the code half (optional for pure-static)
  "compatibility_date": "2026-07-19",
  "compatibility_flags": ["nodejs_compat"],
  "assets": { "directory": "public" }, // the static half — this replaces Pages
  "observability": { "enabled": true }  // logs on by default, always
}

And the Worker that answered the hero strip — requests for real files never reach it; only unmatched routes like /api/edge fall through:

export default {
  async fetch(request) {
    const url = new URL(request.url);
    if (url.pathname === "/api/edge") {
      return Response.json({
        colo: request.cf?.colo,      // which datacentre answered
        city: request.cf?.city,
        servedAt: new Date().toISOString(),
      });
    }
    return Response.json({ error: "No such route" }, { status: 404 });
  },
} satisfies ExportedHandler<Env>;

Other traps for the migration file: Workers custom domains need the zone in the same account (wait for the cutover) · zone subscriptions like the old Pro plan don't move with a zone · D1/KV/R2 never crosses accounts — export and re-import, or leave the project where its data lives.