Plans and costs
What you are charged for, where to see it, and how the plan's limits relate to the bill.
On this page
What it is
A plan sits on the organization. It sets the limits, and it includes an amount of credit each month. What you actually run is metered against that credit, and anything beyond it is billed.
Two numbers matter and they are different questions. Limits answer "may I create this", and they are enforced on the form. Usage answers "what is this costing", and it accumulates while things run.
What is metered
| Metered | How |
|---|---|
| Compute | CPU and memory actually used by your workloads, over time |
| Storage | The size of the volumes and databases you have provisioned |
| Protected storage | Volumes with backup turned on, counted separately because keeping copies costs more than keeping one |
A workload scaled to zero stops costing compute and keeps costing storage. That is the cheapest way to park something you are not ready to delete.
Where to look
- Billing shows the current period: credit included, credit used, what is projected.
- Usage breaks that down by project and by workload, so a surprise has an address.
- Statements is the history, kept indefinitely, so last March is still there.
Limits and the plan
Every plan caps the same things: how many projects, apps and databases, how many replicas per app, how many custom domains, and how much CPU, memory and disk a single project may use in total.
Hitting a limit is a refused create with a message naming the limit, not a silent failure and not a surprise on the invoice. The free plan is deliberately small: one project, one app, one database, one replica each.
Limits are checked when you create, so a plan downgrade does not switch anything off. What is already running keeps running, and you will not be able to create more until you are back under the limit.
Settings reference
| Setting | Where | What it does |
|---|---|---|
| Plan | Billing | Sets every limit and the included credit. |
| Credit | Billing | Included monthly, consumed by usage before anything is charged. |
| Project quota | Quotas | How much CPU, memory and disk one project may use, inside the plan's ceiling. |
Limits and gotchas
- Storage bills whether or not it is used. A 100 GB volume that holds 2 GB costs 100 GB, because the space is reserved for you.
- Backups are storage too. Turning on protection for a large volume changes the bill, which is why it is off by default.
- Deleting is the only way to stop storage costs. Scaling to zero stops compute only.
- Only admins see any of this. Editors can create things that cost money and cannot see what they cost.
Related
- Organizations, projects, workloads for what the plan applies to.
- Members and roles for who may see the bill.