Back up Supabase, and prove it restores
Restore-tested backups of your Supabase Postgres, written to storage you control. Connect through the session pooler, pick a schedule, and every backup can prove it restores.
- Spin up a throwaway database
- Restore the backup
- Check the data came back 48 of 48 tables
- Delete the throwaway database
A second copy, outside Supabase
An off-site backup is the one you can still reach when something goes wrong with the platform or the account. Norcube keeps it outside Supabase, in storage you control, and proves it restores.
Off-site, in storage you control
Norcube runs a full pg_dump on your schedule and writes the encrypted archive to Norcube-managed storage in Frankfurt or to your own S3-compatible bucket.
Proven to restore
Every backup can be restore-tested: Norcube restores it into a throwaway database and confirms your schemas, tables and rows come back.
Yours, in a standard format
Download any backup and restore it with standard Postgres tools, independent of Norcube. No proprietary format, no lock-in.
Connect Supabase, step by step
The Supabase-specific settings, from the connection string to network access. Everything after that is the standard Protect form: schedule, retention and restore testing.
Open your project's Connect panel
In the Supabase dashboard, open your project and click the green Connect button in the project header. It only shows on a project's pages, not on the organization overview.
Choose the session pooler
Open the connection string option and set Connection method to Session pooler. The direct host is IPv6-only unless you've bought Supabase's IPv4 add-on, and the transaction pooler on port
6543doesn't work withpg_dump.Copy the string and add your password
It looks like
postgresql://postgres.<project-ref>:[YOUR-PASSWORD]@aws-0-<region>.pooler.supabase.com:5432/postgres. Replace[YOUR-PASSWORD]with your database password.Paste it into Norcube with SSL required
Choose Protect a database, pick PostgreSQL, paste the string and set SSL mode to
require. Then pick a schedule, retention and how often to restore-test.Allow Norcube's IP if you restrict access
A new Supabase project accepts the connection with just the password. If you've turned on Supabase Network Restrictions, add Norcube's egress IP
18.196.207.101to the allowed list.
What Norcube adds
Restore testing
Prove each backup restores, not just that the dump ran. A Passed badge per backup and a restore-health score per database show recoverability at a glance.
Failure and missed-backup alerts
Get notified when a backup fails, a restore test can't confirm your data, or a schedule silently stops. By email, Slack or a signed webhook, on every plan.
Your own bucket
Keep backups in Norcube-managed storage in Frankfurt, or in your own Amazon S3, Cloudflare R2, Backblaze B2, Wasabi or MinIO bucket.
Standard archives
Every backup is a standard pg_dump archive, gzip-compressed by default. Download it any time.
Supabase backups, answered
The questions that come up when backing up Supabase. The full guide is in the docs.
Which Supabase connection string should I use?
aws-0-<region>.pooler.supabase.com:5432). The direct connection is IPv6-only without Supabase's IPv4 add-on, and Norcube connects over IPv4. The transaction pooler on port 6543 is built for short-lived queries and doesn't work with pg_dump.Why does a restore test mention vault and pgsodium?
vault and the pgsodium it builds on, that only exist on Supabase's platform. They aren't your application data and Supabase recreates them, so a restore test notes their absence as expected and still records a clean Passed. It proves what matters: your schemas, tables and rows restore.Do I need to allowlist an IP address?
18.196.207.101, the single address Norcube connects from.Can I restore a backup without Norcube?
Your Supabase data, backed up and tested
Start on the Free plan. No credit card required. Connect Supabase, pick a schedule and let the first restore test prove it.
- Free plan
- No credit card
- Standard formats
- Restore-tested