ARCHIVE / 01 — OFF-SITE POSTGRES BACKUPS

Your database, sealed off-site. Every hour.

Supabase Pro keeps 7 days of backups — on Supabase's own infrastructure. OffsiteDB dumps, encrypts, and ships every snapshot to a bucket you own, on a schedule you set, with a restore command you can run at 3 a.m. with shaking hands.

14-day free trial · no card required · works with any Postgres connection string

BACKUP LEDGER — LAST 24HLIVE
04:00:11prod-api · supabase2.4 GBSEALED
04:00:09billing-core · neon812 MBSEALED
03:00:14prod-api · supabase2.4 GBSEALED
03:00:08analytics-wh · railway6.1 GBSEALED
02:00:12prod-api · supabase2.4 GBSEALED
02:00:07billing-core · neon809 MBSEALED
01:00:15staging-db · render411 MBSEALED
01:00:10prod-api · supabase2.3 GBSEALED
00:00:13analytics-wh · railway6.0 GBSEALED
00:00:06billing-core · neon807 MBSEALED
04:00:11prod-api · supabase2.4 GBSEALED
04:00:09billing-core · neon812 MBSEALED
03:00:14prod-api · supabase2.4 GBSEALED
03:00:08analytics-wh · railway6.1 GBSEALED
02:00:12prod-api · supabase2.4 GBSEALED
02:00:07billing-core · neon809 MBSEALED
01:00:15staging-db · render411 MBSEALED
01:00:10prod-api · supabase2.3 GBSEALED
00:00:13analytics-wh · railway6.0 GBSEALED
00:00:06billing-core · neon807 MBSEALED
WORKS WITH  SUPABASE  ·  NEON  ·  RAILWAY  ·  RENDER  ·  FLY.IO  ·  RDS  ·  ANY POSTGRES  ·  WORKS WITH  SUPABASE  ·  NEON  ·  RAILWAY  ·  RENDER  ·  FLY.IO  ·  RDS  ·  ANY POSTGRES  ·  
THE UNCOMFORTABLE PART / 02

“The platform has backups” is not a backup strategy.

Platform snapshots live in the same account, same region, same blast radius as your database. They protect the platform from hardware failure. They do not protect you from:

RISK — A

The Friday-night migration

A bad DROP CASCADE, a botched RLS change, an ORM auto-migration that ate a column. Platform PITR windows are short — and on free tiers, nonexistent.

RISK — B

The locked account

Billing failure, compromised credentials, a platform suspension. If your only backups live inside the account you just lost, you don't have backups.

RISK — C

The compliance question

“Where are your off-site backups and what's your tested restore time?” Every SOC 2 questionnaire, every serious customer. You need a real answer.

PROCEDURE / 03

Three minutes to your first sealed snapshot.

STEP 01

Paste a connection string

Any postgres:// URL — your Supabase pooler URL, a Neon branch, RDS. A read-only role is all OffsiteDB needs. We test the connection before saving and encrypt the credential at rest with AES-256-GCM.

$ postgres://readonly:•••@db.xyz.supabase.co:5432/postgres
 connected — postgres @ PostgreSQL 16.4
STEP 02

Point it at your bucket

AWS S3, Cloudflare R2, or any S3-compatible store. Your data lands in infrastructure you control, encrypted before it leaves the worker. We never hold the only copy — by design.

s3://acme-backups/offsitedb/
  2026-06-09T04-00-11_bk_91f3.dump.gz.enc
  2026-06-09T03-00-14_bk_88c1.dump.gz.enc
STEP 03

Restore with one command

Every snapshot is a standard pg_dump custom-format archive. Download it decrypted from the dashboard, or pull from your own bucket — then pg_restore and you're back.

$ pg_restore -d $NEW_DATABASE_URL \
      --clean --if-exists prod-api_2026-06-09.dump
 restored 184 tables, 9.2M rows
TARIFF / 04

Cheaper than one hour of data-loss panic.

Every plan ships the full engine: encrypted dumps, your own storage, failure alerts, one-command restores. Plans scale with how much there is to protect.

Hobby
$9 / month
  • Databases 1
  • Cadence Daily
  • Retention 30 days
  • Own S3 / R2 bucket
  • Failure alerts
Start trial
Business
$79 / month
  • Databases 25
  • Cadence Hourly
  • Retention 1 year
  • Own S3 / R2 bucket
  • Priority support
Start trial
LAST CALL / 05

You will need a backup once.

That day, this is the best $29 you ever spent. Set it up before you need it.

Seal my first snapshot →