Docs
Supabase cloning documentation
Clear answers on what SupaClone copies, which Supabase resources stay manual, and how credentials, secrets, data, and target-project writes are handled.
Trust essentials
Security
How SupaClone handles credentials, Supabase tokens, data movement, target writes, logs, and deletion expectations.
Read docs →Supported resources
The canonical matrix of what SupaClone clones, partially clones, verifies, skips, and leaves manual.
Read docs →Limitations
Honest boundaries for SupaClone, including resources that are intentionally skipped, platform-limited, or require manual verification.
Read docs →All documentation
Getting started
Run your first SupaClone job safely with a source project, a fresh target project, and a clear clone scope.
Database schema
How SupaClone handles PostgreSQL schemas, tables, constraints, indexes, views, extensions, and selected table data.
RLS policies
How SupaClone copies Row Level Security state and PostgreSQL policy definitions without treating authorization as an afterthought.
Storage
How SupaClone clones Supabase Storage buckets, files, policies, public access, and verification details.
Edge Functions
How SupaClone handles Supabase Edge Function code, settings, and the secret values that must stay manual.
Auth
What SupaClone can and cannot copy from Supabase Auth, including settings, providers, hooks, SMTP, users, and sessions.
Secrets
Why SupaClone does not automatically copy secret values and how to re-enter them safely after cloning.
Troubleshooting
Common SupaClone clone failures, what they mean, and how to recover safely.