Website Builder turns the agent already running on your PocketCorp into your web designer, and your server into the place the result lives. No account anywhere else, no monthly plan, no export fee.
HOW IT GOES
0. Pick how to start. Describe the site you want; or paste the address of a site you already have — it is copied exactly, every page and every image, stylesheet, script and font it loads, working from your server with the old host gone, and the agent also rebuilds it two more ways from what it read: refreshed, or reimagined; or upload a zip of a website you already have as files, and it goes straight to the dashboard, ready to put live and hand to the agent.
1. A short brief. About a dozen questions, one per screen, built to be answered on a phone: what you are building, who for, the one thing a visitor should do, which pages, how it should feel, colour, typography, and any sites you want it to look like — with one-tap links to Godly (https://godly.website), Awwwards (https://www.awwwards.com/websites/), Land-book (https://land-book.com) and SiteInspire (https://www.siteinspire.com) so you can go and grab a few.
2. Three websites. Not three colour schemes of one page — three genuinely different readings of your brief: the straight read, the one built around a single bold idea, and a counter-proposal that questions an assumption you made. They render live in the page, side by side, and you can open any of them full size. Don't like them? Type what to change and get three more. Your brief is kept; your instructions are added on top.
3. A dashboard. Publish with one switch and the site is live over HTTPS at your PocketCorp address immediately. Point your own domain at it and the kit writes the nginx config and gets a Let's Encrypt certificate — one sudo approval, then it is done. Set a site to your PocketCorp login only while you are still working on it, and public when you are ready.
WHY THE DESIGNS DO NOT ALL LOOK THE SAME
Every design turn — the first three and every later edit — is briefed with Anthropic's frontend-design guidance, the same guidance Claude Code uses when it builds an interface: decide the palette, the two typefaces, the layout idea and the one thing the page will be remembered by before writing a line, and avoid the handful of looks every AI-designed page currently defaults to. It is carried in the request itself, not installed for one agent, so it still applies if you switch your PocketCorp to a different agent later. It is also installed as a skill your agent can use for anything else it designs.
AI IMAGES, IF YOU WANT THEM
One switch in the brief. There is no key to paste: your PocketCorp already has its own OpenRouter key, and the images come out of the same agent credit as everything else it does — around $0.03 each, up to four per design, generated to fit the page rather than pasted in. Off is a real choice, not a downgrade: the agent then designs with type, colour and SVG, which suits plenty of briefs better.
EVERY SITE COMES WITH A BACKEND
This is the part that usually stops people. Each website ships with a real FastAPI + SQLModel + SQLite API — one readable file — so the forms on your page have somewhere to post from the first minute. Contact forms and email signups always; private analytics with no cookies and no third party, payments ready to wire to Stripe, bookings that refuse double-booking, comments held for approval and database-backed content if your brief asked for them. A Data tab shows every table and lets you edit any value in place, so 'who filled in the form' is a click, not a database client.
TAKING MONEY IS ONE KEY
Payments is the step that normally defeats people: a Stripe account, a key, a webhook endpoint, a signing secret, then code. Here you paste the secret key and press Connect. The kit checks the key, registers the webhook against your site’s address, stores the signing secret, and restarts the API — you never open the Stripe dashboard again. Add what you sell by name and price and it becomes a real Stripe product; press Test a payment and you get a genuine checkout page, through your own site’s endpoint, with the order appearing in the Data tab and turning to paid when Stripe confirms it. Start on a test key, switch to live when you are happy. The checkout code is already in your API and needs no editing — it is inert without keys and live with them, and it verifies Stripe’s signature itself rather than trusting whoever posts to it.
AND IT KEEPS CHANGING
Every site has its own chat with your agent — the same chat as the PocketCorp dashboard, working in that website's folder. "Make the hero darker", "add a pricing page", "store the form submissions and email me a summary on Mondays". It edits the files, restarts the API and tells you what it did. The agent also gets the site's database as MCP tools, with guardrails: it cannot drop a table or wipe one without a WHERE clause, and it never publishes anything you did not ask it to.
NO LOCK-IN, MEANT LITERALLY
Download button, one zip: the page, its assets, the API, your data and a README that says how to run it anywhere else. Your secrets are the only thing left out.
Requires the Hermes agent (choose Hermes when deploying a new PocketCorp). During installation, approve the sudo prompts from your dashboard when asked — or enable auto-approval first, then it is hands-free. Adding a domain later asks for one more approval, for nginx and the certificate. The kit installs a small Python environment for the site APIs; nothing else leaves your server.