Publish a Web project
Web publication is available only to routes with Web publication capability. A Prototype design artifact and a Native app use different delivery paths. General-purpose Web-hosted projects can expose publication when their configuration allows it.
Prepare a release
- Confirm the active project route and selected stable checkpoint.
- Review the latest file changes and complete the applicable app tests.
- Verify environment variables, data connections, access rules, and any required external integration.
- Review the publication summary, target, and cost or entitlement information shown by the platform.
- Start publication and wait for a final deployment state before sharing the URL.
Deployment and domains
Open the deployment or operations tools to inspect deployment history, public URL, health, logs, and available recovery actions. Domain controls can require a verified domain, DNS changes, or certificate provisioning. Follow the displayed record values exactly and allow DNS/provider propagation. Do not publish private or test data by mistake.
Rollback and shutdown
Compare the unhealthy deployment with the last known stable checkpoint. Use rollback only after confirming which artifact will become active and whether database changes remain compatible. Shutting down can stop public traffic but does not necessarily delete the project or its data. Preserve incident and deployment evidence when requesting help.
Publication is not store release
A Web URL is not an iOS or Android store release. Use the Native delivery workflow for device packages, signing, beta distribution, or store submission.