BackupDrill
Supabase backups you can prove restore
SubscriptionCLIOpen SourceDB2 impressionslaunches Oct 61 comment
Comments
>log in to commentHi DevHunt, I'm Super and I build BackupDrill. What got me started: most teams on Supabase have backups, and very few have ever tried restoring one. The first time I restore-tested a real project's dump into plain Postgres, one table was missing. pg_restore printed an error and carried on, and the error was buried in the role and schema warnings you learn to ignore with Supabase dumps. So BackupDrill does two things. It backs up the database, plus Storage files once you add their S3 keys, into a bucket you own (S3, R2, B2 or Wasabi). Then it restores the backup into a throwaway Postgres and checks that every table came back. Paid plans run that drill weekly and email you the report. The Free plan covers one project with weekly backups and a drill on the first one. The backup engine is an MIT CLI (github.com/backupdrill/cli) if you'd rather run it yourself. Happy to answer questions.
- Supabase backups with storage files
- Prove backups are restorable via scheduled drills
- Open‑source MIT engine (GitHub CLI)
- Backup to your own S3, Cloudflare R2 or Backblaze B2 bucket
- Free plan includes one restore drill
BackupDrill backs up Supabase databases and Storage files to your own S3-compatible bucket and verifies restores.
- for
- Supabase developers and teams needing verified backups.
- pricing
- freemium · free trial
- license
- MIT
Key features
- Full DB & Storage snapshots — Backs up PostgreSQL and all Storage files together into your own bucket.
- Automated restore drills — Runs weekly (or daily) restore tests in an isolated sandbox and emails a verification report.
- Open-source backup engine — MIT-licensed CLI you can audit or run yourself.
- No server hosting — Bytes stream through BackupDrill workers; snapshots never touch their disks.
- Granular project limits — Plans define number of projects, backup frequency, and storage caps per project.
Use cases
- Run daily verified backups of a production Supabase app and get email alerts on failures.
- Validate that Storage files are restorable after a schema change.
- Provide clients with PDF backup reports and proof of restore capability.
BackupDrill pricing
- Free$0/month1 project · Weekly backups · Up to 1 GB per project · One restore drill on first backup
- Solo$19/month/month5 projects · Daily backups · Weekly restore drills with email report · Up to 10 GB per project
- Team$49/month/month20 projects · Daily backups · Weekly restore drills with email report · Up to 25 GB per project
- Agency$99/month/month100 projects · Daily backups · Weekly restore drills with email report · PDF client reports
BackupDrill FAQ
Where are my backups stored?+
In the S3, R2, B2, or Wasabi bucket you provide; BackupDrill streams data through workers but never stores it.
How does BackupDrill differ from Supabase PITR?+
PITR costs $100/month per project and doesn’t include Storage files; BackupDrill provides verified daily snapshots of both DB and files starting at $19/month.
What access does BackupDrill need?+
It creates a read-only backup role via a short-lived Supabase token; no service-role key is required unless you restore Storage files.
What happens during a restore drill?+
The latest snapshot is downloaded to a temporary Postgres instance, verified against the manifest (checksums, table counts, non-empty tables, sampled file hashes) and a report is emailed.
Can I cancel or get a refund?+
Yes, cancel anytime; you keep existing snapshots. Payments are refundable within 14 days.
Summarized by DevHunt from backupdrill.com · Oct 1, 2026. Details may change; check the official site.