Keep an app's code private: the Allow remixing switch

Turn off Allow remixing to keep copies of your app to yourself and its backend, access rules and source private to you and your team, while everyone you share it with keeps using it. A Vibes Pro feature.

Every app on Vibes DIY starts out remixable: anyone who can open it can make their own copy and change it. That is how most apps here get started. When an app is yours to keep, turn off Allow remixing. Only you can remix it, its backend and source stay private to you and your team, and everyone you share it with keeps using it exactly as before.

Where the switch lives

Open your app, tap Share, then Settings. The switch sits under Allow auto-enhance:

Position	What the Share card says
On (the default)	"Anyone who can open this app can remix it into their own."
Off	"Only you can remix it, and its backend and source stay private to you and your team."

The same switch is on the app's Settings tab, in the Remixing card.

Turning it off is part of Vibes Pro. On Free or Plus the switch carries a Pro tag, and tapping it opens the Vibes Pro offer. Turning remixing back on is always open to every owner.

What stays private

With remixing off, these are served only to you, your developers, editors you invited, and Vibes DIY support:

Your backend: backend.js, the code that runs on the server.
Your access rules: access.js, the rules that decide who can read and write each record.
Your starting data: seed.json.
Your source: the files as you wrote them, through the CLI's pull, the Code tab, and every download link.

And only you can make a copy, from the web, the CLI's remix, or the agent's remix tool.

What visitors still get

Your app has to run in each visitor's browser, so the parts that make it run still reach them: the compiled JavaScript, the page's styles, images and other assets. Someone determined can read compiled code in their browser. The promise is a private backend and no source download: the server side of your app, its rules and the files you wrote stay with you.

Visitors see "The owner keeps this one to themselves. Make your own." where the remix box would be, and their words start a new app of their own.

Who keeps full access

Who	Remix it	Backend and source
You, the owner	yes	yes
A developer you granted	no	yes
An editor you invited, or approved on request	no	yes
Everyone else who can open the app	no	no

Developers and editors keep working on the app itself; making copies is your call. See developer grants for what a developer can do.

If you leave Vibes Pro

Your app stays as it is until you publish again. Your next publish turns remixing back on, and the switch says so while it waits: "Remixing turns back on at your next publish. Vibes Pro keeps it off."

Good to know

Copies made before you turned remixing off belong to the people who made them.
Pull your own app's source as usual: npx vibes-diy pull signs in as you.
A copy you make of your own app starts remixable, and you decide again for that one.