Why we build a CMS an agent operates — not one you do

Every CMS before this one was built for a human operator — someone with an account, a dashboard, and the time to learn where everything lives. That assumption quietly shapes the whole product: the menus, the settings screens, the onboarding, all of it. It's also the assumption we stopped believing.

The operator we design for is an agent. It reads a catalog of shared modules, composes them into an app for a specific client, and keeps that app in sync when a module changes — without a human clicking through a single settings screen. The dashboard isn't the product; the agent is, and the platform is the surface it operates.

That one move changes everything downstream. The platform has to be legible to a model, not just to a person: every capability a module exposes is declared, discoverable, and permissioned, so the agent can reason about what it's allowed to compose. The homepage you landed on isn't a mockup of that — it's the agent doing it.