Free tier = no backups.
Supabase's free plan includes zero automated backups. One bad migration, one wrong DELETE, and your data is gone.
Snapback takes automatic daily backups with visual diffs. See exactly what changed between any two snapshots — and snap back to any point, down to a single row.
Free during beta · No credit card
| change | id | plan | |
|---|---|---|---|
| + | 8f2a1c | alice@example.com | pro |
| + | 91bd07 | dev@acme.io | free |
| + | a70e33 | sam@studio.co | free |
| − | 1c9d44 | bob@example.com | free |
| − | 2b8e10 | old@example.com | pro |
The gap
Supabase's free plan includes zero automated backups. One bad migration, one wrong DELETE, and your data is gone.
Daily snapshots tell you that you have backups — not what changed or when things went wrong.
Point-in-time recovery is powerful, but it's priced for companies, not side projects.
How it works
A calendar-style timeline of every backup, each tagged with what moved. Spot the day things went sideways without opening a single dump file.
| date | changes |
|---|---|
| 2026-07-27 | users +320 · orders ~8 · posts −12 |
| 2026-07-26 | users +18 |
| 2026-07-25 | users +24 · posts +3 |
| 2026-07-24 | — |
| 2026-07-23 | users +11 · orders +2 |
Pick any two snapshots. Snapback shows added, changed, and deleted rows per table — plus schema and RLS policy changes.
column added: refunded_at (timestamptz, null)
| change | id | status | refunded_at |
|---|---|---|---|
| ~ | 55e2f9 | refunded | 2026-07-27 |
| ~ | 6a1b04 | refunded | 2026-07-27 |
Check the rows you want from the diff, preview the result, and restore. No full-database rollback, no collateral damage.
| restore | change | id | title | author |
|---|---|---|---|---|
| [x] | − | d31f77 | Launch notes | alice |
| [x] | − | e04a92 | Pricing draft | sam |
| [ ] | − | f92c15 | Changelog v3 | alice |
Live demo
Yesterday · 03:00 UTC
| id | plan | |
|---|---|---|
| 4c1a90 | maria@example.com | pro |
| 1c9d44 | bob@example.com | free |
| 2b8e10 | old@example.com | pro |
| id | status |
|---|---|
| 55e2f9 | paid |
| 6a1b04 | paid |
| id | title | author |
|---|---|---|
| d31f77 | Launch notes | alice |
| e04a92 | Pricing draft | sam |
| f92c15 | Changelog v3 | alice |
Pricing
$0/mo
$12/mo
$29/mo
Early access members get 50% off for the first year.
Read-only by design.
Snapback never sees your service_role key, never stores write credentials, and will publish its egress IPs at launch so you can lock us out at the network level.
Read the security model →FAQ
Snapback will connect with a read-only role you create — we never ask for your service_role key, and we never store write credentials. Backups will be AES-256 encrypted, and we'll publish our fixed egress IPs at launch so you can lock your database down to them. One click will delete everything.
No. Just a read-only Postgres role. We give you the exact SQL to create it — and to revoke it anytime.
We'll generate the restore SQL for you to review and run yourself, so you stay in control. One-click restore — using a write credential held in memory only, never stored — is on the roadmap.
Native backups are snapshots you can't look inside. Snapback will show you what changed and let you restore selectively.
Supabase first. Neon is next on the roadmap.
On the roadmap. Tell us if it's a dealbreaker for you — it moves up the list fast if enough people say so.
Free during beta · No credit card