Deploy your app
Publish through Pluto Hosting or a connected provider
Review your app and its important flows before publishing. Deployment availability and charges depend on the hosting option and account configuration shown in your environment.
Pluto Hosting
When Pluto Hosting is enabled, open Ship on Pluto from the project controls and choose Ship it on Pluto. PlutoAI runs the required checks and reports the deployment result. A successful deployment provides a product address on plutoai.live.
Open Settings → Hosting → Open hosting panel to manage hosted products, versions and links. The panel uses your Pluto account session. If the hosting controls are absent or report unavailable, that environment has not made this hosting option ready.
Netlify or Vercel
You can also use the supported workflow for a connected Netlify or Vercel account. Connect the intended account and project, then request deployment. Check the build and deployment result and open the returned URL. Provider quotas, charges and runtime support are separate from your PlutoAI allowance.
Use the same target for later updates unless you intend to create a different deployment. Changes in a preview do not publish automatically just because the files changed.
Custom domains
Pluto Hosting supports custom-domain management when the hosting environment is enabled. Use the hosting panel and configure the DNS records required for your product; DNS must resolve correctly before the domain can be verified and attached. Certificate availability can take additional time.
For Netlify or Vercel deployments, manage the domain through the connected provider's supported controls or dashboard.
Before and after publishing
- Try the important flows in the preview, including sign-in and access rules where relevant.
- Check that production configuration points to the intended accounts and services.
- Review the requested deployment and any approval shown.
- Wait for the reported outcome, then test the live URL.
A passing build does not by itself prove every live feature works. If deployment fails, share the exact reported error with the agent and verify the target before retrying.
Keep your source
Saving to GitHub and exporting source are separate from hosting. Use the project's source-control or export controls to retain your files. Exports have size, file-type and workspace-readiness limits; a failed export should be resolved rather than treated as a complete backup.
See your codebase, testing and environment variables.