Any model can generate an application that looks finished. The gap between looks finished and is finished is where software actually lives: does the login work, does the form validate, does the deploy boot, does the edge case crash. The Software Studio's pipeline exists for that gap.
Plan, build, preview
A build starts with a plan you can read — architecture, scope, and the credit quote — before code is written. The build stage produces working software, and the preview stage puts it behind a live URL you can click through yourself. Engineering stages always run on frontier models; we do not route your build to a cheaper model to save cost.
Then the part most pipelines skip
The QA Agent drives a real browser against the preview — actual journeys, web vitals, accessibility checks — and files findings with evidence attached. The Fix Agent takes those findings, edits the repository, verifies each file it touched, and opens a pull request. What lands in your review queue has been exercised by a browser, not just rendered once in a screenshot.
Changes arrive as pull requests rather than silent pushes, long builds persist their state so a closed laptop does not kill the job, and every high-impact step — merging, deploying, spending — waits behind an approval that shows exactly what will happen. That is what an engineering team on demand should mean.