Choose a hosting provider
Use the native publishing flow or prepare a deployment with a connected hosting tool.
Review the hosting choice
Open the project’s publishing action and review the hosting choices. Netlify has a native MaShop integration. Vercel and Railway can be connected through the hosting dialog’s remote MCP connection, then used to prepare publication with the assistant.
A successful account connection is not a completed deployment. Ask the assistant to inspect the available provider tools, the project’s build requirements and the expected public URL before proceeding.
Publish with the selected provider
- Choose the intended account and provider.
- For the native Netlify flow, complete the project connections requested by provisioning, including Supabase when that flow requires it.
- For a remote hosting tool, complete its authorization and ask the assistant to prepare the deployment for the linked repository.
- Review environment variables, build settings and any required approval.
- Wait for the provider’s result, then open the actual deployed URL and test the application.
Control builds and configuration
Hosting plans may limit builds, runtime or traffic. A code commit does not prove a deployment succeeded; inspect the provider result. Avoid repeated publication attempts while a build is already in progress.
Store secrets in the provider’s environment settings, not in public source files. Domain records and application hosting are separate settings; a custom domain needs to point at the chosen deployment and have valid HTTPS.