# ReviveDB

> Independent, off-platform backup and disaster recovery for Supabase projects. Each backup
> captures the PostgreSQL database and Auth data, Storage object bytes, Edge Function bundles
> and supported project configuration as one recovery point. Every database backup is
> automatically restore-tested in an isolated PostgreSQL instance. Schema, rows, table grants
> and RLS are compared against a capture-time inventory.

Backup data is stored in the European Union.

## Scope and limits

- Supabase is the only supported source. Connection is through Supabase OAuth; there is no
  connection-string form, and other PostgreSQL hosts are not supported.
- The OAuth grant includes Database write permission, used to create and drop a temporary
  login per job. The backup login itself is read-only; "read-only" describes that login,
  not the OAuth authorization.
- Secret values (Edge Function secrets, Vault contents) are never copied.
- Database dumps are restore-tested. Storage object bytes and Edge Function bundles are verified by
  SHA-256 hash, not by restore.
- European storage only. No bring-your-own bucket, no self-hosting, no sub-daily schedules.

## Key pages

- [ReviveDB](https://revivedb.dev/): Product overview, what a recovery point contains, pricing and FAQ.
- [Supabase backup](https://revivedb.dev/supabase-backup): What Supabase native backups cover and what they leave out.
- [Supabase backup verification](https://revivedb.dev/backup-verification): How every database backup is restored, compared and reported, with explicit verification boundaries for other project components.
- [Supabase backup tools compared](https://revivedb.dev/supabase-backup-tools): Comparison of the available Supabase backup options, with sources and check dates.
- [Alternatives](https://revivedb.dev/alternatives): ReviveDB compared with SimpleBackups, SnapShooter, Supabase PITR and a self-managed pg_dump.
- [Supabase disaster recovery](https://revivedb.dev/supabase-disaster-recovery): Restoring a Supabase project when the original is gone.
- [Features](https://revivedb.dev/features): Backup coverage and the four-step verification pipeline.
- [Pricing](https://revivedb.dev/pricing): Plans, limits and prices in euro, VAT included.
- [Security](https://revivedb.dev/security): Credential handling, encryption and data residency.
- [About the author](https://revivedb.dev/about): Who builds ReviveDB and how product and editorial claims are checked.
- [Backup terms](https://revivedb.dev/glossary): What a restore test is, and what a recovery point contains.

## Documentation

- [Back up your first Supabase project](https://revivedb.dev/docs/getting-started): Connect Supabase, choose a project and create your first verified recovery point.
- [Backup coverage and limitations](https://revivedb.dev/docs/backup-coverage): Components included in a recovery point, manual recovery work and current platform limits.
- [How backup verification works](https://revivedb.dev/docs/verification): The restore and comparison checks required for a verified recovery point.
- [Restore a recovery point](https://revivedb.dev/docs/restores): Choose between an in-place rollback and recovery into a separate empty Supabase project.
- [Security, regions and retention](https://revivedb.dev/docs/security-retention): Credential encryption, storage regions, retention rules and deletion behavior.

## Articles

- [How to verify a Supabase backup can be restored](https://revivedb.dev/blog/verify-backup-is-restorable): A green backup job proves a file was written. Proving it restores takes four specific checks.
- [How to back up Supabase with the CLI](https://revivedb.dev/blog/supabase-cli-backup-guide): The three supported dump commands, the restore check that matters, and the project components a database export does not contain.
- [How to back up Supabase on the free plan](https://revivedb.dev/blog/backup-supabase-free-plan): Free projects receive no automatic backups at all. Here are three ways to get one, and what each leaves out.
- [How to download a Supabase database backup](https://revivedb.dev/blog/download-supabase-database-backup): Create a portable PostgreSQL dump and record the Storage, Functions and settings that are not inside it.
- [How long should you keep Supabase backups?](https://revivedb.dev/blog/supabase-backup-retention): Choose retention from detection time, recovery needs and legal limits, not only storage cost.
- [Supabase backup without sharing the database password](https://revivedb.dev/blog/supabase-backup-without-database-password): How ReviveDB uses a unique read-only Postgres login for each backup while keeping the broader Supabase OAuth permission explicit.
- [How to restore a Supabase backup to a new project](https://revivedb.dev/blog/restore-supabase-backup-new-project): A safe Supabase recovery keeps the source intact until the new project has passed database, Auth, Storage and application checks.
- [Supabase backup and restore checklist](https://revivedb.dev/blog/supabase-backup-restore-checklist): A practical recovery sequence for the database, Auth, Storage, Edge Functions, settings and external services.
- [What pg_dump leaves out of a Supabase backup](https://revivedb.dev/blog/pg-dump-cron-is-not-a-backup): A scheduled pg_dump protects the database. Supabase Storage files, Edge Functions and restore testing need separate work.
- [Do Supabase backups include Storage files?](https://revivedb.dev/blog/do-supabase-backups-include-storage): No. Supabase database backups keep Storage metadata, not the files. Here is what to copy and how to check it.
- [Supabase PITR pricing: 7, 14 and 28 days](https://revivedb.dev/blog/supabase-pitr-cost): Current Supabase PITR prices, compute requirements and the parts of a project that PITR does not cover.
- [What Supabase backups cover and what they do not](https://revivedb.dev/blog/supabase-native-backups-vs-revivedb): Supabase backups are useful for database recovery. Storage files, portability and project deletion need a separate plan.
- [Supabase OAuth cannot read Realtime or Storage configuration](https://revivedb.dev/blog/supabase-config-backup-oauth-limits): Auth and PostgREST configuration work through OAuth. Realtime and Storage configuration currently return HTTP 401.
- ["Sign in with Supabase" doesn't work yet: GET /v1/profile rejects OAuth tokens](https://revivedb.dev/blog/sign-in-with-supabase-oauth): Tested again on 5 August 2026: Supabase Management API OAuth tokens still get HTTP 401 from GET /v1/profile, so an app cannot identify who authorized it.
- [How to test the database layer of a Supabase backup](https://revivedb.dev/blog/how-to-test-postgresql-backup): Restore a PostgreSQL dump into a clean target, fail on errors and compare the result with the source inventory.
- [Supabase backups vs point-in-time recovery (PITR): differences and pricing](https://revivedb.dev/blog/supabase-backups-vs-pitr): Daily backups give fixed database restore points. PITR gives more precise ones. Neither includes Storage files or an off-platform copy.
- [How to back up a Supabase project](https://revivedb.dev/blog/how-to-back-up-supabase-properly): Back up Postgres, Auth, Storage files, Edge Functions and the settings you will need during a restore.

## Contact

- [Contact and support](https://revivedb.dev/contact)