Your remix URL and sharing your app

Copy an app into a workspace, understand what comes with it, and control whether other people can remix it.

A remix starts a separate copy of an app. Editing its saved source does not edit the original. Copied actions can still contact real services.

Duplicate your own app

Use Duplicate on your app in the dashboard to make a copy in the same workspace. You can duplicate your own app even when public remixing is turned off. Wait until the source app has finished building first.

The source does not have to be published. The copy uses the current saved files, custom endpoint code and scheduled-task definitions, rather than only the last published version.

Let someone else remix it

Share the app's Remix link from its sharing controls. Public remixing must be enabled. The recipient signs in and creates the copy in their workspace. Turning off public remixing does not remove copies already made.

A remix URL looks like https://www.overskill.com/remix/<app-id>. Use the link supplied by the editor.

What happens to data and credentials?

The copy has its own app data store and copies the database structure. It does not transfer the original's user accounts or private user/team records. Eligible public seed data can be copied: public tables without a required role are included by default unless seed copying is disabled. Role-gated public seed data requires the source's explicit opt-in. Do not assume every copy starts empty.

Secret environment-variable values and payment credentials are not transferred to the recipient. Non-secret configuration can be copied, so review external URLs and account references as well as the missing secrets.

Use the copy for testing

  1. Check the copy's data before adding test records. Use synthetic data instead of exporting private customer records unnecessarily.
  2. Review scheduled tasks and outbound actions before enabling or running them. A copied URL, shared workspace integration or newly reconnected provider can still reach a real external account.
  3. Configure test accounts and credentials for the services you need. Confirm which integration account each action uses.
  4. Check the copy in Preview. Preview and the live version of that copy share its data; Preview is not a second test database.
  5. Publish the copy separately only if you want it available at its own live address.

Export ZIP is a backup, not a one-click restore into another app. Bring selected test rows in through the data import flow and check the result.

Creating the copy itself does not run a billed builder turn. Asking the builder to customize it uses credits. AI and other paid actions inside the copy can also incur charges.

Was this helpful?

Thanks for the signal — it helps us improve the docs.

More in Publishing and sharing

Connecting your own domain

Use your own web address — like myapp.com — instead of the default one.

Preview vs live: how publishing works

Your changes are visible to you instantly. They're visible to your users when you publish. Here's the difference.

The Overskill badge on your app

The small badge in the corner of your app — what it is, how to move it, how to hide it, and the one step people forget.

Still need help?

If this didn't answer your question, our team is one click away.