Website Builder
Describe a website in one sentence. Get a built, checked project with a preview and export bundles.
The website builder turns a short description into a built, checked and exportable web project. /site <description> starts it as an unattended background run: it appears under Jobs with its log and cost, and you can close the chat while it works. The template previews appear in the chat. /design is the other route, where the AI designs with a live preview next to the chat.
Diagram as text
- Brief: a sentence of free text becomes a brief. The builder does not ask questions back; it writes down every assumption and every gap so the final report can list them.
- Research: open facts are filled in only when a quote from a fetched source confirms them. Otherwise a visible placeholder stays.
- Style and previews: the builder picks a style and shows five template previews in the chat.
- It continues at once with the best-scored template. If you choose another one later, the build restarts at the content step.
- Build: content, scaffold, images, frontend, backend and wiring, in your container.
- Build gate: install, typecheck, lint, build, boot and smoke test. A site that does not build is not exported.
- Visual critic: screenshots at 360, 768 and 1440 px, with repair rounds for the defects found.
- Security gate: code rules, dependency audit and response headers.
- Acceptance: the served page is rendered and what does not work is repaired.
- Finish: domain ideas, export bundles and a report.
What a run does
| Step | What it does | Your part |
|---|---|---|
| 1. Brief | Turns the description into a brief. It never asks questions back; every assumption and every gap is written down and listed in the final report. | None. |
| 2. Research | Fills open facts, but only when a quote from a fetched source confirms them. Otherwise a visible placeholder stays. | None. |
| 3. Template previews | Picks a style from 181 curated ones and shows five template previews in the chat. The best-scored one is used at once. | Optional: choose another. The build restarts at the content step. |
| 4. Annotation | Draw an arrow, circle, frame, freehand stroke, text note or point on the preview to ask for a precise change. | Optional. |
| 5. Build | Writes content, scaffold, images, frontend, backend and wiring in your container. | None. |
| 6. Checks | A build gate (install, typecheck, lint, build, boot, smoke test); a visual critic that takes screenshots at 360, 768 and 1440 px and repairs defects; a security gate (code rules, dependency audit, response headers); an acceptance check that renders the served page and repairs what does not work. A site that does not build is not exported. | None. |
| 7. Finish | Suggests domain names and checks them, builds the export bundles and writes a report. | Download a bundle, or deploy it. |
Visual markup notes stick to HTML element selectors rather than screen coordinates. If a revision moves a button or re-flows a grid, your note stays attached to the element you clicked. If no selector can be found, the note says so.
Options
Flags go after the description: --profile ssr (a server-rendered app instead of static pages plus API), --budget <CHF>, --lang de,en (up to four languages), --no-domain, --export docker,static, --model <id> and --firma <id>. An unknown flag stays part of the description. Starting a run returns a cost estimate. For several sites in one go, see /ultrasite.
Export bundles
Seven targets exist: docker, static, webspace (classic hosting), zerolog-native (the site stays where it was built), vercel, netlify and cf-pages (Cloudflare Pages). Without --export you get docker, static, webspace and zerolog-native; with --profile ssr only docker and zerolog-native. Every bundle comes with a README, an .env.example and a VERIFY.md. Vercel, Netlify and Cloudflare Pages host the frontend only; the backend runs from the docker bundle.
Distinct design directions
When Design Engine v2 is available for your build, it compares each direction with your earlier builds and common design patterns. If a direction is too similar, the builder revises it, at most twice, before it creates the full site.
Completed v2 builds add design and review signals to a rolling memory of your last 50 builds. Deleting a project also deletes its saved design memory.
What to check yourself
For Swiss businesses the builder adds imprint and privacy pages, and notes that the legal texts must be checked by the operator. Placeholders that remain visible are facts it could not confirm.
Something missing or wrong here? Say so. The documentation is part of the product, not an afterthought. All topics · Security · Status · X · Legal & privacy · Home