Why you should ask
You have seen platforms remove a free tier, change the deal, or quietly shut down. Putting a client's project on a small company is a real risk and pretending otherwise would be insulting.
So rather than reassure you, here is what is structurally true.
Your app does not depend on us running
Your database is standard PostgreSQL, MySQL or SQLite on a machine you control. Your app is a container on your own server that renews its own certificates. A deployed CrescoDB app makes no call to our platform to keep serving traffic.
If our control plane went dark tonight, your app would not notice.
One command hands you everything
Writes a folder that runs with no account and no dependency on us: your code, your data as plain SQL that any database client can read, and the engine vendored in. Nothing in it phones home.
This is not an export you request and wait for. It is a command that exists today, on the free tier.
If the company ceases operating
The CLI and engine source get published under Apache 2.0. That commitment is written down and public at crescodb.com/continuity, with the conditions that trigger it, rather than offered verbally.
We are closed source and privately owned, and we still hand you the exit. Lock-in is a business model we decided not to have.
How to verify this before trusting it
- Run cresco eject on a test project and start the folder it writes, with no account signed in.
- Open the .sql file it produces in any database client.
- Read the continuity page and check whether the trigger conditions are things you could verify yourself, without our cooperation.
If any of those does not hold up, we would rather you found out now.