Use case

Hackathon hosting that outlives the weekend.

A hackathon project built as a supported Next.js app gets a real production URL with one command, during the event, in minutes. A week of hosting costs $1.41 — 7 × $0.20 plus a $0.01 upload — prepaid in USDC, with no account to create while the clock is running.

Deploy in minutes, during the event

From the project root, run:

$ npx x402-hosting@latest deploy --days 7

The CLI adds the OpenNext Cloudflare configuration, builds locally, and only then asks for payment through an HTTP 402 challenge. A build that fails locally costs nothing, which matters when the code is changing every ten minutes. On success, the project publishes as a Cloudflare Worker and the URL is ready for the demo.

Next.js project→local OpenNext build→Cloudflare Worker→production URL
One command moves a Next.js project from a local directory to a production URL.

What the project gets

  • Static assets, 100,000 dynamic requests, 15 million CPU ms
  • Route handlers for APIs and form submissions
  • Redeploys at the same URL for $0.01 during judging
  • Free status reads to check expiry without a login
  • Supported Next.js: 15.5.21 to below 16, or 16.2.11 and later

Let an agent deploy while you keep coding

The CLI is designed for machine use: the payment is an HTTP challenge a wallet settles, not a checkout form a human fills in. An agent can run the deploy command, sign the payment, and hand back the URL while you keep writing code or rehearsing the presentation. The documentation describes the agent-facing surfaces.

Renew only if the project has legs

Most hackathon projects should not outlive the weekend, and prepaid hosting matches that: when the seven days end, the project expires with nothing to cancel. If the project wins or finds users, npx x402-hosting@latest renew --days 30 extends it for $0.20 per day from the same wallet — and a 30-day grace window after expiry still republishes at the same URL. Exact numbers are on the pricing page.

The repo keeps the URL

The first deploy writes x402-hosting.json to the project root with the URL, project id, owner wallet, and expiry. Keep it in the repository: the demo link stays connected to the code, and any teammate with the owner wallet can redeploy or renew.

Related guides