Automated Supabase backups, proven to restore

On Pro and above, yes: one backup a day, kept for 7 days (14 on Team, up to 30 on Enterprise), stored inside the project and deleted with it. On the Free plan there are no scheduled backups you can restore or download — only the snapshot Supabase takes when it pauses an idle project. BackupDrill keeps copies in your own bucket on a schedule — weekly on Free, daily on paid plans — and runs restore drills to show they come back.

No. Supabase’s backups, daily and PITR alike, cover the database only, and the database holds just the metadata for your Storage objects. Restoring brings back pointers to files that may no longer exist. BackupDrill puts Storage files in the same snapshot as the database once you add the project’s Storage S3 keys.

Only on projects still on the older logical backup process. Projects on physical backups — Postgres 15.8.1.079 or newer, or any project with PITR — can’t download them from the dashboard. BackupDrill writes standard pg_dump files to your bucket, so you can restore them anywhere with pg_restore.

The Free plan has no backups you can rely on, so you need your own copy. Run pg_dump yourself (a GitHub Actions schedule can automate it), or use BackupDrill’s Free plan: one project up to 1 GB, weekly backups into your own bucket, and a restore drill on your first backup — no credit card, no time limit, and every snapshot stays in your bucket whether you subscribe or not. Paid plans add daily backups and a drill every week: first month $1, then $19/month. Cancel anytime.

In your own cloud storage — a bucket you create on Amazon S3, Cloudflare R2, Backblaze B2 or Wasabi — so your data stays private and under your control. We don’t keep a copy: backups stream straight to your bucket without touching our disks, and a restore drill runs in a temporary sandbox that’s deleted when the check finishes. If you cancel, every backup is still yours.

PITR gives you point-in-time recovery for $100/month per project — and still doesn’t cover Storage files. We sell verified daily snapshots of your database and Storage files together — Storage joins the same snapshot once you add its S3 keys — starting at $19/month. If you need sub-24h recovery points, run both: they solve different problems.

We download your latest snapshot into an isolated temporary sandbox, provision a temporary Postgres, restore into it, and verify it against the backup manifest: archive sha256, pg_restore completes, table count matches with no missing tables, populated tables restored non-empty, and — when the snapshot includes Storage files — sampled sha256 checks on them. We measure the wall-clock restore time, then destroy the sandbox and the instance. The report lands in your inbox.

Click Connect Supabase and approve Database (read and write) and Projects (read) access once. We use it to create a read-only backup role in your project (it can read RLS-protected tables, which a full backup needs), then discard the token; only that role’s connection string is kept, sealed-box encrypted. No database password, no service_role key. Prefer not to authorize? Run a three-line SQL snippet or paste a connection string instead. Restoring Storage files into a new project is the one exception: it needs that project’s service-role key, which you enter at restore time and we never store.

Sign up free — no credit card. Click Connect Supabase, pick the project, and point us at your own bucket. Connect Supabase needs Postgres 16 or newer; older projects paste a connection string instead. Your first backup runs within a few minutes, and the free restore drill follows it.