Skip to content

Help

Frequently asked questions

Tested with:Databasezy API v1 · zb CLI 0.1

Databasezy runs managed databases for you: you pick an engine, a size and a region, and we run it, back it up, meter it and keep it patched. These are the questions we hear most. Each answer links to the page with the full detail.

A managed database host. Each database is an instance with its own hostname, credentials, IP allow-list, backups and metering. Instances live in projects inside your organization, which holds the plan, the members and the bill. Concepts explains the vocabulary and Quickstart creates your first database.

Eighteen engines are in the catalogue and all of them can be ordered today: PostgreSQL, TimescaleDB, MySQL, MariaDB, Valkey, Redis (compatible), libSQL / SQLite, DuckDB, FerretDB, MongoDB (Percona Server), ClickHouse, CouchDB, TypeDB, Meilisearch, Qdrant, Weaviate, InfluxDB 3 and QuestDB. Versions and features per engine are in the engine reference.

New instances can be created in US East (N. Virginia), region id us-east. EU West (Ireland) is planned and is not accepting instances yet; the API answers region ... is not accepting new instances if you ask for it.

One database on the smallest size, no card needed, with hard limits instead of overage charges. Idle Free databases sleep after 15 minutes without connections and wake on the next connection. After 7 idle days they are archived, and can be resumed explicitly. There is currently no automatic deletion timer for archived databases; the catalogue’s 90-day threshold is reserved for cleanup review, not automatic deletion. Keep independent backups and follow account notices. ClickHouse cannot sleep, so it is not offered on Free. See Pause and resume and Limits and quotas.

Yes, on every engine except ClickHouse. A paused instance bills no compute, but its storage and backups are still billed. Paid instances never pause on their own. See Pause and resume and Paused instances and wake-up time.

In the region you chose for the instance, on a volume that belongs to that instance alone. Backups are kept in that region too; Enterprise and secure instances also get a cross-region copy for disaster recovery. The control plane never stores your instance credentials and never proxies your queries. Details are in Data confidentiality.

Not yet. Health data belongs on a secure instance, and HIPAA hosting opens after the independent penetration test. Until then you can join the waitlist: an organization owner signs the Business Associate Agreement (BAA) under Compliance in the portal (Team or Enterprise), or email [email protected]. Signing the BAA makes two-factor authentication mandatory for every member; it does not unlock secure placement before the HIPAA cell opens. Once open, secure hosting is chosen per instance. Do not put patient data on a non-secure instance. See Secure hosting and the BAA and Compliance.

Deleting an instance keeps its data for your plan’s retention window, then purges the volume, the secrets, every backup (the newest backup included) and the point-in-time archives. Full erasure (purge without waiting for the window, with an erasure record in your audit log; a backup under Object Lock goes when its lock lapses, up to 35 days after the request) is temporarily unavailable: the API answers 503. Deleting needs a recent second factor. Retention per plan is in Backups, restore and PITR. An owner can also close the whole organization.

There is no one-step export yet. Run the engine’s own dump tool (pg_dump, mysqldump, mongodump and so on) against the instance over TLS. Data transfer out is billed as egress. Moving data in is covered by Migrations.

On the status page at databasezy.com/status, with component status per region and incident history. The AI assistant in the portal also checks current incidents when you ask it about a problem. Availability commitments are in the service level agreement.

A monthly plan fee, plus compute per running instance per hour, plus usage above the included allowances, plus add-ons. Start with Understanding your bill.

There is no live chat. Search, the AI assistant and support tickets are described in How to get help.

Search the help center or ask the assistant in the portal Help panel; if that does not solve it, open a support ticket from the portal (Help → Open a ticket) and include your organization id, the instance id and region if the question is about one database, and what you have already tried. Never paste passwords, connection strings with passwords, API keys or patient data (PHI) into a ticket. See How to get help.