Plans & limits

What the Free trial, Business and Enterprise plans include, which limits apply, what a limit error looks like in the CLI and console, and how to upgrade.

Dibbla has three plans — Free trial, Business and Enterprise — and this page is the reference the platform itself points at: when a deploy or a db create stops at a plan limit, the error links here.

Prices and what each plan includes are on the pricing page. Your organization’s current plan is shown in the chrome of every screen — a badge in the sidebar of both the portal and the console, so it travels with you instead of living on one page you have no standing reason to visit. Org settings → Plan in the console adds the usage bars for the limited resources and the upgrade actions.

The CLI shows it too, in dibbla org list (the PLAN column) and in dibbla status — but note that the CLI prints the plan’s internal key, so the Business plan appears there as standard. Same plan, older name.

How you get a trial

Sign up free on the public pricing page takes you through login and, when you are new, organization creation. The 30 days belong to the new organization — clicking the CTA never resets an existing or expired trial. Existing users continue to their current organization and plan.

Both routes on the first-run screen create a new organization and start its trial:

• Personal Account — a personal workspace just for you.
• Create Organization — a workspace for a team.

Either way the new organization starts on a 30-day free trial, and no card is collected. Stripe only enters the picture if an owner or admin explicitly confirms an upgrade. The end date is shown in the console, on the portal welcome screen and in dibbla status:

Plan:    trial (ends 2026-09-21T23:06:45Z)
         upgrade: run dibbla upgrade for a payment link

In the trial’s last week dibbla status counts the days instead and adds the upgrade link:

Plan:    trial (ends in 3 days, Oct 1)
         upgrade: https://console.dibbla.com/org-settings/plan?upgrade=review
                  or run dibbla upgrade for a payment link

Reminders by e-mail

You don’t have to be deploying to hear about it. Every owner and admin of the organization gets a short e-mail (for a personal workspace, that is you):

• Seven days before the trial ends, and again the day before: when it ends, that your apps keep running afterwards, and the link to upgrade.
• The day it ends: your apps keep running exactly as they are; deploying is paused until you upgrade, and the link is there when you want it.
• A week after it ended, only if the organization is still on the trial: your apps are still running, and what, if anything, is in the way.

Reply to any of them and a person reads your answer. There are no reminders after that.

Each reminder is sent once. An organization that has upgraded gets none of the ones still to come, and none is sent late: a reminder whose day had already passed is skipped. A subscription that ended through Stripe — a cancellation or a payment that finally failed — gets no trial reminders; Stripe’s own e-mails cover that. The Unsubscribe link at the bottom of the mail stops further trial reminders for you; the other owners and admins keep theirs. In the console the reminders are listed under Free trial among the events you can subscribe to, and each one shows up in the delivery log.

Two things follow from where the trial is granted:

• Creating an organization is open to anyone. It used to be limited to a short list of e-mail domains; that restriction is gone.
• Being invited into an existing organization does not start a new trial. You join that organization and inherit whatever plan it is on — joining a paying team gives you the paying team’s plan, not a fresh 30-day clock.

Limits per plan

Two rules worth knowing:

• Limits apply to creating things, never to running them. An app that is already deployed keeps serving whatever happens to your plan — and an organization sitting exactly at its app limit can always redeploy the apps it has. Only adding an app or database past the limit is refused.
• No plan means no limits. Self-hosted installations have no billing surface and no plan concept; nothing on this page applies there.

Organizations with individually agreed limits (Enterprise, or any adjustment made by the platform team) see their own numbers in the console usage bars — the table above is the default.

A heads-up in the trial’s last week

So the end is never a surprise, the last seven days of a trial are said out loud where you work. A successful dibbla deploy ends with a line like this (on a git push it follows the operation on the remote: lines):

Heads-up: your free trial ends in 5 days (Oct 1). Your apps keep running
after that, but deploys pause until you upgrade:
https://console.dibbla.com/org-settings/plan?upgrade=review

The deploy itself worked; the line is a reminder, not an error. An agent over MCP gets the same reminder from platform_deployment_start and platform_whoami as trial_warning (days left and the upgrade link), with an instruction to mention it to you once. platform_whoami also states the days left — or that the trial ended — at any point in a trial, and --json output carries trial_warning.

Days are counted the way the console counts them: whole days, rounded up, never negative, and “ended” once the end has passed. Eight days or more, or any plan other than the free trial, shows nothing.

What hitting a limit looks like

The refusal happens before any work: a deploy past the app limit is rejected before the archive even uploads. The refusal says what is included, and links straight to the page where you upgrade:

● Your trial plan includes 3 apps and this org has 3. To add another, remove
  one or upgrade to Business (1 000 kr / €89 / $100 per month, VAT included):
      https://console.dibbla.com/org-settings/plan?upgrade=review

  Docs: https://docs.dibbla.com/reference/plans

When a free trial ends, deploys (dibbla deploy, git push, and agents over MCP) and creating databases are paused. Your running apps, databases and data are not touched, and upgrading lifts the pause at once:

● Your free trial has ended — thanks for trying Dibbla!
  Your apps keep running exactly as they are. To deploy again, upgrade to
  Business (1 000 kr / €89 / $100 per month, VAT included):
      https://console.dibbla.com/org-settings/plan?upgrade=review
    Or get the payment link right here: dibbla upgrade

  Docs: https://docs.dibbla.com/reference/plans

The link opens the upgrade review in the console, one step from Stripe Checkout. The price is read from Stripe when the message is written; if it cannot be read, the message leaves it out rather than guess.

• git push to main is refused with the same text on the push’s remote: lines, so main stays at what is running.
• dibbla db create says “To create databases again”.
• An agent over MCP gets the same text, the link as upgrade_url, and an instruction to show you the link instead of retrying. If you are an owner or admin, the agent can also hand you a direct payment link — see From your agent.
• In the terminal, the refusal ends with dibbla upgrade, which prints a direct payment link — see From the terminal.
• --json output carries api_error_code, documentation, upgrade_url and, for a trial, upgrade_command.

The console shows the corresponding state inline in Org settings → Plan.

Upgrading

From the public pricing page, Sign up for Business carries your intent through login and first-organization onboarding. It does not create a payment session.

In the console, open Org settings → Plan and choose Review upgrade to Business. The review names the organization, monthly plan and current base price. Nothing has been created in Stripe yet. Only Confirm and continue to Stripe starts the hosted checkout; Stripe shows the final currency and total before you decide whether to complete payment. Dibbla never sees your card details, and the plan changes as soon as payment completes.

From your agent

If your agent is connected to Dibbla over MCP (Claude Code, Codex, claude.ai), ask it for the upgrade link. It calls platform_whoami with upgrade=true and shows you a Stripe Checkout link for Business for the organization it is connected to. Nothing changes until you pay; after you have, Stripe returns you to Org settings → Plan in the console, which confirms Business for that organization even if the console was not open or had another organization selected, and the agent’s next deploy goes through. The link expires after 24 hours if you do not use it.

The agent only gives the link to an owner or admin. A member or viewer is told who can upgrade, and an organization that is already on Business, on Enterprise or invoiced by Dibbla directly is told so — without a link, and without anything being created in Stripe.

From the terminal

dibbla upgrade prints the same Stripe Checkout link for the organization the CLI acts as, with a short explanation. --open also opens it in your browser, and --json gives it to a script or an agent as checkout_url:

dibbla upgrade
dibbla upgrade --open
dibbla upgrade --json

As with the agent, nothing changes until you pay, and the link expires after 24 hours. Only an owner or admin gets a link. A member or viewer is told who can upgrade, and an organization already on Business, on Enterprise or invoiced by Dibbla directly is told so — without a link ("status": "not_available" and a reason in --json). Managing or cancelling a subscription is not done from the CLI; use Manage billing in the console.

Who can upgrade

If you are a member or viewer, ask an organization owner or admin to upgrade — the Plan screen and Checkout action are administrative. Card and subscription management (receipts, cancelling) lives behind Manage billing on the same tab.

For Enterprise — self-hosting, increased support, SLA or custom limits — contact us.