Section III · Databases Encrypted Postgres backups Read the changelog
dbcrate

Databases

What dbcrate backs up today, and what is next

PostgreSQL is what works today. The agent is built so that adding other engines later is a small piece of work, not a rewrite.

❦Supported today❦

PostgreSQL

13 · 14 · 15 · 16 · 17 · 18

Logical backups via pg_dump, custom format. The agent fetches a matching dump binary for the server’s major version on demand, from a signed registry, so you do not have to install anything alongside it.

Available|Self-hosted Postgres|Logical, v1

❦Next for Postgres❦

Point-in-time recovery

base backup + WAL

Continuous WAL streaming on top of the scheduled base backup. Recover to a specific second by picking a base and replaying WAL up to a timestamp or LSN. Target RPO is measured in seconds, set by how aggressively WAL is shipped — not by the daily schedule. Lands after verified restores.

Next|Postgres 13–18|Physical, continuous

❦Other engines, on the roadmap❦

The agent is engine-agnostic. Each engine ships as a small plug-in that knows how to dump, how to restore, and (eventually) how to verify. We are not committing dates — we would rather ship one engine well than promise four. PITR for Postgres comes first.

MySQL & MariaDB

planned

Logical backups via mysqldump with single-transaction and triggers, with room for physical backups for the larger end later on.

Planned

MongoDB

planned

Logical via mongodump, with index metadata captured separately.

Planned

Redis & Valkey

planned

RDB snapshots streamed off a replica, with optional AOF for installations that ask for it.

Planned

ClickHouse, SQLite, and others

considered

On the longer list. If you operate one of these and want it on the page above, write to us — demand pulls work forward.

Considered

❦How an engine gets added❦

The agent is engine-agnostic. The engine-specific bits live in a small plug-in that knows three things: how to dump, how to restore, and how to verify. We will publish the contract when the second engine is on staging and the shape has stopped moving.

For each engine we ship, the commitment is:

  • A logical backup path that runs without elevated privileges on the host.
  • A clear list of what is captured, and what is not.
  • End-to-end encryption to the same organisation key as Postgres.
  • A migration plan from the previous version of the plug-in.

If the engine you operate is not above and you would like it to be, write to us. We are reading.

Engine / capability Status Method Notes
PostgreSQL 13 to 18 Available pg_dump · custom Self-hosted; agent fetches matching binary
Postgres — verified restores Roadmap scheduled clean restore Paid plans
Postgres — PITR Next after verify base backup + WAL streaming RPO in seconds
MySQL / MariaDB Planned mysqldump (later: physical) No date
MongoDB Planned mongodump No date
Redis / Valkey Planned RDB · AOF No date
ClickHouse / SQLite / others Considered tbd Demand-driven