Supabase · verified backups
Supabase backups that live outside Supabase — and provably restore.
Supabase's built-in backups are good. They're also stored by the same platform, under the same account, with the same failure modes. Firedrill gives you an independent copy, encrypted client-side, restore-tested after every backup.
Free tier keeps no backups at all
Supabase's free plan has no automated backups; Pro keeps daily backups with limited retention. If a bad migration lands on Friday and you notice the data damage 10 days later, the clean copy may already be gone.
One account, one blast radius
If your Supabase account is compromised, suspended, or hit by a billing mishap, backups stored inside that account go with it. Off-platform independence is the whole point of a backup.
Have you ever actually restored one?
Downloading a backup is not restoring a backup. Firedrill restores every backup onto a fresh Postgres of the same major version and runs schema, row-count, index (amcheck), and query checks — then shows you the report.
Frequently asked
Does this need write access to my Supabase database?
No — Firedrill refuses writable roles. You create a read-only role with the SQL snippet we provide (runs in the Supabase SQL editor) and connect with that.
Does it work on the Supabase free tier?
Yes. Firedrill connects like any Postgres client over the direct connection string or session pooler. Free-tier projects — the ones with no native backups — are exactly who needs this.
What about Supabase Storage buckets?
V1 covers the Postgres database (which includes your auth users). Storage-bucket backup is on the roadmap — we'd rather tell you that honestly than pretend.