Billing & Usage

How billing works

Billing is measured per workspace:

• Plans define entitlements and quotas — what your workspace is allowed to do (number of services, replica counts, build minutes, and so on).
• Usage events are recorded by the platform as you consume resources: running replicas, builds, storage, bandwidth.
• Aggregates roll those events up into the numbers you see on the usage page and that quota checks enforce.

Usage metering is billing-grade: it's a dedicated pipeline separate from diagnostic metrics, designed so that what you're billed for can be traced back to individual recorded events.

Credits

Workspaces spend from a credit ledger. Plan allowances refill credits monthly; top-ups add to the same balance. Every grant and consumption is an individual ledger entry, so the balance is always explainable.

Quotas and entitlements

Quota checks are enforced at the source of truth (the billing service), not in the dashboard UI. When you hit a limit — creating a service, scaling replicas, starting a build — the API rejects the action with a clear entitlement error, and the dashboard surfaces it.

Upgrading a plan changes entitlements immediately; already-running resources that now exceed the new limits are not forcibly torn down, but new actions beyond quota are blocked.

Invoices

When a payment period closes, an invoice is generated for the workspace and delivered via notification (in-app and email). Invoice history stays available in billing settings.

What consumes what

Exact units and rates depend on your plan; the usage page shows live numbers per project and service.