No database. No server. No lock-in. Your site is a folder of files in a repository you own; an agent edits it and two platforms serve it. This is everything that happens.
in plain languageTell an AI agent what you want, in any language. No syntax, no admin panel to learn.
read schema.ts · write .md/.htmlThe agent reads your content model, edits the right files, and saves the change as a commit, exactly like a developer would.
git push origin mainYour repository is the source of truth. Every version is recorded and reversible. The repo belongs to you: take it anywhere, any time.
astro buildA static build compiles the files to plain HTML. Nothing to run in production, nothing to hack, nothing to patch.
300+ cities · cachedYour site goes out from Cloudflare's network, close to every visitor. Page views are unmetered, so it is fast everywhere, and free.
sitemap.xml · llms.txtIt's a real site on the open web, with real URLs, structured data, and a contract for agents. Discoverable by design.
Nothing here was invented. Astro renders, Git remembers, Cloudflare serves, and one small broker holds the secrets so your site never has to. What Lanza does is wire them together and then get out of the way.
astro buildAstro compiles components to HTML ahead of time and ships no framework to the browser. The rendering code is not in your repository: it lives in the lanza-site npm package, and Astro's srcDir points into it. Your repo holds words, data and templates. The templates are ordinary HTML with {{placeholders}}, which is what lets an agent write one and a person still read it.
git push origin mainEvery page is a file. Every save is a commit on the staging branch, and publishing is a merge into main. That is the entire publishing model. There is no database, so there is nothing to migrate, nothing to back up and no export feature to build: git clone is the export, and git revert is the undo.
push → build → edgePages watches the repository, runs the build on every push, and serves the result from around 300 cities. Page views are unmetered, so traffic never moves the bill. Branch previews are what make staging real: your draft gets its own URL, built by the same pipeline as production. A handful of Pages Functions cover what cannot be static: the /admin gate, the GitHub proxy and /api/mcp. Every public route stays static and cached.
connect.lanzacms.comYour site is a tenant, and a tenant holds no private key: it ships with a public one and can only verify. The broker is the other half. It runs onboarding, signs a short-lived RS256 session naming your GitHub login and your site's origin, and mints a GitHub token per save, scoped to one repository and good for about an hour. Your site checks the signature, then checks separately that the person is an owner: a valid signature proves someone signed in, not that the site is theirs.
This is a whole Lanza site. The code arrives as a dependency at a version you choose, so nothing we publish reaches your site until you take it.
npm install && lanza build produces the same static site Cloudflare builds. Clone it, run it, take it somewhere else; nothing in that tree needs us.
Astro + Git + Cloudflare Pages, all on the free tier. No database to run, no runtime to keep alive. Skip the connect.lanzacms.com wizard entirely: fork it, self-host it, point your own agent at the same content model. Nothing here holds you in.
Lanza was made this way on purpose. The CMS, the render engine, this page and the site around it were built with Claude Code: an agent working in the same repository, through the same commits and the same reviews a developer would use. A tool for editing a site by talking to an agent ought to be built by talking to an agent. And the proof is public: the whole history is in the repository, mistakes included.