Billing, invoices and overage
How billing works per organization: changing plan, the monthly cycle, usage, invoices and payment, choosing which services may go beyond their allowance, and cancelling.
Billing belongs to the organization: one plan covers all its projects and one invoice is issued per month. Prices are on the pricing page; every limit is in Plan limits.
Change plan
Organization › Billing › Change plan
Owners, admins and members with
billing.managecan change it.Check out
Pay for the new plan; it applies to every project in the organization at once.
Limits move with it
Higher limits apply immediately. On a lower plan, actions beyond its limits are refused with
403 PLAN_LIMIT_REACHED(for example creating more projects than it allows).
Usage and allowances
Each plan includes monthly allowances (requests, storage, function compute, egress, emails, messages…) and ceilings (projects, connections, file size…). Allowances reset each month. Project Settings › Plan & usage shows usage against each one, and the console warns before you reach a limit (Plan and usage).
| At an allowance | Free | Paid plans |
|---|---|---|
| Default | Stops (403 PLAN_QUOTA_EXHAUSTED) until the month resets or you upgrade. | Keeps working and the extra is billed (overage) for services marked "billed beyond". |
| Your choice | — | Turn overage off per service under Billing; that service then stops at its allowance like Free. |
Ceilings never bill extra: reaching one refuses the action with 403 PLAN_LIMIT_REACHED and a link to upgrade.
Invoices and payment
- Billing › Invoices lists every invoice; the current month's shows usage so far.
- Pay an open invoice from its row. Payment details are entered on the payment provider's page; Sovaria never sees card numbers.
Cancel or resume
Cancelling a paid subscription keeps the plan until the end of the paid period; Resume before then undoes it. Deleting the organization cancels the subscription too (Organizations, members and roles).
From code
Usage, invoices and overage switches are available over the API for dashboards and cost alerts — REST: plans, usage and billing, JavaScript: Billing and usage, Python: Billing, usage and health.
Keep costs down
- Give functions the memory they need, not the maximum: compute is billed in GB-seconds (Function memory, timeout and limits).
- Serve public files from public buckets so they can be cached; use signed links for private ones.
- Turn on idle pause for databases you use rarely (Free pauses after 7 idle days automatically) — Database: connection, compute, disk and backups.
- Keep log retention and log drains to what you use.