Sharing your app

Every app you build gets a real, public web address the moment it's deployed. You can open it,
send it to friends, post it, or put it on a business card — it's a normal link that works in any
browser, on any device.

Getting your link

When your AI finishes building or updating an app, it gives you the link in its reply. You can
also just ask:

> *"What's the link to my app?"*

What to expect

- It's live immediately. No waiting, no publishing step beyond the deploy your AI already did.
- Anyone with the link can open it. There's no login wall unless you asked your app to have
  one.
- The link stays the same when you make changes. Editing your app updates it in place — you
  don't get a new address each time, so a link you've already shared keeps working.
- It works on phones. Ask for a "mobile-friendly" design if that matters to you.

Controlling who can do what

The link being public doesn't mean everything is open. If you want limits, ask for them:

- *"Add a simple password page before anyone can see the app."*
- *"Only let me delete entries, but let anyone add them."*
- *"Hide the admin page behind a secret link."*

Letting others fork your app

You can let other people fork your app — make their own copy they can edit and run under
their own account. Turn it on from your project page in the dashboard ("Sharing" → *Enable
public forking*), or just ask your AI to *"let others fork this app"*.

When someone forks your app, they receive:

- your code,
- your database structure (the shape of the tables — but none of your actual data), and
- your public assets (images, fonts, files you added at build time).

They do not get your data, your users' uploads, or your secrets (API keys you stored as
environment variables). Their copy starts empty and disconnected from yours — changes they make
never touch your app.

> ⚠️ One thing to check first: if you (or your AI) wrote any password or API key *directly
> into the code* instead of storing it as a secret, a fork would copy it. Before enabling public
> forking, ask your AI to *"make sure no secrets are hardcoded — move them to environment
> variables."* This is good practice anyway.

When you turn it on you can add a short description of your app — it shows on the fork page
and in the gallery so people know what they're copying.

Every forkable app gets a page at onvibe.run/fork/your-app-name that explains what a fork
includes and how to do it — share that link with anyone you want to let copy your app. To also
get featured in the public gallery at onvibe.run/forkable, an onvibe admin approves it first
(a light quality check); your own fork page works right away regardless.

Want a "fork me" button right inside your app? Just ask your AI: *"add a fork button that
links to my fork page."* It can place a small badge or a corner ribbon, styled however you like.

You can disable public forking again at any time; it doesn't affect copies people already made.

Good to know

- If you want a custom domain (your-own-name.com) instead of the default address, ask your AI
  whether that's available for your app and how to set it up.
- Sharing the link shares the app, not your account — people who open it can't see your dashboard
  or your other projects.