An alternative to Supabase PITR
Claims checked against vendor documentation on 10 August 2026.
The short answer
Supabase PITR and an off-platform backup solve different problems, so this is not strictly an either-or. PITR offers recovery with up to seconds of granularity, which is useful after a bad migration, but its snapshots stay with the project and are not directly downloadable. It costs 100 dollars per month per 7 days of retention. ReviveDB keeps a copy outside Supabase that survives project deletion, but its shortest schedule is daily.
Keep PITR when
Your main risk is a bad write, not losing the project.
- Choose a recovery point with up to seconds of granularity after a bad migration or accidental delete.
- No daily backup can match that precision.
- Costs 100 dollars per month per 7 days of retention, on top of your plan.
Add ReviveDB when
You could lose access to the project itself.
- PITR snapshots are not directly downloadable and are removed with the project.
- Recovery points are stored in European object storage, separate from Supabase.
- Covers Storage objects and Edge Functions, which PITR excludes entirely.
- Many teams keep PITR for fast rollback and add ReviveDB for everything else.
Side by side
| Option | Supabase PITR | ReviveDB |
|---|---|---|
| PostgreSQL database | Yes | Yes |
| Auth users and identities | Yes | Yes |
| Storage object bytes | No | Yes |
| Edge Function bundles | No | Yes |
| Project configuration1 | No | Partial |
| Restore-tested automatically2 | No | Yes |
| Copy survives project deletion | No | Yes |
| Backup can be downloaded | No | Yes |
| Self-hostable | No | No |
| Bring your own bucket | No | No |
- 1Supabase does not expose every project setting to OAuth applications, so no third-party tool can capture all of it. ReviveDB scores this partial because it captures the settings Supabase does expose, never copies secret values, and lists whatever it could not capture as named manual steps in the recovery report. A tool claiming full configuration coverage is working within the same platform limit.
- 2Restore-tested means the database dump is restored into an isolated PostgreSQL instance and compared against a capture-time inventory, on every backup. For ReviveDB this covers the database. Storage object bytes and Edge Function bundles are verified by SHA-256 hash instead. Where a vendor does not document a restore test, this is recorded as not documented rather than as an absence.
Sources
Claims checked against vendor documentation on 10 August 2026.
See all options side by sideCreate your first recovery point free.
Connect one Supabase project with OAuth. ReviveDB starts the first backup and shows what can be recovered. No card required.