Billing & plans

Plans, metered usage, invoices, payment, and what suspension means.

How Cloud billing works

A project subscribes to a plan: a base fee plus metered prices over the usage dimensions (reads, writes, storage, function requests…). Each billing period the meters are rated against the plan's published prices and an invoice is issued. The invoice freezes its numbers — repricing a plan later never rewrites a past invoice.

The Billing screen: plan, live estimate, invoices.

Paying

Invoices are paid through the payment provider; the Pay button hands you to it, and the invoice becomes paid only when the provider's confirmation is verified server-side. There is no "mark as paid".

The billing role

Add your finance person with the billing role: they see plans, usage totals and invoices and can pay — and can never open Basket data, Auth users or API keys. Teams & roles.

Falling behind, and hard caps

Past due — the invoice ages unpaid; the console says so plainly.
Suspended — writes are refused (Basket writes, function invocations); reads and the billing page keep working, because the way back to good standing must never be behind the wall.
Hard caps — a plan may cap a dimension; at the cap, writes on that dimension refuse with a clear error instead of billing you past what you agreed.

Function invocations refused for commercial state are refused before dispatch — never billed. Functions billing.