This very page proves the point. The site you are reading was authored, built, and published by the fastsite engine — the same engine you can point your own content at.
What fastsite is
An ultra-lean static publishing engine. Content comes in over REST, a signed webhook, MCP, or the dashboard; it lands in per-site SQLite; the engine renders fully static HTML, commits it to git one commit per publish, and Cloudflare Pages serves it. Not a CMS — there is no runtime, no client-side framework, and nothing to hydrate.
Why zero JavaScript
The fastest script is the one you never ship. Every page here is inlined, minified CSS and pre-rendered HTML. A build-time audit refuses to publish a page that ships a <script>, loads an external resource, or drops an image dimension — so a perfect PageSpeed score is a property of the pipeline, not a thing you chase.
Built for agents, too
fastsite treats an AI agent as a first-class author. The MCP server exposes the whole engine as tools; an agent designs the shell, writes content, imports images, translates into new languages, and publishes — all under OAuth consent and per-scope control. The authoring guide is served in a machine-readable form so the agent knows the rules before it starts.
What is new
- Teams — share a site with your collaborators by email invite.
- Per-user GitHub credentials — each publisher uses their own token; nothing shared, nothing in a config file.
- A WYSIWYG editor — write bodies visually, drop in components, or flip to raw HTML.
- Redirects & trash — canonical-host control, manual redirects, and soft-delete you can undo.
Design a shell once, and let humans and agents fill it forever. Start with how it works, then the MCP reference or the REST API.