PostgreSQL · verified backups
If it speaks Postgres, we back it up — and prove it restores.
RDS, a VPS, a homelab, a managed provider we've never heard of: if Firedrill can connect with a read-only role, you get scheduled encrypted backups and a real restore test for every single one.
Your cron job has no one watching it
The classic failure: pg_dump cron silently broken for months — wrong password after a rotation, full disk, a TLS change. Firedrill heartbeats every scheduled run to an independent monitor. Silence raises an alert; nothing fails silently.
pg_dump version mismatches bite at restore time
Dumping a Postgres 16 server with a 12-era pg_dump, or restoring with the wrong pg_restore, fails at the worst moment. Firedrill always uses version-matched tools — and because we actually restore every backup, a mismatch can't hide.
Retention policy by hope
"We keep some dumps in a bucket" is not a retention policy. Firedrill enforces daily/weekly/monthly (GFS) retention automatically and never prunes your most recent verified backup.
Frequently asked
Which Postgres versions are supported?
Majors 14 through 17, with version-matched pg_dump/pg_restore binaries. The server version is detected automatically at connect time.
Do you support WAL archiving / PITR?
Not in v1 — Firedrill does verified logical backups (pg_dump custom format). PITR complements, not replaces, restore-tested logical archives.
Where are backups stored?
Cloudflare R2, encrypted client-side with AES-256-GCM using a per-project key before upload. Your data is never stored or logged in plaintext.