Publishing your app
Last reviewed:
This page covers publishing a website to a URL. For mobile apps, see Connect Expo and prepare for store publishing.
Open “Deploy” to publish your website on a link you can share. Only the project owner can deploy or redeploy.
Your first deployment
- 1
Prepare the project
Wait for Codey’s task to finish. Open the preview and try the pages and buttons. If the project has no files yet, ask Codey to build the website first.
- 2
Open “Deploy”
Choose “Deploy” in the project’s tool tabs. If the tab is closed, open it from “+”. Wait for the deployment status and tier to load.
- 3
Review the tier and click “Deploy”
Review the displayed resources and price. Choosing a tier only saves your preference; starting hosting is a separate action. See Deployment tiers.
- 4
Choose a link when prompted
On the first deployment, a suggested subdomain appears. Edit it, wait for “Available”, then click “Confirm & deploy”. The name is fixed after confirmation; see Domains.
- 5
Follow the stages
The stages show preparation, security checks, upload, database updates, build, and deployment. Completion time varies by project. Wait for the live status; progress refreshes about every 4 seconds while work continues.
- 6
Open your website
When the live status appears, click the link and check your key pages. Copy the address from your browser to share it. If deployment fails, follow Common deployment errors.
Updating and redeploying
- 1
Test your changes
Ask Codey for the change, wait for the task to finish, and test it in preview. Workspace changes are not published automatically.
- 2
Click “Redeploy”
Open “Deploy”. After a previous deployment, an outlined button with a refresh icon appears. It reuses the saved subdomain and keeps verified custom domains.
- 3
Wait for the result
Follow the status and log until the operation finishes, then open the link and test the change. Avoid another request while deployment is in progress. If it fails, open the log and use “Solve with Codey” when available.
Redeployment prepares an update for the existing website. The service may need to restart, so uninterrupted availability is not guaranteed. A database schema update failure before the build stops that attempt while the previous version keeps serving visitors.
Security checks before deployment
The platform attempts a free basic scan before each deployment. A critical finding blocks it; medium and low findings do not block it on their own. The report appears in the deployment panel, and the latest results are in “Security”. A successful deployment does not guarantee that every check completed or that the website has no vulnerabilities.
See Security scans and fixes for deep scans, cost confirmation, and fixing findings with Codey.
After deployment
See Logs and deployment controls to stop, restart, or roll back your website. The published website uses a database separate from test data; see Your database.