Build

Build is where the app stops pretending. The backend, database and integrations become real, and the app runs end-to-end on the Build Server. Sign-in is the one exception: the preview signs you in automatically, and the real sign-in screen first appears in Rehearsal. See the servers.

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.

What Build costs

The agent work you ask for, and the Build Server once your free hours are used. Every organisation’s first 50 Build Server hours are free; after that the Build Server costs €1 an hour, drawn from your wallet. Agent turns cost points here exactly as they do in every other stage.

Hosting cost for standing infrastructure starts at Rehearsal, where the infrastructure becomes real and standing.

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