Quickstart: hosted Supabase backups

Six steps to a Supabase project that backs itself up into a bucket you own: the database, plus Storage files once you add the project’s Storage S3 keys. Restore drills run on a schedule, and you get an email when a backup or drill fails. Prefer to run it yourself? Use the open-source CLI instead.

01

Create an account

Sign in at app.backupdrill.com/login. The same page also creates new accounts. No credit card: every new account starts on the Free plan and stays there unless you subscribe.

02

Connect your Supabase project

Click Connect Supabase. You authorize BackupDrill on the organization you pick, then choose the project. The consent screen shows two scopes: Database (read + write) and Projects (read). BackupDrill creates a dedicated read-only backup role in it (named backupdrill_…, with BYPASSRLS so pg_dump can read RLS-protected tables) and tests the connection from the network your backups run from. No database password. The authorization token lives only in a short-lived cookie in your browser (at most 10 minutes), is deleted after the connection is set up successfully (otherwise it expires within 10 minutes), and is never saved on our servers. We store only that role’s connection string, sealed-box encrypted. The project page shows the three-line SQL that revokes the role.

Two prerequisites: the project must run Postgres 16 or newer (creating a BYPASSRLS role on 15 needs a superuser, which hosted projects don’t have), and if you use Supabase Network Restrictions, allow BackupDrill’s backup IP first. The connection test tells you if it’s blocked.

Prefer not to authorize? Choose Run the SQL yourself: paste the Session pooler string exactly as Supabase shows it (leave [YOUR-PASSWORD] as is), run the generated three-line SQL in the Supabase SQL Editor, and click I ran it. You get the same role and the same connection test. The password is generated in your browser and, like every credential, stored sealed-box encrypted for the backup worker.

Or paste a connection string (the classic path, needs your database password): use the Session pooler string from the Connect button at the top of the Supabase dashboard, not the Direct one, which resolves to IPv6 only.

On that path the postgres user works as-is: it owns your tables, so dumps get past row-level security. A least-privilege backup_reader role is an advanced option with two catches. pg_dump needs select on sequences too, and it errors on any RLS-enabled table it can’t bypass, so the role only works if your schema has no RLS tables:

-- replace <generate-a-strong-password> before running
create role backup_reader with login password '<generate-a-strong-password>';
grant usage on schema public to backup_reader;
grant select on all tables in schema public to backup_reader;
grant select on all sequences in schema public to backup_reader;
alter default privileges in schema public grant select on tables to backup_reader;
alter default privileges in schema public grant select on sequences to backup_reader;

03

Choose where backups go

Backups are written to storage you own, never to ours. The quickest is Google Drive: click Connect Google Drive and allow access in the Google window. There are no keys to create, and BackupDrill can only see the files it creates in your Drive. Drive backups cover the database only; Storage files need a bucket.

Or use a bucket you own on S3, R2, or B2 and provide the endpoint, region, bucket name, access key ID, and secret access key. No bucket yet? The bucket setup guide has exact click-paths for each provider. For Cloudflare R2:

Endpoint: https://<account>.r2.cloudflarestorage.com
Region:   auto

R2 is addressed path-style: the bucket name goes in the request path, so the endpoint stays the same for every bucket in your account. The snapshots are in a bucket you own, so they stay yours. If you cancel, they still restore through the restore paths or the RECOVERY.md saved next to each backup.

04

Pick your schedule

How often backups and drills run depends on your plan:

PlanPriceBackupsDrillsNotes
Free$0WeeklyOne-time1 project
Solo$19/monthDailyDailyEmail alerts
Team$49/monthEvery 12 hoursDailyFor small teams
Agency$99/monthEvery 12 hoursDailyClient PDF reports

05

Your first backup runs within a few minutes

There’s nothing else to configure. The first backup starts within a few minutes of connecting, and later runs follow your plan’s schedule. Each run writes a pg_dump in custom format and a checksummed manifest into your Drive folder or bucket. In a bucket, it also copies your Storage files once you add the project’s Storage S3 keys on the project page. The tree below shows exactly what goes into a bucket.

06

Drills prove it restores (daily on paid plans; once on Free)

Paid plans include daily drills, and Free gets one on your first backup. A drill restores your latest snapshot into a throwaway Postgres and verifies it: archive sha256, pg_restore completes, post-data objects (indexes and constraints) applied, table count matches, no missing tables, populated tables are non-empty, and row counts match the backup table by table. Paid plans email you a report every week (Free gets one after its first drill), so when you need an actual restore, you have recent drill results showing the snapshot restored in testing.

What lands in your bucket

<prefix>/<project>/<timestamp>/
  ├── dump.pgcustom              # pg_dump --format=custom (public schema by default)
  ├── auth.dump                  # Supabase Auth users and sign-in identities (on by default)
  ├── storage/<bucket>/<key>     # your Storage files (if Storage keys are added)
  └── manifest.json              # schemas, tables, estimated row counts, file list, sizes + sha256

Plain pg_dump output and plain files. There is no proprietary format, and you don’t need us to read them.

One note on retention: the console rotates its snapshot records per your plan, but we never delete objects from your bucket, because a backup tool with delete permissions is a bigger risk than the storage bill. Old folders pile up until you add a lifecycle rule, which is a one-time setup. Each destination guide (R2, S3, B2) shows the setup. Keep the expiry longer than your plan’s retention so a paused project can’t age out of its last good snapshot.

Free covers one project: weekly backups into your bucket, plus a restore drill on the first one. No credit card, no expiry.

Start free