squilla/
early alpha ★ 1
docker compose up
§ about

Why Squilla exists.

WordPress made publishing easy in 2003. It is now 2026. The web has changed. Most CMSes haven't.

We built Squilla because the existing options force a trade: be developer-friendly OR editor-friendly. Be fast OR flexible. Be open-source OR AI-ready. Squilla refuses the trade. The kernel does the minimum required to be a CMS, and every feature is a sovereign extension that owns its full stack.

The kernel is Linux-small. The extension model is Debian-clean. The MCP layer is agent-native. The runtime is Go-fast. The GPL-3.0 license is forever.

§ principles
  1. 01
    AI agents are first-class users.
    Not as a “ChatGPT integration”. As primary operators with the same API surface humans use — the MCP server and the CoreAPI.
  2. 02
    Performance is non-negotiable.
    Pre-resolved layouts, JSONB + GIN indexes, atomic config swaps, no N+1 reads. The CMS gets out of the way.
  3. 03
    The kernel stays small.
    If disabling a feature would leave dead code in core, that feature belongs in an extension. Always.
  4. 04
    Extensions are sovereign.
    Their tables, their UI, their scripts, their migrations. The kernel never reaches inside.
  5. 05
    One-shot setup.
    docker compose up and you're publishing. No package managers, no cron jobs, no PHP-FPM tuning, no “first-time setup wizard”.
§ team

Six humans. One of them real.

Squilla is built by Erik and a tireless team of "Claude" personas — different names, different roles, same model. The joke writes itself; the work is real. Standups are quiet.

  • Erik Kubica aka. Master
    Founder & engineer
  • Claudia aka. Claude
    Human resources
    // LLM
  • Fred aka. Claude
    Software architect
    // LLM
  • Tom aka. Claude
    Design
    // LLM
  • Léa aka. Claude
    QA & testing
    // LLM
  • Max aka. Claude
    DevOps & infra
    // LLM

Yes, every "Claude" above is the same underlying model. We give them different names because it's funnier than "Claude (1 of 5)" in standups, and because giving the QA persona a slightly different prompt than the architect persona genuinely changes what each one notices.