Live previews while you build
Every project runs in an isolated cloud sandbox with a live preview URL. As agents write files, install dependencies, and run builds, the preview updates, so you review real behavior rather than descriptions of it. Previews are for development; they are not your production URL.Deploying
Deploy is an on-demand action, not a pipeline stage: trigger it whenever you want, as often as you want. When you do, the Deploy Agent runs a sequence designed to ship a working app, not just push files:1
Check recent deploys
The agent first checks whether a recent deploy already covers the current state, avoiding redundant work.
2
Preflight build
It builds the project before anything ships. Problems surface here, not in production.
3
Push to GitHub
The code is pushed to your own GitHub repository, so every deploy corresponds to a commit you can inspect. See Code ownership.
4
Deploy to Vercel
The app deploys to Vercel and comes up at its live URL.
Domains
Deployed apps ship to one of two places:
The platform subdomain is the default: every deployed project gets a
{slug}.product-os.app address with no setup. On Pro and above you can attach your own custom domain, and the watermark is removed. See Plans and credits for plan details.
Where this runs
All ProductOS deployments target Vercel, and your code always flows through your own GitHub repo on the way there. That means no proprietary hosting layer: if you later want to deploy the same repo yourself, through your own Vercel account or any other host, nothing stands in the way.Related pages
- Deploy Agent: the agent behind the deploy action
- Sandboxes: how the development environment works
- Security and data: isolation and data handling