BackupDrill Docs
BackupDrill backs up your Supabase database to Google Drive or your own S3, R2, or B2 bucket. With a bucket, it also backs up the Storage files a database restore leaves behind, once you add the project’s Storage S3 keys. Then it runs scheduled restore drills that check the backup restores. These guides cover setting up the hosted service, running the open-source CLI yourself, and restoring your data when something goes wrong.
Quickstart
Connect a Supabase project to the hosted service: Session pooler string, your own bucket, a schedule, and drills that prove restores work.
CLI
The open-source backupdrill CLI: install, configure, and run backup, estimate, drill, and restore yourself — plus what it costs in Supabase egress.
Restore & recovery
The bad-day page. Four ways back: the console wizard (database only), the CLI (database and Storage files), your own artifacts, or raw pg_restore.
Bucket setup
Create a bucket and S3 credentials on Cloudflare R2, AWS S3, or Backblaze B2 — exact click-paths and how each value maps to the project form.
Coverage
The honest boundary: what a backup contains, what a drill proves, and what is not covered: Auth sessions, Edge Functions, platform config.
Drill status API
A public, read-only link that returns whether a project's latest restore drill passed, for status pages, scripts and README badges. Off by default.
Bitwarden Secrets Manager
Keep the CLI's connection string and bucket keys in Bitwarden Secrets Manager and run backups with bws run or Bitwarden's GitHub Action.