Blog
Backups, restores and the boring parts of not losing data.
Guides written from running backups for Supabase projects every day. Vendor-neutral where it can be, honest about VaultKeep where it can't.
- How to back up a Supabase database: every option, honestly compared
Built-in daily backups, point-in-time recovery, pg_dump by hand, the Supabase CLI, and third-party services — what each one covers, what it costs, and the gaps nobody mentions.
- Supabase Free tier has no backups. Here's a free fix in ten minutes
A GitHub Actions workflow that pg_dumps your Supabase database every night, encrypts it, uploads it to any S3-compatible bucket, and test-restores it — with no servers and no bill.
- A backup you've never restored is just a hope: how to test-restore Postgres properly
Checksums prove the file is intact. Only a restore proves it works. Here is the four-step drill we run every week, why row counts matter more than table counts, and how to do it yourself.
- Supabase backups for SOC 2: the questions auditors actually ask
What a SOC 2 auditor wants to see about your database backups, why Supabase's built-in backups only answer half of it, and a checklist you can finish in a week.
- Backing up Supabase Storage buckets, the part your database backup skips
User uploads live in Storage, not Postgres, and no Supabase backup plan includes them. How Storage is laid out, how to copy it with rclone or the AWS CLI, and how to keep the copy incremental and encrypted.