Skip to content
Live now - clone in seconds

Clone your Supabase project in seconds - not hours.

SupaClone copies schemas, tables, RLS policies, functions, triggers, and the data you pick into a fresh project - powered by native pg_dump, verified after every run.

Full clones on every tier · pay once, no subscription

prod → stagingcloning
Connected via Supabase OAuthread-only
82 tables clonedpublic
64 RLS policies enabledpublic
37 functions & triggersplpgsql
129 indexes & constraintsbtree
Storage buckets & policies12 policies
Schema verification0 diffs

source read-only · target verified empty · native pg_dump

native pg_dump / pg_restore
fresh, empty targets only
verified after every clone
OAuth via Management API

Why not just pg_dump?

pg_dump alone breaks on Supabase projects.

pg_dump is a great tool - but Supabase projects ship with managed schemas, roles, and extensions that a raw dump-and-restore gets wrong.

raw pg_dump

the manual way
  • Chokes on Supabase-managed schemas like auth, storage, and realtime
  • Happily restores into non-empty targets and overwrites what's there
  • No report - silent failures surface days later
  • Connection strings copied around by hand

supaclone

with guardrails
  • Baseline-aware restore plan skips Supabase-managed objects correctly
  • Requires a fresh, empty target - production is never a write target
  • Field-by-field schema verification and a full report after every run
  • Projects discovered via Supabase OAuth - no connection strings pasted

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-cli

$ 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.

verificationcomparing…
tables
rls policies
functions & triggers
indexes & constraints

Field-by-field verification

Every cloned object is compared against the source after the run - differences are named, never hidden.

clone-manifest
table

Schemas & tables

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

policy

RLS policies

Row level security lands enabled, not as an afterthought.

function

Functions & triggers

Database functions and triggers arrive wired up and ready.

index

Indexes & constraints

Primary keys, foreign keys, uniques, and indexes carried over.

view

Views & enums

Views, materialized views, and enum types included.

data

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.

Optional

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.

On the roadmap

Anonymized data clones

Coming soon

Mask or fake PII on the way over, so staging gets realistic but not real data.

Scheduled clones

Coming soon

Keep staging in sync with recurring clone schedules.

How it works

Production schema to staging in three steps.

01

Connect Supabase

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

02

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.

03

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.

verified · 0 diffs

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.

Pricing

Pay once, clone full. No subscription.

Every tier can clone the full project - structure and data. Buy a single run or a 5-pack, and your credits never expire - or go Lifetime for unlimited runs and every feature we will ever ship.

Single Run

$9.99one-time

1 full clone run, yours until you use it. Only successful runs count.

  • 1 full clone run
  • Full clones - structure + data
  • Unlimited projects
  • Credits never expire
  • Failed clones never use up a run
  • Earn up to 5 free clone credits per referral
Get Single Run
Best Value

Lifetime

$79.99one-time

Pay once. Everything we ever build is included.

  • Unlimited projects & clone runs
  • Full clones - structure + data
  • Full clone reports
  • All future features included
  • Referrals earn withdrawable cash rewards
  • Scheduled clonesComing soon
  • Priority support
Get lifetime access

5-Pack

$29.99one-time · $6.00 per run

5 full clone runs for $6.00 each. Only successful runs count.

  • 5 full clone runs
  • Full clones - structure + data
  • Unlimited projects
  • Credits never expire
  • Failed clones never use up a run
  • Earn up to 5 free clone credits per referral
Get the 5-Pack

FAQ

Frequently asked questions.

Yes - every plan can clone the full project: schemas, tables, RLS policies, functions, triggers, indexes, views, enums, extensions, and the table data you select. There is no structure-only tier.

Yes. Data clones rewrite storage URLs stored in your rows - like https://<project-ref>.supabase.co/storage/... links - to the new project, so the clone loads files from its own buckets. Only signed URLs need re-generating, and the clone report shows exactly how many rows were updated.

No. Clone targets must be fresh, empty Supabase projects - SupaClone never merges into or overwrites an existing project. Your source project is only ever read from.

Supabase projects ship with managed schemas (auth, storage, realtime) that a raw dump-and-restore gets wrong. SupaClone builds a baseline-aware restore plan around them, verifies the restored schema field by field, and hands you a full report.

Secrets are never copied. Anything that needs a secret - OAuth provider keys, SMTP passwords, function secrets - is listed as a manual step in your clone report instead.

A Supabase account. You connect your organization via OAuth, SupaClone discovers your projects through the Supabase Management API, and all you enter is each project's database password - no connection strings to hunt down.

A Single Run is $9.99 one-time and includes 1 full clone run. The 5-Pack is $29.99 one-time for 5 full clone runs - $6.00 per run. Lifetime is $79.99 one-time with unlimited clone runs and every future feature included. No subscription, and only successful runs count.

Your staging environment is one clone away.

Full clones on every tier · pay once · no subscription