A real CMS inside every website.
Model the content a website actually needs, then let non-technical people edit it safely. No second product to buy, run, or wire up.
- Custom collections per website
- Draft and publish per item
- Safe renames, references intact
Model the content the website needs.
Case studies, listings, menus, team pages, a journal. Collections are defined per website, so the schema fits the site instead of the site fitting a template.
Rich field types
Text, rich text, numbers, dates, options, colors, references, images, galleries, and downloadable files.
References between collections
Authors on posts, clients on case studies. Relationships are real, not a text field holding a name you have to keep in sync.
Per-item drafts
Every item carries its own draft and published state, so an editor can stage next month’s work without it appearing today.
Manual ordering
When the order is the design, drag the items into it. When it is not, sort by whatever field you like.
Safe restructuring
Rename a field and existing data migrates with it. References survive. A restructure does not break the live website.
Publishing without a rebuild
Published websites read published items at request time, so an editor pressing publish is live immediately, with no build to wait for.
Content that does not fight the website.
The old way
With Cactal
A separate headless CMS to choose, pay for, and integrate
The CMS is part of the website, already connected
Editors who can accidentally break the layout
Editors work in structured fields, never in the design
A schema change that means a migration project
Rename and reshape, with data migrated for you
Content changes that need a developer to deploy
Publish an item and it is live at once
CMS questions
Modelling something unusual? Talk to us. Talk to us.
No. It is built into every Cactal website. Content, source, hosting, publishing, and analytics are one platform, so there is nothing to integrate and nothing that can fall out of sync.
Yes. Editing content and editing the website are separate. A collaborator can be given content-only access, which lets them write and publish items and nothing else.
Yes. Pages generated from collection items are real routes with their own metadata, and they appear in the sitemap automatically as items are published.
Yes. Collections, fields, and items are all part of the public API and the MCP server, so an agent can model a schema and fill it, or bulk-edit items you would rather not touch by hand.
