SnapbackFree tier = no backups.
Supabase's free plan includes zero automated backups. One bad migration, one wrong DELETE, and your data is gone.
See what changed in your Supabase database.
Snapback takes read-only daily snapshots and compares them with your current database. Find schema and row changes before a migration becomes a guessing game.
Free during beta · Read-only access · No credit card
users+320 · −12
| 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
Backups you can't look inside aren't answers.
Pro backups don't answer the real question.
Daily snapshots tell you that you have backups — not what changed or when things went wrong.
PITR starts at $100/mo.
Point-in-time recovery is powerful, but it's priced for companies, not side projects.
How it works
Three screens between you and a very bad day.
Timeline
See your database's history at a glance.
A calendar-style timeline of every backup, each tagged with what moved. Spot the day things went sideways without opening a single dump file.
backupslast 7 days
| 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 |
Visual Diff
git diff, but for your data.
Pick any two snapshots. Snapback shows added, changed, and deleted rows per table — plus schema changes.
ordersschema changed · ~8
column added: refunded_at (timestamptz, null)
| change | id | status | refunded_at |
|---|---|---|---|
| ~ | 55e2f9 | refunded | 2026-07-27 |
| ~ | 6a1b04 | refunded | 2026-07-27 |
Focused Review
Find the rows that changed. Not the whole database.
Check the changed rows from the diff and narrow the blast radius before you decide what to fix in Supabase.
posts2 of 12 selected
| review | change | id | title | author |
|---|---|---|---|---|
| [x] | − | d31f77 | Launch notes | alice |
| [x] | − | e04a92 | Pricing draft | sam |
| [ ] | − | f92c15 | Changelog v3 | alice |
Live demo
This is what a bad Tuesday looks like.
Yesterday · 03:00 UTC
users
| id | plan | |
|---|---|---|
| 4c1a90 | maria@example.com | pro |
| 1c9d44 | bob@example.com | free |
| 2b8e10 | old@example.com | pro |
orders
| id | status |
|---|---|
| 55e2f9 | paid |
| 6a1b04 | paid |
posts
| id | title | author |
|---|---|---|
| d31f77 | Launch notes | alice |
| e04a92 | Pricing draft | sam |
| f92c15 | Changelog v3 | alice |
Beta access
Everything you need to see what changed.
Beta
$0during beta
- 1 Supabase project
- Max 7 snapshots
- 7-day retention
- Schema and data diffs
- Read-only access
- No restore yet
Join the beta to help shape what we build next.
Read-only by design.
Snapback never sees your service_role key. Beta and free accounts use a read-only connection only.
Read the security model →FAQ
The questions you should be asking.
Is my data safe?
Snapback connects with a read-only role you create — we never ask for your service_role key. Connection strings are encrypted before we store them. One click will delete the credentials and snapshots we hold.
Do you need my service_role key?
No. Just a read-only Postgres role. We give you the exact SQL to create it — and to revoke it anytime.
Can Snapback restore my data?
Not in beta or the free plan. Snapback shows the diff so you can see exactly what changed, but it does not write back to your database.
How is this different from Supabase's built-in backups?
Native backups are snapshots you can't look inside. Snapback shows what changed so you can fix the right data.
Do you support Neon or PlanetScale?
Supabase first. Neon is next on the roadmap.
What about Storage buckets?
On the roadmap. Tell us if it's a dealbreaker for you — it moves up the list fast if enough people say so.
Want to see what changed in your Supabase database?
Free during beta · Read-only access · No credit card