Instatic hands your whole CMS to an agent, tool by tool
Instatic is a self-hosted visual CMS that doubled its GitHub stars overnight, sitting near 5.6k and climbing fast on the daily trending page. On the surface it's another Webflow, Framer or WordPress alternative: design, content and publishing in one app, outputting clean semantic HTML instead of framework bloat. What's pulling the stars is the part underneath.
Every other builder now claims AI editing, usually meaning it spits out a screenshot or a wall of code. Instatic's agent actually edits the page. You describe the change and it builds real, editable nodes right on the canvas, the same nodes you'd drag around by hand. It talks to Claude, OpenAI, OpenRouter or a local Ollama model, so you're not locked to one provider or a cloud you can't turn off.
The detail that matters isn't the demo, it's the shape. The whole product is built as a tool surface an agent operates. There's a Site scope with 35 tools for building pages and a Content scope with 15 for editing entries, and plugins run in QuickJS-WASM sandboxes with explicit permissions. So an agent isn't clicking pixels or guessing at your DOM, it's calling a real, permissioned API for your website, with a sandbox around anything third-party. Bun and TypeScript throughout, SQLite or Postgres, MIT licensed.
This is the pattern worth noticing. The interesting agent-native software of 2026 isn't the stuff that bolts a chat box onto an old app. It's the stuff rebuilt so that a human and an agent reach for the exact same set of tools, with permissions drawn around the dangerous parts. Instatic is a clean, small example of what that actually looks like: https://github.com/CoreBunch/Instatic
← Back to all articles
Every other builder now claims AI editing, usually meaning it spits out a screenshot or a wall of code. Instatic's agent actually edits the page. You describe the change and it builds real, editable nodes right on the canvas, the same nodes you'd drag around by hand. It talks to Claude, OpenAI, OpenRouter or a local Ollama model, so you're not locked to one provider or a cloud you can't turn off.
The detail that matters isn't the demo, it's the shape. The whole product is built as a tool surface an agent operates. There's a Site scope with 35 tools for building pages and a Content scope with 15 for editing entries, and plugins run in QuickJS-WASM sandboxes with explicit permissions. So an agent isn't clicking pixels or guessing at your DOM, it's calling a real, permissioned API for your website, with a sandbox around anything third-party. Bun and TypeScript throughout, SQLite or Postgres, MIT licensed.
This is the pattern worth noticing. The interesting agent-native software of 2026 isn't the stuff that bolts a chat box onto an old app. It's the stuff rebuilt so that a human and an agent reach for the exact same set of tools, with permissions drawn around the dangerous parts. Instatic is a clean, small example of what that actually looks like: https://github.com/CoreBunch/Instatic
Comments