Skip to content

Help

Understanding your bill

Tested with:Databasezy API v1 · zb CLI 0.1

Your monthly bill is the plan fee, plus compute for every running instance at its size’s hourly price, plus usage above your plan’s included allowances, plus add-ons. The included allowances and the monthly compute credit are subtracted before usage reaches the invoice, so the invoice shows only what you pay for. Free organizations are never billed. Current prices and allowances are generated from our catalogue on Usage and billing; this article explains why a line is there.

Where do I see what I will pay this month?

Section titled “Where do I see what I will pay this month?”

In the portal, open Billing. This period’s bill is an estimate until the invoice is issued, built from the same metering data billing uses. Usage shows metric and instance filters for the selected time range. From the CLI:

shell
zb usage --by instance # this month so far, list-price cost per instance
zb usage --by metric --csv # one row per meter, as CSV

zb usage takes --from and --to (RFC 3339) for other periods.

The plan fee is only the first line. The others are:

  • Compute. Every running instance is billed at its size price (sizes): per hour for a normal database, and per minute (rounded up, at least one minute) for a short-lived one - a branch, a database with a time to live, or a restore preview.
  • Disk above the per-instance allowance.
  • Egress (data sent from your instances to clients) above the organization’s pool.
  • Backup storage above the included amount.
  • Add-ons such as point-in-time recovery and custom domains, and the secure hosting charge per secure instance.
  • Platform services (auth, storage, functions, realtime, apps) above their allowances, listed in Platform pricing and limits.

Taxes are added by Stripe on the invoice.

Solo and Team include one instance: a monthly credit, applied once per organization, that covers one instance of the smallest paid size running all month. The credit is a money amount, so it is netted against your compute across all sizes. It does not carry over to the next month.

Why was my second instance charged in full?

Section titled “Why was my second instance charged in full?”

The credit covers one smallest-size instance. Every additional instance, and the part of a larger size above the credit, is billed at its full hourly price. Read replicas are billed like an instance of their size, and the credit never applies to them.

Pausing stops compute billing only. The instance’s disk and its backups are kept, so they are still billed if they are above your allowances. To stop all charges for an instance you no longer need, delete it. Deleted instances keep their data for your plan’s retention window (backups and retention).

Disk is billed on the provisioned size of each instance’s volume, not on the bytes your data uses. The allowance is per instance, so one instance’s unused allowance does not offset another’s. Storage can grow but cannot shrink in place: to get a smaller volume, restore a backup into a new, smaller instance and delete the old one (resize).

Why was I charged for an instance I deleted?

Section titled “Why was I charged for an instance I deleted?”

Compute is billed for the hours an instance was running. It is derived from state changes (created, paused, resumed, deleted), not sampled, so a database that ran for part of the month appears for exactly those hours.

Bytes sent from an instance to your clients, measured at our gateway, plus response bytes from platform services. Data you send in, and backups, are free. Egress prices differ by region.

Why does the invoice not match the estimate exactly?

Section titled “Why does the invoice not match the estimate exactly?”

The estimate in the portal uses list prices before tax. The invoice adds tax, and applies any credits on your account (promotional credits, programme credits, SLA credits) as a balance. Usage is pushed to Stripe hourly, so the last hours of the period land just before the invoice is finalised.

On Solo (on by default) and Team (off by default), the plan’s spend cap stops overage on database storage, data transfer and backup storage from being charged. The plan fee, compute and add-ons are always billed. With the cap on, platform-service allowances become hard limits instead of being billed; Remote Config fetches above their allowance are neither refused nor billed. The Billing page shows the amount that was not charged. See Spending caps and quota errors.

Search the help center or ask the assistant in the portal Help panel; it can read your plan and this period’s usage summary. If that does not solve it, open a support ticket from the portal (Help → Open a ticket, category billing) and include the invoice number or billing period, the line you are asking about, and the instance id if it is about one instance. Never paste passwords, connection strings with passwords, API keys or patient data (PHI) into a ticket, and never send card numbers. See How to get help.