Publishing your app

Publishing takes your app live on the web. Before you publish, only you and your collaborators can see your work. After you publish, anyone you have allowed can visit.

Before you publish

Five minutes of checking saves an awkward launch:

1. Click through the core flows in the preview the way a stranger would: land, sign up, do the main thing, come back.
2. Test privacy with two accounts if your app has sign-in: create data as one user, confirm a second user cannot see it. See How data privacy works.
3. Check mobile with the device toggle; half your visitors will arrive on a phone.
4. Set your title, description, and preview image in Vault → SEO, so shared links look right from the first share.
5. Review who can use the app in Vault → Auth: open to anyone, invite-only, or sign-in required. See Public vs private apps.

How to publish

In the build workspace, hit Publish. Vaulter builds a production version of your app and puts it online. In a moment you have a real, shareable URL.

Your app goes live at its own address on vaulter.run, formed from your app's name, like salon-booker--acme.vaulter.run. You can share that link right away from the Share menu in the workspace, or put your app on a custom domain: buy one inside Vaulter or connect one you own.

What publishing actually does

Each publish is a complete production build, prepared for the open web:

• Your pages get their social and search tags: title, description, and a preview image, so shared links unfurl properly. See SEO.
• On paid plans, the analytics tracker is added so visits to your live app show up in your dashboard. See Analytics.
• Everything is served over HTTPS, on Vaulter's edge network.
• Caches are versioned per publish, so visitors get your new version immediately, never a stale mix of old and new.
• Publishing also refreshes your project's thumbnail, the image on your dashboard card.

On the free plan, published apps carry a small "Built with Vaulter" badge. Paid plans can turn it off in Vault → SEO.

Shipping updates

Publishing is not a one-time event. Keep building after you launch, and hit Publish again whenever you want changes to go live. Your visitors always see the last version you published, never your work in progress. Every publish is recorded in Vault → Deployments, so you can see your app's release history.

How often you can publish

Each workspace has a publishing limit over a rolling 24 hours, shared by every project in it: 10 a day on Free, 50 on Starter, 200 on Pro, and unlimited on Teams. Previewing your app is never limited, so you can iterate as much as you like and publish when you are happy. See Plans.

Who can publish, and who can visit

Publishing requires an admin role on the project, so a collaborator with view or edit access cannot ship your app by accident.

By default a published app is open: anyone with the link can visit. If your app should require sign-in to view, or only let people you invite sign in, see Public vs private apps.

Frequently asked

Does publishing cost tokens?

No. Tokens meter AI work only. Publishing has its own daily count per plan, and that is the whole story. See Tokens and usage.

Do visitors notice when I publish an update?

No interruption: caches are versioned per publish, so visitors get the new version cleanly on their next load, never a stale mix of old and new.

A publish went wrong. How do I get the old version back?

Vault → Deployments, pick the previous version, Roll back. It restores the live app in seconds and does not count against your publish allowance. See Undo, versions, and going back.

Can I customize what visitors see on a missing page?

On Pro and Teams you can set custom error pages, along with head code and PWA install. On other plans visitors get a clean default.