Automated, encrypted backups for Supabase — with proof they restore.

Most backup scripts and cheap competitors only prove they can write a file. SupaBackup runs a real, isolated restore of your database every week and diffs the object counts — so "backed up" means "restorable," not just "a file exists somewhere."

Verified restore tests, weekly

Every backup is restored into a fresh, isolated Postgres instance — same major version, same Supabase extensions — and the restored object count is compared against the original dump's manifest. A silently dropped table (missing extension, unsupported type) fails the test instead of passing quietly.

Database + Storage buckets, together

Supabase's own backups don't cover Storage bucket file bytes. SupaBackup backs up both the database and the actual files in your Storage buckets, and restores them as one paired unit — so you never end up with valid-looking URLs that 404.

Encrypted end-to-end

Database dumps are age-encrypted, bucket files go through an encrypted rclone crypt layer. Your connection strings and storage credentials are encrypted at rest and never logged.

Honest failure reporting

If a restore can't be fully verified — an extension we can't install, an unmapped Postgres version — we say so explicitly instead of reporting a false pass.

Who it's for

Teams running production on Supabase who want a backup they can actually trust in an incident — not a cron job that's never been tested against a real restore.

Pricing

$12/month

One plan, per project. Daily encrypted backups, weekly verified restore tests, Storage bucket sync, and email alerts on failure.