Prepaid and capped. No surprise bills.
A tier is a prepaid lease: you pay up front for a fixed window and fixed, pooled limits, and when a limit is reached the platform refuses the write rather than billing you for it. A hobby or team organization that outgrows its pools can turn on prepaid metered usage under a monthly cap it sets; the platform still never sends a bill. The prototype tier is free — it settles in testnet USDC purely to verify the agent's wallet and x402 setup, so no real money moves.
Every project gets a free yourname.run402.com address on every tier. Putting it on
your own domain — with automatic TLS, Run402-hosted DNS (one nameserver change), and email
at that domain — comes with Hobby and Team. Domains you have already connected keep working on any tier.
| Cheapest plan that includes your own domain | Price |
|---|---|
| Run402 Hobby — database, functions, hosting, auth and email included | $5 for 30 days |
| Base44 Starter | $20/month |
| Lovable Pro | $25/month |
| Bolt.new Pro | $25/month |
| Supabase Pro + custom domain add-on | $35/month ($25 + $10 per domain) |
Other vendors' prices are from their own pricing pages and documentation on September 26, 2026, billed monthly; annual billing can be cheaper. Check their sites for current terms.
Production tiers (hobby and team) are paid by the agent itself with real
USDC on Base via x402 or
pathUSD on Tempo via MPP, or
sats over Bitcoin Lightning via MPP from the agent's own budgeted Lightning wallet
(run402 init lightning) — no signup, no
dashboard, no card on file. If you would rather pay as a human, you can fund the organization's allowance with a
credit card via Stripe and let the agent spend it, or top the allowance up in sats —
run402 billing topup --sats 5000 mints a Lightning invoice any wallet can pay.
Storage, API calls, functions, secrets and email sends are pooled across every project your organization owns, not metered per project — several projects on one organization share one budget. Limits that bound a single invocation (function timeout, memory, schedule interval) stay per function.
A hobby or team organization can turn its pooled quotas into metered usage: the lease's pools become the included amounts, and what sits above them is charged once a day from the organization's allowance, never past a monthly cap you set. The same cap bounds a card standing order that refills the allowance from a card you save once. When the allowance or the cap cannot cover a day, metering pauses: nothing is deleted, everything keeps serving, the pooled limits apply again, and you are told before it happens.
| Above the included pools | Price |
|---|---|
| App storage | $0.10 per GB-month, prorated by the day |
| Vault bytes | $0.10 per GB-month, prorated by the day |
| API calls | $0.50 per million |
Under metering the function and secret ceilings apply per project instead of pooling. The free
prototype tier does not meter. run402 billing metering --enable --cap 50 turns it on;
run402 billing card setup saves the card.
When a lease expires the project does not vanish. It enters a grace ladder — the control plane locks first, while your users keep being served — and renewing restores it. The exact windows are in the full API reference.
Projects that sign Ethereum transactions rent a KMS-backed signer: $0.04/day per wallet ($1.20/month) plus $0.000005 per contract call (the KMS sign fee). Chain gas is passed through at cost. Keys are generated in AWS KMS and never leave it — non-custodial, and the gateway holds no decrypt permission. See /billing/.
KyGit has no separate price. A vault's bytes count against the same organization-pooled storage budget quoted on the cards above — billed as the larger of a 1 MB per-vault minimum or the sum of each unique object's size (with a 4 KiB per-object accounting floor), so a small vault reads as roughly the minimum instead of scaling with object count. An upload session reserves its bytes at issuance and releases them if it aborts or expires; a maintenance lease adds bounded headroom so a compaction can temporarily exceed the steady-state limit. Over the pool the write is refused rather than billed, the same as every other limit here.
Almost everything is covered by an active tier. The one per-call price left is image generation
at $0.03 per image, payable over x402, MPP on Tempo, or MPP on Bitcoin Lightning. The paid endpoints are listed in
api.run402.com/.well-known/x402; the price
itself arrives in the 402 challenge the endpoint returns, so an agent learns the
cost before it settles anything.
Machine-readable tier limits, payment rails and error codes live in
/llms.txt and /openapi.json. Setting a tier is one
call: POST /tiers/v1/:tier.