Cloned Components
When you run a clone, Twins can copy up to 14 types of components from your source project to your target project. Each component is independent and can be enabled or disabled.
Component List
| Component | Description | Detail Page |
|---|---|---|
| Tables (schema) | Table structure, columns, constraints, indexes | Detail |
| Data | Table rows | Detail |
| Views | SQL views | Detail |
| Functions and triggers | PostgreSQL functions and triggers | Detail |
| RLS Policies | Row Level Security access rules | Detail |
| Edge Functions | Supabase serverless functions | Detail |
| Storage | Buckets and files | Detail |
| Auth Users | User accounts | Detail |
| Cron Jobs | Scheduled tasks | Detail |
| Webhooks | Database webhooks | Detail |
| Realtime | Realtime configuration | Detail |
| Project Config | Project settings | Detail |
Clone Order
Components are cloned in a specific order to respect dependencies:
- Extensions — required before tables (e.g.
uuid-ossp,pgcrypto) - Custom types — tables may use enums
- Tables (schema only) — structure creation
- Sequences — serial/identity columns
- Views — depend on tables
- Functions — may be referenced by triggers
- Triggers — depend on functions and tables
- RLS Policies — depend on tables
- Data — inserted once the schema is in place
- Edge Functions — independent of the database
- Storage — independent
- Auth Users — independent
- Cron Jobs — may reference functions
- Webhooks — reference tables
- Realtime — publication configuration
- Project Config — global settings
What happens if a component fails?
The clone continues with the remaining components. A failure on one component does not stop the process. The final report details what succeeded and what failed.
Next Steps
Click on a component above to understand in detail what is copied and the key considerations.