Docs
Start building
Build

How Building Works

What happens between pressing Send and having a finished build — the same shape for every build type.

The flow

You describe it
Plan it first, or build straight away
Intake questions
A few multiple-choice questions on style and content
The pipeline runs
Plan → generate → audit → repair → images → review
Preview
The result, on every device size
Refine and publish
Edits keep everything you did not ask to change
Planning and the intake questions are optional and never charged. The build is charged once, for what it actually cost, and only if it succeeds.

Plan or Build

The composer opens in Plan: a conversation about the approach, with nothing built yet. When the plan looks right, choose Build it. Switch to Build to skip planning. Planning is the cheap place to change your mind — a build is not.

The engine is chosen by the build type

The build type sends your description down one of four engines, and that decides what the result is: a validated specification rendered into a site, a self-contained interactive program, a React Native project, or a 3D game definition. Switching type means a new build, not a conversion. See Build Types.

What you see while it runs

Each stage appears as it starts and finishes, with skipped stages marked — for example, Lite skips photographs. The stages are listed on each build type’s page and in full in the Generation Pipeline.