{slug}.product-os.app, or to a custom domain.
Tools
What it reads and produces
Reads: the built project in the sandbox; environment variables; the deployment target. Produces: a live production deployment on its own URL; a GitHub repo with your code; a cumulative deploy ledger.Where it sits in the pipeline
Deploy is an on-demand action, not a stage: you trigger it whenever you want to ship, and you can redeploy as often as you like. It is the last agent in the chain, downstream of the Fullstack Builder that wrote the code and, ideally, a passing run from the QA Agent. The Orchestrator can also poll live deployment state directly withcheck_deploy_status, so you can ask about a release without triggering a new one.
The sequence is deliberately defensive. check_recent_deploy runs first so the agent never deploys blind over an in-flight or just-finished release, and preflight_build runs the production build inside the sandbox before anything is pushed, so most failures are caught and fixed before they ever reach Vercel.
For domains and deployment details beyond the agent itself, see deployments and domains.