Skip to content
SupaClone logosupaclone

Everything SupaClone clones — verified after every run

Native pg_dump/pg_restore with a baseline-aware plan, field-by-field schema verification, and a full report of what happened.

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.

Schemas & tables

Every user schema, table, and column — exactly as defined.

RLS policies

Row level security policies land 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.

Extensions

Postgres extensions detected and enabled on the target.

Optional add-ons

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.

Data clones — exact & anonymized

Coming soon

Copy real table data, or anonymize PII on the way over.

Scheduled clones

Coming soon

Keep staging in sync with recurring clone schedules.

How it works

Production schema to staging in three steps.

1

Connect Supabase

One-click OAuth via the Supabase Management API. Your projects are discovered automatically — no connection strings pasted around.

2

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.

3

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.

  • ClonedEverything that made it over, object by object.
  • SkippedSupabase-managed objects left alone on purpose.
  • FailedAnything that didn't restore — named, never hidden.
  • Manual stepsSecrets and settings you need to set by hand, listed for you.
  • Targets must be fresh, empty projects — SupaClone never merges or overwrites
  • Your source project is only ever read from
  • Supabase-managed schemas (auth, storage, realtime) are handled correctly
  • Secrets are never copied — they show up as manual steps instead

From a real report

RLS enabled on 42 tablesverified
Extension pgcrypto enabledcloned
Storage bucket avatars + 3 policiescloned
SMTP password not copiedmanual step

Your staging environment is one clone away.

Start your free trial

14-day free trial · 1 clone included · Cancel anytime