The deploy
One command, to a server you rent from whoever you like. Automatic HTTPS with certificates that renew themselves. A rollback point saved before it switches over.
The access audit runs first, so a table anyone can read never reaches the internet. If there is a critical finding, the deploy refuses and writes nothing.
What runs on the server
Your app is a container. Your database is standard PostgreSQL, MySQL or SQLite, on that machine. There is no call home: a deployed CrescoDB app does not ask our platform for permission to keep running, which is what makes the continuity story checkable rather than a promise.
The cost shape, said plainly
Hosted backends bill per project. Every client you take on adds a line to the bill. We bill per account, and the server is one you already rent.
| Apps you run | Hosted, per project | CrescoDB Pro + a $6 server |
|---|---|---|
| 1 | $25 | $29 |
| 3 | $45 | $29 |
| 8 | $95 | $29 |
| 15 | $165 | $29 |
On one app, hosted is cheaper, and we are not going to pretend otherwise. The difference shows up on the second one. Figures are the published rates as of September 2026, before any storage, bandwidth or compute overage. Check both yourself.
Compared to the managed platforms
The full side by side is on CrescoDB vs Supabase.
No usage meter
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. That is the entire reason a surprise bill is not possible here: there is no meter to run away with.