What gets cloned
Everything that defines your project's structure.
One clone run reproduces the full shape of your database in a fresh Supabase project.
$ supaclone clone prod-app → staging
✓ baseline detected · postgres 15
✓ pg_restore complete · 24.8s
✓ schema verification passed · 0 diffs
Baseline-aware clone plan
Supabase-managed schemas are detected and skipped - no broken restores into auth or storage.
Field-by-field verification
Every cloned object is compared against the source after the run - differences are named, never hidden.
Schemas & tables
Every user schema, table, and column - exactly as defined.
RLS policies
Row level security lands enabled, not as an afterthought.
Functions & triggers
Database functions and triggers arrive wired up and ready.
Indexes & constraints
Primary keys, foreign keys, uniques, and indexes carried over.
Views & enums
Views, materialized views, and enum types included.
Table data
Copy your rows too - every table, or only the ones you pick. Storage URLs inside your data are rewritten to the new project.
Storage
Buckets, files, bucket settings, and storage policies.
Edge Functions
Active function code plus verify-JWT settings.
Auth config
Site URL, redirects, email templates, provider wiring - secrets listed as manual steps.
Anonymized data clones
Coming soonMask or fake PII on the way over, so staging gets realistic but not real data.
Scheduled clones
Coming soonKeep staging in sync with recurring clone schedules.
How it works
Production schema to staging in three steps.
Connect Supabase
One-click OAuth via the Supabase Management API. Your projects are discovered automatically - no connection strings pasted around.
Pick source and a fresh target
Choose the project to clone and a fresh, empty target. SupaClone only writes into empty projects, so production is never at risk.
Clone and verify
Native pg_dump/pg_restore with a baseline-aware plan, then field-by-field schema verification and a full report of what happened.
Safety & transparency
No silent failures. Every clone ends in a report.
Each run is broken down into four buckets, so you know exactly what state your new project is in.
312
cloned
Everything that made it over, object by object.
4
skipped
Supabase-managed objects left alone on purpose.
0
failed
Anything that didn't restore - named, never hidden.
1
manual steps
Secrets you set by hand, listed for you.
Fresh targets only
SupaClone never merges or overwrites - it only writes into projects it has verified to be empty.
Source stays read-only
Your production project is only ever read from. Not a single write goes back to the source.
Managed schemas handled
auth, storage, and realtime are recognized and skipped correctly instead of breaking the restore.
Secrets never copied
SMTP passwords and provider secrets are never transferred - they appear as named manual steps.
Your staging environment is one clone away.
Full clones on every tier · pay once · no subscription