Restore verification must check more than database row counts
ReviveDB says it restores every Supabase database backup into isolated PostgreSQL and compares it with an inventory from the same snapshot, including constraints, grants and row-level security policies. Storage files and Edge Function bundles receive hash checks, not execution tests. The distinction matters: a readable database dump and matching row counts alone cannot show that permissions or an application’s recovery are correct.
ReviveDB · PostgreSQL · Oct 28, 2026
Why it matters
The documented method gives database teams specific evidence to ask for when assessing a backup system.
More context
The October 28 announcement supports Supabase on PostgreSQL 17. The free tier covers one project with weekly backups; daily backups require a paid plan. Inspect a report and rehearse recovery on a disposable project before trusting it.
Keep in mind
Checks do not run your application or copy secret values. ReviveDB also disclosed a hosting-provider incident: credentials were replaced, but available logs could not rule out access to customer data or recovery points.
Original read