Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Describe billing behavior from the actual implementation rather than from outdated status notes.

​
Prerequisites

  • None

​
Workflow

1
Use the billing dashboard for subscription and usage state.
2
Use the spending-limit surface to define alert thresholds and at-limit behavior.
3
Use payment-method management for default-method and deletion actions where supported.

​
What the billing dashboard includes

  • Plan selection and subscription-state cards
  • Current usage, usage projection, and spending-limit controls
  • Payment methods, transactions, and cancellation/change-plan flows

​
Reading subscription state

The subscription card reflects the real account state — for example active or trialing — which is what gates plan-limited features like extra databases, team creation, connection pooling, and manual database backups. If a feature prompts you to upgrade, this is where the state behind that prompt lives.

​
Spending controls

  • Set spending limits and alert thresholds so cost does not surprise you.
  • Understand at-limit behavior before you hit it.
  • Manage the default payment method and review transactions from the same surface.

​
Expected result

Billing documentation matches the current dashboard behavior and stops understating the feature area.

Plans and usage

Use the billing area to inspect plans, subscription state, usage, transactions, payment methods, and spending limits.