Core Philosophy

Axolot was born from a frustration with "Dashboard-First" CMSs. We believe that in 2026, a CMS should not be a separate silo, but a seamless extension of your development environment.

1. Code is the Schema

Traditional headless CMSs force you to define "Content Types" in a UI, then map them to your frontend code. This creates a brittle link. In Axolot, your code defines the content. If you add a new data-slot in your editor, that field exists. If you delete the code, the field is archived. No synchronization lag.

2. Zero-Runtime, Zero-Bloat

Most "visual" CMSs inject heavy JavaScript libraries to enable editing. Axolot takes a Surgical Approach. We use the local file system during development and pure Static Site Generation (SSG) or Server-Side Rendering (SSR) for production. Your users receive 0kB of CMS-specific code.

3. The Semantic Contract

By using the data-slot system, you aren't just tagging elements for a visual editor; you are creating a semantic contract for AI agents. Your AI assistant doesn't see a random <h1>; it sees a piece of content with a specific key and purpose, allowing it to generate high-quality, contextual updates.

4. Hybrid Control

"Your Data, Our Studio". We don't want to own your data. Axolot is built to connect to your own PostgreSQL instance. We provide the management layer (the AI-powered dashboard and MCP servers), while you retain full control over your infrastructure.