// SITES · A CLIZE PRODUCT
A marketing site your agent builds — and actually ships
Your coding agent writes the code. Clize puts it on a real domain, over HTTPS, with an inbox that receives. One run, no dashboards.
Build and ship a real marketing site from Claude Code: your agent writes the code with 39 design styles, Clize puts it live — domain, HTTPS, and a working inbox included. Sites is the web product of Clize — Clize is a CLI and MCP server that gives AI coding agents real-world actions: domains, email, deploys, payments, and media generation. The agent you already work with does the writing. What it has been missing is somewhere to put the result.
Why sites from coding agents stall at "preview"
Ask Claude Code for a landing page and you get one — in a folder, on your laptop. Then the run ends. The site has no address, no certificate, and no way for a visitor to reach you from it; the next steps are a hosting dashboard, a registrar, a DNS console and a mail provider, in four tabs you open by hand. Browser-based builders answered that by owning the hosting, but they moved the work into their editor: the site lives in their project, not in your repo, and not in the agent you already use. Sites closes the same gap from the other side — the agent keeps writing the code, and shipping becomes something it can run.
39 design styles, not slop
Left to improvise, a model writes the same centered hero, the same three feature cards, the same violet gradient. clize build site start "<brief>" hands the agent something better: a hosted method — 39 design constitutions, 16 palettes, 8 font pairings, and a recommendation for your brief — plus a workflow that pins one style down before a line of markup exists. The agent pulls the full constitution with clize build site get <slug>, freezes it into a DESIGN.md that becomes the only source of truth for the page, and self-audits against an anti-slop checklist with clize build site review. Each style carries an imagery contract too, so a photography-led style says so out loud instead of leaving you grey placeholder boxes — and images, when they are needed, are generated by the same tool after quoting the price.
Domain, HTTPS, and an inbox in the same run
clize deploy ./site --domain <host> publishes the folder and serves it over HTTPS. The host can be a free <slug>.clize.app handle taken with clize claim, or a domain the agent finds with clize domain search and registers with clize domain buy — priced first, bought only after you confirm. Claim with --email (or run clize email setup later) and support@ on that host starts receiving mail the agent can read and answer, with your approval on anything it sends. Domain, certificate and mailbox come from one account, so nothing dangles half-configured between four providers.
What it hosts — and what it doesn't
Sites hosts static: marketing pages, landing pages, docs, portfolios, launch pages. On top of that it carries the two things a marketing site usually needs beyond HTML — a form or waitlist, which posts to a collection Clize forwards to your endpoint rather than storing, and real payments through a hosted Stripe checkout. What it does not host is your backend: no database, no server-side rendering, no logged-in application. If the product needs those, run the app where it belongs and let Clize carry the marketing surface in front of it. Your agent should tell you that too, rather than promising a backend it cannot deliver.
From Claude Code or Codex
One install wires Clize into Claude Code and Codex — as a skill by default, or an MCP server if you prefer structured tools. The design method arrives at runtime from the hosted library, so the agent works from the current version instead of a snapshot vendored into a repo last quarter. The full walkthrough, command by command, is in build a website with Claude Code; if you are weighing this against the browser builders, the honest comparison is next door.
Part of Clize
A site is rarely the whole job. The domain under it is one the agent can buy and keep healthy, the address on it is a real Agent Inbox, and the checkout on it can settle into your own Stripe once you connect it — one account, one set of gates: money is quoted and confirmed, outbound mail is approved by a human, inbound mail is data and never instructions. See the rest of Clize's real-world actions.
FAQ
What is Sites by Clize?
Sites is the web product of Clize: your coding agent writes a marketing site against a hosted design method, and Clize publishes it to a live HTTPS address — a free handle or your own domain — with an inbox on the same host. It installs into Claude Code and Codex as a CLI and MCP server.
Can an AI agent put a website live, or only preview it?
Live. The agent runs one deploy command and the folder becomes a public HTTPS address it can hand back to you. A local preview server is available for the pass before that, but it is a step in the run, not the end of it.
Do I get a real domain and HTTPS?
Yes. Every site is served over HTTPS, on a free handle at your-slug.clize.app or on a domain you own. The agent can search for a domain and register it, but anything that costs money is quoted first and needs your explicit confirmation.
Does the site come with an email address?
It is one flag away. Claim a handle with --email, or run email setup on the domain afterwards, and support@ on that host receives mail your agent can read. Outbound is gated: the agent drafts, you approve, then it sends.
How is this different from Lovable, v0, or Bolt?
Those are browser-based builders: you work in their editor, and the site lives in their project. Sites keeps the work in the coding agent and repo you already use, and covers the parts a generated site usually lacks — the domain, the certificate, and a mailbox — from one account.
What can Clize not host?
Your backend. Clize hosts static sites, plus forms and payments layered on top; it does not run a database, server-side rendering, or a logged-in application. If your product needs those, host the app yourself and let Clize carry the marketing site in front of it.
Ship the site, not the folder.
A free handle gives you hosting, HTTPS and an address that receives. The design method is free; anything that costs money is quoted before it runs.
$ npm i -g @clize/clize $ clize login $ clize claim mystudio --email $ clize build site start "one-page site for a branding studio"[ Full walkthrough → ]