Skip to content

Help

Upgrade, downgrade or cancel your plan

Tested with:Databasezy API v1 · zb CLI 0.1

Plan changes are made in the portal under Billing → Plans. Upgrades apply at once and Stripe prorates the rest of the period. Downgrades between paid plans apply at the end of the current period, and only once your organization fits the smaller plan. Moving to Free means cancelling the paid plan. Enterprise is a contract arranged with sales.

A person with the billing:manage permission (owners, admins and billing members by default), signed in to the portal. API keys and support sessions cannot change or cancel a plan. When you move between paid plans or cancel, you may be asked to sign in again first:

  • If you use two-factor authentication, your second factor must be from the last 15 minutes.
  • If you do not, you need a sign-in from the last 15 minutes. You are never made to set up two-factor authentication just to change or cancel a plan.

Choose Solo or Team under Billing → Plans. You are sent to Stripe Checkout to add a card (paid plans need one), your billing address and, if you have one, a tax ID. The new plan’s limits apply as soon as checkout completes.

  • Solo → Team (upgrade): applies immediately. Stripe charges the prorated difference for the rest of the current period.
  • Team → Solo (downgrade): scheduled for the end of the current period. Until then Team keeps working. Choosing Team again before the period ends withdraws the scheduled downgrade.

The plan picker shows, before you confirm, how the change is made, when it applies and anything that blocks it. The same preview is available from the API:

shell
zb api GET "/v1/orgs/{org}/plan-change-preview?plan=solo"

“the organization does not fit the smaller plan yet”

Section titled ““the organization does not fit the smaller plan yet””

A downgrade is refused (409) while you use more than the target plan allows. The error lists each blocker, for example:

  • Instances: “Solo allows 20 instances; you have 23. Delete 3 before switching.”
  • Sizes: an instance is larger than the target plan’s largest size. Resize or delete it.
  • Placement: the target plan has no secure or dedicated-node hosting. Move or delete those instances.
  • Members: Solo has one seat, the owner. Remove the other members on Members.
  • Projects and custom domains above the target plan’s limits.

Clear the listed items, then try again. Quotas for every plan are in Limits and quotas.

Choose Free under Billing → Plans. This opens the cancellation page, which asks for a reason and shows the exact dates for your organization:

  1. Until the end of the current period, your paid plan keeps working.
  2. At the period end, the organization moves to Free. The final invoice covers that period’s usage; no further plan fee is charged.
  3. 7 days later, every database is suspended: connections are refused, but the data is kept.
  4. Suspended databases and their data stay kept: nothing deletes them on a timer. Subscribe to a paid plan again to resume them, or delete what you no longer need. If an inactive organization is ever reviewed for cleanup, you are emailed at least 24 hours before anything is deleted.

You can Resume subscription from the Billing page any time before the period ends; nothing changes and the plan renews as before. If a “the plan is cancelled at the end of this period: resume it first” error appears when you try another plan change, resume first.

Enterprise is a contract plan. The portal answers “Enterprise is a contract plan: talk to sales” and the plan picker shows a contact option instead of checkout. Changes to an Enterprise contract go through your account manager.

Limits, included allowances and features change as soon as the new plan applies: more instances and larger sizes, more members, project roles, SSO, the audit log and HIPAA secure hosting on Team, and longer backup retention. Compare plans on Usage and billing and the pricing page.

Search the help center or ask the assistant in the portal Help panel. If that does not solve it, open a support ticket from the portal (Help → Open a ticket, category billing) and include the plan you are moving from and to, the exact error text with its list of blockers, and the time in UTC. Never paste passwords, connection strings with passwords, API keys or patient data (PHI) into a ticket. See How to get help.