Compare
x402-hosting vs Cloudflare Pages and Workers.
This comparison has a twist: x402-hosting runs on Cloudflare. Every deployment is built locally with OpenNext and published as a Cloudflare Worker, so the runtime is the same global network either way. The real question is whether you want to operate Cloudflare yourself — account, dashboard, wrangler configuration, Workers concepts — or have one prepaid command do it for you.
At a glance
- Cloudflare: a broad developer platform with accounts and a dashboard; x402-hosting: one CLI command, no account
- Cloudflare: you configure OpenNext and wrangler yourself; x402-hosting: the CLI configures them for you
- Cloudflare: platform billing on an account; x402-hosting: $0.20 per project-day prepaid in USDC
- Same runtime either way: your app ends up as a Cloudflare Worker
- x402-hosting: the paying wallet owns the project, with no platform login involved
Platform versus product
Cloudflare Pages and Workers are platform primitives: enormously capable, and yours to assemble. Deploying a Next.js app means creating an account, learning how Workers are configured, wiring up@opennextjs/cloudflare, and keeping build settings current as versions change. x402-hosting packages exactly that path into a product: the CLI detects your Next.js version, adds the OpenNext configuration and wrangler setup to your project, builds locally, and publishes. You get the same network without operating the platform.
Account billing versus prepaid payments
Cloudflare usage is billed to an account under a plan, which fits teams standardizing on one vendor for DNS, CDN, security, and compute. x402-hosting charges per operation in USDC over the x402 protocol: $0.20 per project-day, $0.01 per deployment, free status reads. Thirty days of hosting costs $6.01 in total, quoted by an HTTP 402 payment challenge before any wallet signs. There is no plan to pick and no invoice to reconcile — see the pricing page.
Who should choose which
Choose Cloudflare directly if you want the full platform surface — custom Worker setups, storage products, queues, DNS — and you are happy to configure and operate it under your own account. Choose x402-hosting if what you actually want is a production URL for a Next.js app: one command, a known price, an owner wallet instead of an account, and a lifecycle (renew, rollback, transfer, delete) simple enough for an agent to operate. An active project includes static assets, 100,000 dynamic requests, and 15 million CPU milliseconds.
$ npx x402-hosting@latest deploy --days 30