CrescoDB

SQLite is the zero-config default for local dev and read-heavy apps. For production scale you point CrescoDB at PostgreSQL or MySQL from day one and develop against it directly. Same schema, same API, no SQLite-to-Postgres rewrite at deploy.

Yes. Your app talks to the auto-generated REST API over HTTP from any language (Python, Go, Rust, PHP, your frontend). You only need Node installed to run the CLI, the same way you'd need Docker to run a database container.

cresco create auth writes complete, working auth into your repo: register.js, login.js, middleware you can read and edit, not a black box. Want it managed instead? cresco add auth enables the built-in module with per-table RBAC. Express and Next.js variants included.

Chat is included on every plan; the coding agent unlocks on Pro. Each plan comes with monthly Cresco tokens, and your dashboard shows your balance.

The agent is scoped to your project folder, every file edit shows a diff you can undo, and every terminal command needs your approval. It runs locally, on your machine.

Yes. Team plans (per seat) let you create shared workspaces where everyone works on the same live database, plus a private @org module registry. Enterprise adds our most capable model on every big task, unlimited cloud resources, and dedicated support.

Yes. You rent a $5 box from anywhere (Hetzner, DigitalOcean, Vultr), paste one command into it, and CrescoDB does the rest: Docker, a locked-down deploy user, the reverse proxy, the HTTPS certificate. When you add a domain, we show you the exact record to paste into Cloudflare or Namecheap, then check it for you and tell you what is wrong if it is not working. You do not need to learn Linux to use this.

Everything on your own machine, forever, with no card: the database, the API, auth, storage, realtime, the dashboard, the scaffolds, and AI chat. On top of that you get one app deployed to one server. What free does not include is automatic nightly backups, and alerts are capped at 50 a month, by email only, with 3 alert rules and 3 uptime checks.

Nothing stops. Your database is a file on a server you rent, your code is in your repo, and your app keeps serving traffic exactly as it is. You lose the nightly backups and the alerting, not the app. We never hold your data to make you stay.

Most platforms call a backup successful when a file finishes writing. That tells you nothing about whether it works. We take the snapshot, then load it into a scratch database and check the tables are really there. If the restore fails, you get an email that morning, while you still have older copies to fall back on.