Europe

Next.js hosting from Amsterdam.

x402-hosting is Next.js hosting from Amsterdam, the Netherlands: a hosting company built around prepaid simplicity rather than accounts and subscriptions. One command deploys a project, hosting costs $0.20 per project-day prepaid in USDC, and there is no account anywhere in the flow.

A hosting company based in Amsterdam

The company behind x402-hosting is based in Amsterdam. That matters less as geography and more as an engineering culture: Amsterdam has a long trading history built on simple, direct dealing — clear prices, clear terms, no ceremony. Prepaid hosting fits that tradition. You pay for a fixed number of project-days, the project runs, and when the time is up you either renew or let it expire. There is nothing else to negotiate, and ending the relationship requires no cancellation flow — you simply do not renew.

A narrow, well-defined service

The product reflects the same pragmatism. x402-hosting does one thing: it takes a supported Next.js project and puts it on a production URL. Supported versions are 15.5.21 up to (but not including) 16, and 16.2.11 and later. An active project includes its static assets, 100,000 dynamic requests, and 15 million CPU milliseconds. Every price is fixed and published on the pricing page.

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

Fixed prices, prepaid in USDC

  • Hosting: $0.20 per project-day, prepaid
  • Thirty days: $6.01 in total, including the $0.01 upload
  • Redeploy at the same URL: $0.01
  • Rollback, transfer, or delete: $0.01
  • Status and deployment-history reads: free

Payment settles in USDC over the x402 protocol. The HTTP 402 payment challenge is the authoritative quote before any wallet signs, and local builds run before payment, so a failed build costs nothing. After expiry, a 30-day grace window lets you renew and republish at the same URL; beyond that, the project is gone and starting over means a new URL.

Built for software agents from day one

The Amsterdam team designed the service so an agent can operate it end to end: a CLI with --json output, machine-readable entry points like /llms.txt and /openapi.json, and ownership bound to a wallet instead of an account. The about page describes how the product is shaped like an agent task. A successful first deploy writes x402-hosting.json to the project root with the URL, project id, owner wallet, and expiry — a public record, kept with the repository.

From Amsterdam, for everywhere

The company is Dutch; the service is global. Deployments publish as Cloudflare Workers on Cloudflare's worldwide network, so a project deployed from Amsterdam serves users wherever they are. What stays local is the way the business works: fixed prices, prepaid terms, and no accounts.

Related guides