An alternative to a pg_dump cron job
Claims checked against vendor documentation on 10 August 2026.
The short answer
A scheduled pg_dump gives you a portable logical backup with full control and no licence cost, and for a database-only project it is a legitimate answer. What it does not do is cover Supabase Storage objects, Edge Functions or project configuration, and it does not tell you whether the dump can actually be restored. Those gaps are what a managed service is being paid to close.
Keep your own pg_dump when
You already run reliable scheduled jobs, and someone owns that pipeline.
- Complete control over format, schedule and destination, at no licence cost.
- You take on the monitoring, the alerting, the credential rotation and the restore drills.
- Most silent backup failures are a cron job that stopped months earlier and told nobody.
Choose ReviveDB when
You would rather not own that pipeline.
- Runs the schedule and captures Storage objects and Edge Functions alongside the database.
- Restores every dump into isolated PostgreSQL, so a broken backup surfaces immediately.
- No production password in a script: connects through Supabase OAuth with a temporary read-only login.
Side by side
| Option | pg_dump on a schedule | ReviveDB |
|---|---|---|
| PostgreSQL database | Yes | Yes |
| Auth users and identities | Partial | Yes |
| Storage object bytes | No | Yes |
| Edge Function bundles | No | Yes |
| Project configuration1 | No | Partial |
| Restore-tested automatically2 | No | Yes |
| Copy survives project deletion | Yes | Yes |
| Backup can be downloaded | Yes | Yes |
| Self-hostable | Yes | No |
| Bring your own bucket | Yes | 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.