Skip to content

Spend cap

The spend cap makes sure you are never billed for more than your plan’s base price. It is on by default on every plan, and always on for Free.

With the cap on

Usage past an allowance is never billed. Instead:

Allowance used upWhat is blockedError
Storage or write requestsWrites. Reads keep working.429 plan_limit on writes
Read requestsEvery query429 plan_limit
  • The block is applied within minutes of usage crossing the allowance, and lifted when the billing period resets (or when you upgrade or turn the cap off).
  • Over Bolt, blocked statements fail with Security.Forbidden.
  • Owners, admins and billing members are emailed at 80% and 100% of each allowance, and when the cap blocks something (the Alerts page can change who). The same events are available as alerts and webhooks (usage.threshold, spend_cap.reached).

On Free there is no overage price, so the Free allowances are hard caps.

With the cap off

Owners, admins and billing members of a Pro or Scale organization can turn the cap off under Billing → Spend cap. Everything then keeps serving past the allowance, and the overage is billed at the plan’s rates:

ProScale
Storage$0.025 per GB-month$0.02 per GB-month
Write requests$6 per million$5.50 per million
Read requests$0.50 per million$0.45 per million

The Usage page and GET /usage show the estimated overage so far in the period. Turning the cap back on applies from that moment; usage already billed stays billed.

Every change to the cap is in the audit log.

Tips

  • Watch the Usage page or subscribe a webhook to usage.threshold to hear about growth before it blocks anything.
  • Rate limits are separate from the spend cap: a burst over the plan’s requests per second answers 429 rate_limited with a short Retry-After, whatever the cap says. See Rate limits.