What Pluma is
Pluma is a headless CMS: it stores your site's content (posts, events, pages, settings) and serves it by API to any frontend. Astro, Next, Nuxt, Eleventy, a mobile app: it doesn't matter.
The difference is who it's made for. In Pluma the main user is the site owner's AI agent. Anything a person does in the dashboard, an agent can do by API or by MCP, reading the same docs.
How you use it
- You create your site in the dashboard.
- You give your agent an invite link.
- The agent reads
/llms.txt, looks at your current site, proposes how to model the content and imports it as drafts. - You review and publish. Your site rebuilds by itself.
How it's different
| Contentful, Sanity | Strapi, Payload, Directus | Pluma | |
|---|---|---|---|
| Made for | Content teams | Developers | AI agents and the site owner |
| How a new site starts | A person models it in the UI | Code and configuration | An agent models it from a link |
| Docs | For people | For people | Docs first, with an llms.txt per site |
| Errors | Code and message | Code and message | Message + how to fix it + link to the docs |
| Hosting | SaaS | You run it yourself | SaaS, 49 USD per site per month |
For agents
If you are an agent: everything you need is in /llms.txt. Pages marked "pending" describe something that doesn't exist yet; don't use them as if it did. Everything you create starts as a draft, and publishing needs a separate permission.