Compare
x402-hosting vs Netlify.
Netlify is an account-based hosting platform known for static sites, build pipelines, and a dashboard-driven workflow. x402-hosting is a prepaid Next.js hosting service built in Amsterdam: one command publishes your app as a Cloudflare Worker, hosting time is paid in USDC at $0.20 per project-day, and there is no account, dashboard, or subscription. Both get a site online; they differ in everything around that fact.
At a glance
- Netlify: sign-up, site dashboard, team accounts; x402-hosting: no account
- Netlify: plans and metered usage; x402-hosting: $0.20 per project-day prepaid in USDC
- Netlify: many frameworks and static hosting; x402-hosting: Next.js only, done deliberately
- Netlify: automation via API tokens; x402-hosting: automation via wallet payments, no tokens
- x402-hosting: the wallet that pays owns the project and can transfer it for $0.01
Accounts versus wallets
Netlify organizes work into accounts, sites, and teams, all reached through a login and a dashboard. That model fits organizations that want a shared control panel. x402-hosting removes the account layer entirely: the first $0.01 upload payment binds the paying wallet as project owner, and every later paid operation must settle from that wallet. There is no password to reset, no seat to manage, and no dashboard session to expire — ownership is cryptographic.
Subscriptions versus prepaid days
Netlify billing centers on plans with metered components such as build minutes and bandwidth, invoiced monthly. x402-hosting is prepaid: thirty days costs $6.01, a redeploy costs $0.01, and reads are free. Nothing renews automatically, so an abandoned project cannot surprise you — it expires, and a 30-day grace window lets you bring it back at the same URL. Every charge is quoted by an HTTP 402 payment challenge before any wallet signs, so the price list never hides a variable.
Built for agents
Netlify exposes an API authenticated with tokens, which means a stored secret per environment. On x402-hosting the payment is the credential: an agent holds a wallet, not a token, and operates the whole lifecycle — deploy, renew, rollback, transfer, delete — through one CLI or plain HTTP endpoints. Machine-readable entry points (/llms.txt, /openapi.json, ?mode=agent) let an agent learn the service on its own:
$ npx x402-hosting@latest deploy --days 30
Who should choose which
Choose Netlify if you run static sites across mixed frameworks and want a dashboard, form handling, and team features under one login. Choose x402-hosting if your project is a Next.js app, you want it online for a known prepaid price, and you prefer infrastructure that needs no account — for yourself or for an agent acting on your behalf. An active project includes static assets, 100,000 dynamic requests, and 15 million CPU milliseconds.