Publishing & sharing an app

Every app you build runs on real infrastructure, at its own public URL, from the moment it builds successfully. Publishing is a separate, lightweight thing on top of that: it marks the app as released.

What publishing does

Open your app in Visual Code view — or its detail screen — and tap Publish:

• The app's status flips from Draft to Published, shown as a green Store chip on the app's detail screen.
• A Preview button appears in the header, giving you the app's live URL to open and share.
• The app stays fully editable — publishing isn't a one-way door. Keep chatting to improve it, and every later change goes live on the same URL.

Tapping it again unpublishes the app, which returns it to Draft.

There is no directory to browse

No app store, no install flow

Nexrall has no browsable app directory and no "Get"/install flow. An app is reached by its own URL — you share the link, or point a custom domain at it. There is nothing to publish into.

So the app's URL is the distribution channel. To let someone use your app, send them the link, or give it a custom domain.

The Store filter in your Apps list is just a view of your own projects — it separates the apps you have published from your drafts. It is not a marketplace.

Your app's URL is public — always

This is the part that surprises people, so it is worth stating plainly:

	Reachable at its URL	Shown as
Draft	✅ Yes — anyone with the link	Draft
Published	✅ Yes	Store

There is no login wall in front of an app in either state. That is deliberate: it is what lets a real end-user open a shared link, a custom domain, or an embed without ever having a Nexrall account.

So Draft does not mean private. Unpublishing changes the app's released status; it does not take the URL offline.

Taking an app offline

Because unpublishing doesn't remove the URL, the way to genuinely take an app down is to delete it from the app's detail screen. Deleting deprovisions the app's Worker, its storage and its domains, so the URL stops serving.

If you simply want an app out of circulation, unpublish it and stop sharing its URL — but treat anything you have already shared as reachable until the app is deleted.

App runtime & isolation

Published (and draft) apps run in their own isolated Cloudflare Worker environment — separate from your Nexrall session, with their own scoped database and storage. An app never has access to your Nexrall account data beyond what you explicitly wire into it, and publishing does not loosen that isolation.

Each app also has its own allowance of database and storage. If it outgrows that, you can buy extra capacity per app — see Billing & Wallet.