Build
In short
Build replaces mocked data with a real backend, database and integrations on the Build Server, so the app works end-to-end before anyone pays for production infrastructure.
Build is where the app stops pretending. The backend, database, authentication and integrations become real, and the app runs end-to-end on the Build Server.
What changes when you enter Build
- The agent’s scope widens from the frontend to the whole project, backend included.
- Schema changes become migrations, with a history.
- Automated tests are generated and start gating changes.
- Integrations move from stubs to real credentials against sandboxes or test accounts.
Work in slices
The fastest route through Build is one complete journey at a time — one flow working end-to-end, tested, before opening the next — rather than every screen half-wired. It keeps each verification cycle small and makes a failure point at one change.
Costs start here
The Build Server is real infrastructure and draws from your wallet while it runs. Agent turns cost points in every stage; hosting cost is what Build adds.
Signs you are ready to leave
- The main journeys work end-to-end against real data.
- Tests pass and cover the paths you would be embarrassed to break.
- Integrations are proven against something other than a stub.
- You know where the real data is coming from at go-live and roughly how much there is.
Next: Rehearsal · Editing generated code