Duplicate Website

Duplicate creates an exact copy of your Sticklight website in a new project. The clone includes your full codebase and database structure, but starts with empty tables. No data from the original is copied.

This is useful when you want to:

• Use an existing project as a starting point for something new
• Create a separate version for testing or experimentation
• Build a template from a project you have already completed

How to Duplicate a Project

1. Go to your Sticklight homepage
2. Find the project you want to duplicate
3. Click the three dots menu (⋮) on the project card
4. Select “Duplicate”
5. Confirm in the dialog that the action is initiated

The clone will be named “Copy of [Original Name]” and appear in your project list once complete. If additional copies of the same project already exist, the system appends ” (1)”, ” (2)”, etc., up to 100 attempts.

What Gets Duplicated

Your entire codebase is copied:

• All pages, components, and layouts
• CSS and styling
• Images and assets
• Project name and description

If Cloud Backend is enabled, your database structure is copied:

• Tables, columns, and indexes
• Row-Level Security (RLS) policies
• Database triggers and functions
• Database extensions
• Auth configuration (email templates, settings)
• Edge Functions (code is copied and deployed automatically)

The clone receives its own database with fresh credentials. Your security rules and database design are preserved exactly as you built them.

What Does Not Get Duplicated

Database content – Tables are copied but start empty. No rows of data transfer to the clone. This protects user privacy and prevents accidental data exposure.

Edge Function secrets – API keys and tokens are not copied for security reasons. You need to add these manually in the clone.

Custom domains – The clone gets a new temporary subdomain (like project-abc123.sticklight.app). Your custom domain stays with the original.

Published state – The clone starts as a draft, not published.

Analytics and history – No analytics data or version history transfers. The clone starts fresh.

How Long Does It Take?

• Without Cloud Backend: Nearly instant
• With Cloud Backend: 1-3 minutes (a new database needs to be provisioned and Edge Functions deployed)

You see a progress indicator while the duplication runs.

After Duplicating

Once your clone is ready, check these things:

1. Add Your Secrets

If your original project used Edge Functions with API keys (like payment processors, email services, or external APIs), you need to add these secrets to the clone:

1. Open the cloned project
2. Go to Cloud > Secrets
3. Add each secret your Edge Functions need

2. Verify Edge Functions

Edge Functions are deployed automatically during clone setup. Test that they work correctly in the new project, especially any that depend on secrets you just added.

3. Verify Database Access

Your RLS policies are copied automatically, so security rules should work the same way. The clone has its own database credentials, configured automatically. You do not need to copy environment variables from the original.

4. Set Up Your Domain (Optional)

If you want a custom domain for the clone, set it up in Settings once you are ready to publish.

Important Notes

Duplicating is free. The duplication process does not use any credits, regardless of how complex your project is.

The clone is completely independent. Changes you make to the clone do not affect the original project, and vice versa. They share no connection after duplication.

Database content is never copied. This is intentional. It protects user data and prevents privacy issues. If you need data in your clone, you need to add it manually or import it.

RLS policies are preserved. Your security rules copy over exactly, so your clone maintains the same access controls as the original.

Each clone gets its own credentials. The clone connects to its own database instance with fresh credentials. You do not need to reconfigure database connections.

FAQ

Why is my cloned database empty?

Duplicate copies your database structure (tables, columns, relationships) but not the data inside. This protects user privacy and ensures you do not accidentally expose sensitive information. The clone is ready for fresh data.

Why do I need to re-add my secrets?

API keys and tokens contain sensitive credentials that could grant access to external services. For security, these are never copied between projects. You find the same secret names are needed, but you must provide the values again.

Are Edge Functions deployed automatically?

Yes. When you duplicate a project with Cloud Backend, Edge Functions are deployed during the clone setup process. You only need to add any secrets they require, then verify they work.

Can I duplicate someone else’s project?

You can only duplicate projects you own. In the future, public templates may be available to duplicate.

What if the duplication fails?

If something goes wrong during duplication, try again. If the problem persists, contact support. In rare cases where a Cloud Backend was partially created, our team can help clean it up.

Can I choose what to duplicate?

Currently, duplication is all-or-nothing for the components listed above. You cannot selectively clone only certain pages or parts of the database.

Does duplicating use credits?

No. Duplicating a project is free and does not consume any credits.