---
title: What is Quilium
description: Quilium is a structured SaaS CMS with a templating layer and first-class AI agents, so your team and your agents build on the same foundation without stepping on each other.
updated: 2026-06-21
next: quickstart
---

## What it is

Quilium is a hosted content management system built around **structured content** and **templates**, with a native [MCP](/en/docs/ai-mcp-skills) server so AI agents can build and edit a site the same way a developer does.

You model your content once as typed objects, ship a template that renders it, and from then on the content evolves without touching code. The same site can be driven by hand through the CMS, through the CLI, or through an agent like Claude.

![Types define the site, editors fill the content, Quilium renders it. Editors, developers and AI agents all drive the same objects.](/thumbs/673d8100-aa3f-11f1-a95c-915afd69b951.svg)

## Who it is for

- **Web designers** who ship templates and hand the content over to editors.
- **Developers** who automate content operations through the CLI and MCP.
- **AI agents** that scaffold types, write templates and fill content under human review.

## The three building blocks

A Quilium site rests on three objects. Telling them apart prevents most modelling mistakes.

| Object | Role | Example |
|---|---|---|
| `page-type` | The template for a single page, with its content zones. | Home, Contact |
| `content-type` | A reusable block dropped into a page. | Hero, Gallery, Quote |
| `collection` | A managed set of structured, listable entries. | Articles, Members, Events |

For the full mental model and a decision table, see [The content model](/en/docs/content-model).

## Two ways to build

You can build a Quilium site through two paths that lead to the **same** result. Pick the one that fits you, the docs cover both.

- **AI path (recommended).** You start from a prototype and let specialized agents do the work: an architect agent decides the structure, a template agent writes the Liquid templates, a content agent fills the site. You review and publish.
- **Manual path.** You scaffold types, write templates and add content yourself through the CLI and the CMS.

Both paths share the same prerequisites: a Quilium account, the CLI installed, and a site created.

## Where to go next

- [Quickstart, 2 min](/en/docs/quickstart), run Quilium on a ready-made demo, no AI.
- [The content model](/en/docs/content-model), understand when to use each building block.
- [AI, MCP and skills](/en/docs/ai-mcp-skills), why Quilium exposes an MCP server and a skills library.