Describe the site to ChatGPT or Claude. An agent plans it, asks what it needs, builds frontend, backend and storage, and publishes a preview. You own the repository, you can work in it alongside the AI, move it to your own cloud, and keep maintaining it from the same chat.
Build a site for my bakery: menu, pre-orders, a blog.
Plan ready, two questions first.
Then I build it and send you a preview to open.
Frontend, backend, storageOne repository, your source code
Preview deployedCommit, checks and migration guide
yourbakery.com
Coming soon. Illustrative flow from a conversation to a deployed site.
The overview
A conversation in. A website and its code out.
The website builder is a remote MCP server that ChatGPT, Claude and other MCP clients connect to. From a conversation, it creates a project, turns your description into a plan with open questions, builds a working website end to end (pages, forms, authenticated areas, data models, storage, uploads and deployment), and keeps iterating on it. Every site lives in its own Git repository with its source code, documentation and automated checks, so you can contribute directly, hand it to your own team, transfer it to your own infrastructure, or keep asking your assistant for changes. It is in development and not yet open; this page describes what it does and how it will work.
What the builder produces
Not a page template or a hosted site you cannot leave. A full application, generated as a normal software project.
Frontend. Marketing pages, contact and lead forms, navigation, responsive layouts and generated images, written 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 database per site and cloud storage for uploads, provisioned with the project instead of bolted on later.
Deployment. A production container, automated checks, a preview URL after every build, and later a subdomain or your own domain.
Documentation. Project, specification, decisions, runbook and migration guides generated with the code and kept up to date as the site changes.
Guardrails. Repository hooks, acceptance checks run on every build, and a clear list of what the site does not do.
From a conversation to a running site
01
Connect the builder. Add it as a connector in ChatGPT or Claude, the same way as any remote MCP server. No separate dashboard to learn.
02
Describe the site. Objective, audience, pages, features, style, colours and what must be true when it is done. The assistant saves that as the brief.
03
Review the plan. The builder quotes the work, asks the questions it cannot answer alone, and returns a plan with acceptance checks you can read and amend.
04
Build and preview. An agent implements the plan in the repository, verifies every acceptance check, and publishes a preview URL for you to open.
05
Iterate. Ask for the next change in the same chat. Each round starts from the current code, never from scratch.
Own the source code, work with the AI
Every site is a Git repository you can read, clone and change. The AI is a contributor to your project, not the owner of it.
Your repository. Full source code, documentation and checks in a repository under your control, with the history of every change the builder made.
Contribute directly. Open the project in your editor, commit alongside the agent, and the next build picks up your changes. The builder never overwrites work it did not make.
Co-work in the open. The plan, decisions and limitations are written down in the repository, so a developer or a second assistant can pick up where the conversation left off.
Standard stack. Next.js, TypeScript, a document database, object storage and containers. Nothing proprietary stands between you and your code.
Transfer it to your own infrastructure
Hosting with us is a convenience, not a lock. Each project ships with a migration guide and a production container, so moving it is a documented task rather than a rewrite.
Point the repository at your own cloud project, run the container on your own platform, bring your own database and storage, and keep the domain. The builder can still work on the code after the move, because it works through the repository, not through our hosting.
Keep maintaining it from your chat
A launched site is where most of the work begins. Content updates, new pages, a changed form, a dependency bump, a new data entity: all of it is a request in the same conversation, with a plan, a check, a preview and a commit you can review.
You decide what gets approved. Every change that costs credits is quoted first, and nothing deploys to production without an explicit go.
Status
The builder is in development and not yet open. The MCP server, the planning and build pipeline, repository provisioning and preview deployments are working internally; accounts, payments, publishing to subdomains and custom domains come next. Tell us about the site you have in mind on the contact page and we let you know when access opens.
A few more details
Frequently asked questions
Is the website builder available now?
Not yet. It is in development and this page describes the service as it will launch. Use the contact page to tell us about your site and we let you know when access opens.
Which assistants can use it?
Any client that supports remote MCP servers over Streamable HTTP, including ChatGPT, Claude on the web and desktop, Claude Code and other MCP clients. Connecting it works like adding any other connector.
Do I own the code?
Yes. Each site is a Git repository with its full source code, documentation and automated checks. You can clone it, change it, hand it to your own team or move it to another host.
Can my developers work on the site at the same time as the AI?
Yes. The builder works through the repository like any contributor. It builds on the current code, documents its decisions, and the next build includes your commits.
Can I move the site to my own infrastructure?
Yes. Every project ships with a production container and a migration guide. After the move, the builder can keep working on the code through the repository, or you can stop using it entirely.
What will it cost?
Pricing is not published yet. The model is credits: planning and building a site are quoted before they run, and only accepted work is charged. Hosting will be priced separately from the build.