Docs
Supported resources
The canonical matrix of what SupaClone clones, partially clones, verifies, skips, and leaves manual.
Last updated 2026-07-09
Supported
| Resource | Status | Notes |
|---|---|---|
| App database schemas | Supported | User/application schemas are cloneable. Supabase-managed schemas are excluded. |
| Tables | Supported | Includes regular and partitioned tables in cloneable schemas. |
| Columns and types | Supported | Restored through native PostgreSQL schema restore. |
| Primary keys and constraints | Supported | Restored and verified where possible. |
| Indexes | Supported | Restored with the schema. |
| Views and materialized views | Supported | Included in structure clones; materialized view data depends on clone mode and source behavior. |
| Enums | Supported | Restored with schema objects. |
| Extensions | Supported | Cloneable extensions are included; Supabase-managed/internal extension behavior may stay target-managed. |
| Functions and triggers | Supported | Includes application functions and triggers. |
| RLS enabled state | Supported | Policy and RLS metadata are part of the schema clone and verification flow. |
| RLS policies | Supported | Includes policy definitions for cloneable schemas. |
| Table data | Optional | User selects whether to copy data and can scope selected schema/table data. |
| Storage buckets | Optional | Bucket configuration can be created or updated on a fresh target. |
| Storage files | Optional | Copied for snapshot clones and verified by object listing, size, and checksums when available. |
| Storage policies | Optional | Policies on storage.objects and storage.buckets are recreated where the target accepts them. |
| Edge Functions | Optional | Function code and function settings can be created or updated. |
| Auth configuration | Partial | Allowlisted non-secret Auth settings can be copied. Secrets require manual re-entry. |
| Project settings | Partial | SupaClone compares selected project/PostgREST settings and reports differences. |
Not cloned automatically
- Auth users, identities, sessions, refresh tokens, and passwords.
- Supabase API keys.
- Secret values, including Edge Function secrets and Auth provider secrets.
- Billing settings.
- Organization membership and Supabase dashboard roles.
- Supabase-managed internal schemas such as
auth,storage,realtime,extensions,vault, andsupabase_functions. - Realtime configuration when Supabase OAuth cannot expose it.
- Unknown future Auth settings until they are reviewed and added to the allowlist.
Verification
SupaClone verifies the restored database schema field by field after the run. Storage file cloning is also checked against the target object listing and available metadata.
Some resources cannot be fully verified through public Supabase APIs. Those resources appear as manual steps or notices in the clone report instead of being silently treated as complete.
Fresh-target rule
SupaClone is not a bidirectional sync tool. It expects a fresh target project and avoids unsafe merges into existing projects. If you need to preserve target data, export and archive it before running a clone.
Ready to run a verified clone?
Start with a fresh target project, choose exactly what to copy, and review the clone report after the run completes.
Clone your first project free