Everything on your own machine stays free forever, with no account and no card. You pay when an app stops being a toy and starts holding something you would hate to lose.
Hosted backends bill per project. We bill per account, and the server is one you already rent.
| Apps you are running | Supabase Pro | CrescoDB Pro, plus a $6 server |
|---|---|---|
| 1 | $25 | $29 |
| 3 | $45 | $29 |
| 8 | $95 | $29 |
| 15 | $165 | $29 |
On one app they are cheaper, and we are not going to pretend otherwise. The difference shows up on the second one. A hosted backend adds a line item every time you take on a client. Our 15 apps run on one box you already pay for, so the bill stops moving.
There is no usage meter on top of it either. No egress charge, no per-row read, no compute add-on that appears the month something gets popular. The server has a fixed price and you picked it.
Supabase Pro as published on 23 August 2026: $25/mo per organisation, first project included, additional projects from $10/mo, before any storage, bandwidth or compute overage. Server price is a small Hetzner or Contabo box. Check both yourself, we would rather you did.
Fair question, so here is the honest answer.
Everything that runs on your laptop costs us nothing, so we do not charge for it. You can build with CrescoDB for years, ship client work with it, and never pay us a penny. That is not a trial, and it does not expire.
What costs us money is the part that runs while you are asleep: taking a backup every night, restoring it into a throwaway database to check it actually works, watching your app and telling you the moment it stops answering. We charge for that, because we are betting that the first time it saves you, you will not want to go back.
Your database is a file on your machine. Your app runs on a server you rent. If you cancel, all of it keeps running exactly as it is, because none of it was ever hostage.
The honest question, answered without a promise.
Your app does not depend on us running. Your database is standard Postgres, MySQL or SQLite on a machine you control, and your app is a container on your own server that renews its own certificates. One command, cresco eject, hands you the whole thing plus every row of your data as plain SQL that any database client can read.
And if the company ceases operating, the CLI and engine source is published under Apache 2.0. That is not us being open source, which we are not. It is insurance for the one case where there is nobody left to own it.