About
Practice the disaster before it happens.
Every team has backups. Almost no team has ever restored one. That gap — between "we have backups" and "we know they work" — is where companies lose their data, their weekends, and sometimes their business. Firedrill exists to close it.
What we do, in one paragraph
Firedrill takes scheduled, encrypted, off-site backups of your Postgres database — then does the part everyone skips: it restores every backup onto a fresh, isolated Postgres instance, verifies the schema, the row counts, the indexes, and the data itself, measures how long recovery actually takes, and writes it all into a report your auditor will accept unedited. We're not a backup company that also verifies. We're a verification company that also stores your backups.
Why "Firedrill"
Buildings don't wait for a fire to find out whether the exits work — they run drills. Databases deserve the same discipline, but almost nobody has the time to restore a backup every day and check it. So we run the fire drill for you: on schedule, on real infrastructure, with the results in writing. When did you last run a fire drill on your database? With Firedrill, the answer is always "today."
How we hold ourselves to it
Proof over promises
We never ask you to trust that a backup works — we restore it on real infrastructure, run seven integrity checks, and show you the results. Every claim on this site is backed by a report you can read.
restore → verify → report · every backup, every time
The pipeline never grades its own homework
Every stage of our system heartbeats an independent external monitor. If anything goes silent — the scheduler, the backups, the drills — we get paged. And a canary database we own runs through the entire pipeline continuously, forever, so the whole path is exercised every few hours.
silence = alert · canary drilled every 6h
We can't touch your data
Firedrill connects with a read-only role and actively refuses credentials that can write. Backups are encrypted with per-project keys before they reach storage. This isn't policy — it's enforced by code, and it's tested in our CI on every change.
read-only enforced · AES-256-GCM before storage
Boring technology, on purpose
Postgres, plain workers, standard pg_dump archives you can restore anywhere without us. Your last line of defense should not be exciting. Portability is part of the promise: if Firedrill disappeared tomorrow, your backups would still restore with stock Postgres tools.
pg_dump custom format · restores with stock tooling
Who's behind it
Firedrill is built by a small, founder-led team that answers its own support email — the same people who designed the pipeline read the replies at info@runfiredrill.com. We keep the company the way we keep the software: small surface, high standards, nothing we can't personally stand behind.
See it work before you trust it.
Point us at any pg_dump file and get a drill report in minutes — free, no signup. That's the fastest way to understand what we do.