Honest comparison
Firedrill vs Supabase's built-in backups
Supabase's built-in backups (daily on Pro, PITR as an add-on) are well built, and if you're on a paid plan you should leave them on. This page isn't 'ours good, theirs bad' — it's about the two properties platform backups can't have: independence from the platform, and third-party proof of restorability.
Where Supabase native backups is genuinely good
- ✔ Zero setup, managed by the people who run your database
- ✔ PITR add-on gives fine-grained point-in-time recovery
- ✔ Restores integrate directly into the Supabase dashboard
Side by side
| Supabase native backups | Firedrill | |
|---|---|---|
| Free tier | No automated backups | Weekly encrypted off-site backups on our free plan; verified restores from $19/mo |
| Independence | Stored by the same platform and account they protect | Separate infrastructure, separate account, client-side encryption |
| Restore proof | Trust the platform | Every backup restored on a fresh instance; per-check evidence you can hand an auditor |
| Retention | Plan-dependent window | Up to 365-day GFS with monthly archives |
| Portability | Restores into Supabase | Standard pg_dump archives restore anywhere Postgres runs |
Keep Supabase's backups on. Add an independent, restore-tested copy that survives anything that happens to your Supabase account — that's the layer Firedrill adds.