Supabase backups that include Storage files — and prove they restore.

In your own S3, R2, or B2 bucket — you bring the bucket, you hold the keys. During backups the bytes stream through our workers and are never written to our disks; a restore drill downloads your snapshot into an isolated temporary sandbox that is destroyed as soon as verification finishes. If you cancel tomorrow, every snapshot 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.

For backups and drills: click Connect Supabase and authorize two scopes on the organization you pick — Database (read + write) and Projects (read). We use them once, to list your projects and create a read-only backup role named backupdrill_… (with BYPASSRLS, so pg_dump can read RLS-protected tables); the authorization token is held only in a short-lived browser cookie (at most 10 minutes), deleted after the connection is set up successfully (otherwise it expires within 10 minutes), and never persisted on our servers; only that role’s connection string is stored, sealed-box encrypted. Prefer not to authorize? Run the same three-line SQL yourself, or paste a Session Pooler connection string. We never ask for your service_role key or dashboard access. Recovery is the one exception: uploading Storage files back into a fresh project needs that project's service-role key, which you supply at restore time and we never store. Credentials are stored sealed-box encrypted.

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.

The Free plan, with no credit card and no time limit: one project, weekly backups into your own bucket, three snapshots of console history, and one restore drill on your first backup — the same drill paid plans run, so you see the proof before you decide anything. Every snapshot stays in your bucket whether you ever subscribe or not. Paid plans add daily backups, a restore drill every week, longer history, and more projects; your first monthly subscription is $1 for its first month, then full price (Solo $19/month, Team $49/month, Agency $99/month). Cancel anytime.

Sign up at app.backupdrill.com — no credit card. Click Connect Supabase, pick the project, and point us at your own S3, R2, or B2 bucket — no database password needed (that path needs Postgres 16 or newer; older projects can paste a connection string instead). Your first backup runs automatically within a few minutes of connecting, and the free restore drill follows it.