Environments

There are two versions of your app: the one you're building and the one your users see. Knowing which is which saves a lot of confusion.

Preview — your working copy

The preview is your app running live as you build it, on an internal preview address. Builds and edits land here first, so you can try things freely without anyone seeing half-finished work.

Everything in Working with the preview happens here.

Published — what your users see

When you publish, Vorx builds your app for production and serves it at your-app.vorx.live, or at your own custom domain. That version stays exactly as it was at the moment you published.

Publishing is what makes a change live

There's no separate promote step. Your edits accumulate in the preview and reach your users the next time you publish — which is why it's normal to build for a while, then publish once you're happy.

It also means that a change you're mid-way through does not leak out to your users, and that rolling back your working copy doesn't alter the live app until you publish again.

Check before you publish

Because publishing is the moment your work becomes visible, it's worth a quick pass first — sign-in works, no placeholder copy, the mobile layout holds up. See the launch checklist.

Keys and test data

Secrets are set per project, so an app configured with a provider's test key uses that key everywhere, including once published. Before you take real payments or send real email, swap the value to the live key under Settings → Cloud → Secrets and publish again.

Next steps

• Deploying your app — publishing and republishing
• Launch checklist — the pass before you go live
• Secrets — keys and configuration