The website builder is a remote MCP server that turns a conversation in ChatGPT, Claude or another MCP client into a complete, deployed website. It is coming soon: the pipeline described here runs internally, accounts and payments are not open yet. The product page summarises it; these pages explain how it works so you know what to expect. To hear when access opens, use the contact page.
What a conversation produces
A site built this way is a normal software project, not a page in a hosted editor.
- Frontend. Marketing pages, contact and lead forms, navigation, responsive layouts and generated images, in Next.js and TypeScript.
- Backend. Server routes, data models for the entities in your brief, list and detail pages, simple admin screens, and sign-in by email link.
- Storage. A dedicated document database per site and object storage for uploads, provisioned with the project.
- Deployment. A production container, automated checks, and a preview URL after every build. Subdomains and custom domains follow in a later release.
- Documentation. Project, specification, decisions, runbook and migration guides, generated with the code and kept current as the site changes.
Everything lives in one Git repository that belongs to you. See your code and repository.
How a site comes together
- Connect the builder to your assistant as a remote MCP server. See connect from ChatGPT or Claude.
- Describe the site: objective, audience, pages, features, style, colours, and what must be true when it is done. The assistant saves this as the brief.
- Plan. The builder quotes the planning work, asks the questions it cannot answer alone, and returns a plan with acceptance checks you can read and amend.
- Build. An agent implements the plan in the repository, verifies every acceptance check, commits, and publishes a preview URL.
- Iterate. Ask for the next change in the same conversation. Every round starts from the current code and the current plan.
Roles
Three parties take part, and the boundaries between them are deliberate.
- You, through your assistant, describe, decide and approve. Nothing that costs credits runs before it is quoted, and nothing reaches production without your go.
- The control service keeps the brief, plan, jobs, quotes and ledger. It authorizes each stage of work and records every event.
- The worker, a long-running coding agent, claims authorized stages, writes code in the repository, verifies checks and submits results. It never talks to you directly and never decides prices.
Credits and quotes
Work is paid in credits. Planning and building are quoted before they start, the quote is approved in the conversation, and only accepted work is charged. A build whose acceptance checks fail is still reported honestly; the service decides whether it is accepted. Pricing for the public release is not published yet.
Not in the first release
Per-user OAuth accounts, card payments, publishing to subdomains and custom domains, payments inside generated sites, third-party integrations that need your customers' credentials, regulated data, multi-tenant customer organisations, and real-time features. When a brief asks for one of these, the planner says so and proposes a scope that works.