Every database you run, in one place
Choose from 18 available engines, including PostgreSQL, MySQL, MariaDB, Valkey, libSQL / SQLite, DuckDB, FerretDB, TypeDB, Meilisearch, Qdrant and TimescaleDB on Free. Backups you can restore, isolation that holds, and HIPAA-ready hosting (opening after our independent pen test) for only the databases that need it. You pay for what runs.
Paid plans from $25/month with one instance included.
orders-db
PostgreSQL 18
Connection string
postgresql://app:(password hidden)@pg-7f3k.us-east.databasezy.com:5432/app?sslmode=verify-full - Size
- s1 · 0.5 vCPU / 2 GiB
- Region
- us-east
- Backups
- Daily, last run 02:00 UTC
- Placement
- Shared, standard cell
Why Databasezy
One operational layer for every engine
The same backups, isolation, metering and portal for a cache, a search index or your primary database.
-
Secure hosting, per database
HIPAA-ready placement for the databases that hold PHI, under a BAA, on nodes dedicated to your organization.
Waitlist: opens after the pen test
How secure hosting works
-
Backups you can restore
Engine-native backups to object storage, restore drills, and the last backup is never pruned.
Backups and restore
-
18 engines, one control plane
Relational, key-value, document, search, vector, time-series and analytics.
Compare engines
-
Guided migrations
Preflight checks, a verified copy and a cutover you control. PostgreSQL and MySQL stay in sync until you switch.
Migrate a database
Engines
Pick the engine that fits the job
Relational, key-value, document, search, vector, time-series and analytics. 18 engines share the same backups, metering and portal. Each engine page lists its plans and features.
- PostgreSQL Available
- MySQL Available
- MariaDB Available
- Valkey Available
- Redis Available
- libSQL / SQLite Available
- DuckDB Available
- FerretDB Available
- MongoDB Available
- TypeDB Available
- CouchDB Available
- Meilisearch Available
- Qdrant Available
- Weaviate Available
- InfluxDB 3 Available
- QuestDB Available
- ClickHouse Available
- TimescaleDB Available
- OrioleDB Coming soon
Migrate
Bring your database with you
Choose where it lives today. We check compatibility before anything moves, copy and verify the data, and keep PostgreSQL and MySQL in sync until you switch your app over.
- MongoDB Atlas Guided now
- Neon Guided now
- PlanetScale Guided now
- Supabase Guided now
- Turso Guided now
- Upstash Redis Guided now
- Aiven Coming soon
- Amazon RDS and Aurora Coming soon
- Cloudflare D1 Coming soon
- Crunchy Bridge Coming soon
- DigitalOcean Managed Databases Coming soon
- Fly.io Coming soon
- Heroku Coming soon
- Netlify DB Coming soon
- Prisma Postgres Coming soon
- Railway Coming soon
- Redis Cloud Coming soon
- Render Coming soon
- Vercel KV (legacy, now Upstash) Coming soon
- Vercel Postgres (legacy, now Neon) Coming soon
- Algolia Coming soon
- Azure Database Coming soon
- Google Cloud SQL Coming soon
- Xata Coming soon
Not on a hosted platform? Migrate from your own server, a Docker container or a dump file with
zb migrate.
Connect
Connect the way you already work
A plain connection string for your app, a CLI for your terminal, an API for your automation and an MCP server for your assistant. All four see the same org-scoped resources.
Any driver that speaks the engine's protocol
Every instance gets a TLS endpoint on the engine's native port. Paste the URL into psql, an ORM or your app's environment and it works as it would anywhere else.
Connection guides per engineexport DATABASE_URL="postgresql://app:<password>@pg-7f3k.us-east.databasezy.com:5432/app?sslmode=verify-full"
psql "$DATABASE_URL" -c "select version();" The zb command line
Create, resize, pause and migrate from a terminal or a CI job. zb connect opens the engine's own shell with TLS and a one-time credential, so nothing sits in your shell history.
CLI referencezb login --key zb_...
zb instances create --engine postgres --size s1 --name orders-db --wait
zb connect inst_01J9ZK7F3K # the id printed by create An org-scoped REST API
The portal and the CLI use the same public API. Keys are scoped to one organization, every path sits under that org, and POST requests accept an idempotency key.
API referencecurl -sS -X POST \
https://api.databasezy.com/v1/orgs/$ZB_ORG_ID/projects/$ZB_PROJECT_ID/instances \
-H "Authorization: Bearer $ZB_API_KEY" \
-H "Content-Type: application/json" \
-d '{"engine":"postgres","size":"s1","name":"orders-db"}' Hand the routine work to your AI assistant
The MCP server lets Claude Code, Cursor or any MCP client list engines, create and pause instances and look up connection details. It never returns secrets; you reveal credentials yourself.
MCP server setup{
"mcpServers": {
"databasezy": {
"command": "npx",
"args": ["-y", "zb-mcp"],
"env": { "ZB_API_KEY": "zb_...", "ZB_ORG_ID": "org_..." }
}
}
} Platform
The work around the database, handled
Each engine gets the same operational layer, so a cache and a primary database are backed up, secured and billed the same way.
- Isolation by tier Free, standard and secure workloads run on separate clusters, buckets and keys.
- Spend cap Overage on storage, egress and backups stops at your allowance until you raise it.
- Teams and roles Project-scoped and read-only roles, SSO and an audit log on Team.
- Network security TLS 1.3 on every endpoint and IP allow-lists on every plan, free included.
- CLI Create, connect, migrate and read usage from a terminal or CI job.
- API and MCP The same org-scoped API the portal uses, plus an MCP server for AI assistants.
Pricing
A plan fee, then the hours you actually run
Every paid plan includes one instance. Add more by the hour at their size price, with disk, egress and backup allowances on top. Solo starts with a spend cap switched on.
Free
- 1 instance on size f0
- 500 MB per instance, 11 GB egress
- 1 member, 1 project
- 2-day first response, no SLA
Solo
Most popular- 1 instance included, then from $10/mo per instance
- 8 GB per instance, 250 GB egress
- 1 seat (the org owner)
- 4-hour first response, no SLA
Team
- 1 instance included, then from $10/mo per instance
- 8 GB per instance, 250 GB egress
- SSO, roles, audit log, HIPAA waitlist
- 99.9% SLA · 1-hour first response
Enterprise
- Negotiated usage and volume pricing
- Backups: Hourly, 35-day retention · PITR 35 days · cross-region copy · immutable (Object Lock)
- Custom retention; CMK and PrivateLink on the roadmap
- 99.95% SLA · 30-minute first response
Worked example
Four databases on Solo, priced line by line
A small production app with a primary database, a cache, an event store and a small SQLite-compatible store for settings. Prices come straight from the same catalogue the bill uses.
| Instance | Engine | Size | Per month |
|---|---|---|---|
| app-db | PostgreSQL | s1 | $15 |
| cache | Valkey | s0 | $10 |
| events | MySQL | s0 | $10 |
| edge-sqlite | libSQL / SQLite | s0 | $10 |
| Solo plan fee | Flat, per organization | $25 | |
| Compute credit | Covers one included instance | −$10 | |
| Estimated total | $60 | ||
Hourly prices × 730 hours, rounded to whole dollars. Each instance includes 8 GB of disk, and the organization shares a 250 GB egress pool and 100 GB of backup storage, so a setup like this usually adds nothing beyond compute.
- Pause an instance and its compute stops; only its disk is billed.
- Resize whenever you like; the bill follows the hours at each size.
- The spend cap stops storage, egress and backup overage at your allowance.
Compare
How it compares with the usual options
A single-engine managed host or a database on your own VM can be the right call. This is where we differ.
| Capability | Databasezy | Single-engine host | Self-managed VM |
|---|---|---|---|
| Many engines on one control plane and one invoice | Yes: 18 available today | No: Usually one or two | Partly: One server per engine, by hand |
| HIPAA-ready hosting chosen per database, with a BAA (opens after our pen test) | Partly: Team and up, after the pen test | Partly: Often enterprise contracts only | Partly: You build and evidence it |
| Staff need a time-boxed grant you issue to touch data | Yes: Enforced, and audited | Partly: Check the terms | Partly: Depends on who has SSH |
| Engine-native backups, last backup kept | Yes: Every engine | Partly: Snapshots vary by engine | No: Your scripts |
| Spend cap on overage | Yes: On by default on Solo | Partly: Alerts more often than caps | No: Fixed bill, idle or not |
| Guided migration with a verified copy | Yes: 6 providers guided today | Partly: Import tools vary | No: Manual dump and restore |
Security
Only you can read your data
Isolation and access control are properties of how the platform is built, not promises in a policy document.
-
Only you read your data
Staff can start, stop, back up and move an instance, but have no read path into it. Support access needs a time-limited grant from you.
-
Credentials stay in the cell
Passwords are generated next to the database and shown to you once. The control plane keeps a reference, never the secret.
-
Encrypted in transit and at rest
TLS 1.2 or 1.3 at the edge. MySQL and MariaDB also encrypt traffic inside the cell; other engines currently use plaintext there. Per-tier keys at rest; per-org customer-managed keys are not available yet.
-
Every action on the record
A tamper-evident audit log of control-plane actions that you can export to your SIEM.
Secure hosting, per database
For the instances that hold protected health information: they run in a HIPAA cell on nodes dedicated to your organization; the rest of your fleet stays on standard cells and standard prices. HIPAA hosting opens after the independent penetration test. Until then, join the waitlist.
- Business Associate Agreement
- Nodes dedicated to your org
- Immutable backups
- Audit log export
FAQ
Questions people ask before they sign up
What does the free tier include?
One database on a free cell, up to 500 MB, on PostgreSQL, MySQL, MariaDB, Valkey, libSQL / SQLite, DuckDB, FerretDB, TypeDB, Meilisearch, Qdrant and TimescaleDB. No card is needed. It sleeps after 15 minutes without connections and wakes on the next one; after 7 days asleep it is archived (disk kept) until you resume it.
How is a paid plan billed?
A monthly plan fee, then every running instance by the hour at its size price. The fee includes a compute credit that covers one s0 instance (about $10 a month). Disk above the per-instance allowance, egress above the shared pool and backup storage are metered. Paused instances stop accruing compute; their disk is still billed.
Can a usage spike surprise me?
Solo ships with a spend cap switched on: storage, egress and backup overage stops being charged at your included allowance, and you get warnings at 80, 90 and 100 percent. Compute is never capped, because you choose the sizes; resizing or pausing is the lever there. On Team the cap is off by default; switching it is not in the portal yet, so ask in a billing ticket.
What is secure hosting, and do I need it?
It is a per-database placement for data covered by HIPAA. A secure instance runs in a separate HIPAA cell on nodes dedicated to your organization, with immutable backups (customer-managed keys are not available yet). It needs Team or above and a signed BAA, and is billed as an add-on per instance-hour ($0.10 per hour plus dedicated node time). Everything else in your org keeps running on the shared standard cells. It is not open yet: HIPAA hosting opens after the independent penetration test. Until then you can join the waitlist: sign the BAA in the portal or contact sales.
Which engines can I run today?
PostgreSQL, MySQL, MariaDB, Valkey, Redis, libSQL / SQLite, DuckDB, FerretDB, MongoDB, TypeDB, CouchDB, Meilisearch, Qdrant, Weaviate, InfluxDB 3, QuestDB, ClickHouse and TimescaleDB are available now. They share the same control plane, backups and billing. Engine pages show plan and feature availability.
Can Databasezy staff see what is in my database?
No. Operators manage instances through the control plane, which has no path to read your data. If support needs to look inside, you issue a time-boxed grant from the portal, and the access is written to your audit log.
How do I move an existing database in?
Point the migration at a connection string, upload a dump, or run the CLI from your own machine. A preflight report lists anything that will not carry over, the copy is verified before you cut over, and PostgreSQL and MySQL can stay in sync until you cut over.
What happens to backups after I delete an instance?
They are kept for a while so a mistake is recoverable: 7 days on Solo and 14 days on Team. Then every backup, the newest backup included, and the point-in-time archives are purged. Full erasure, which removes everything without waiting (a backup under Object Lock when its lock lapses) and gives you an erasure certificate, is temporarily unavailable.
Something else? Read the documentation or email [email protected].
Your first database is a minute away
Start on the free tier without a card. Move to a paid plan when you need more; nothing upgrades on its own.