The CMS for
the agentic era.
Agent-native by design.
Built for production.
A discoverable schema. Typed content. Explicit permissions. Give agents the tools to work inside your rules, from the first draft to a controlled publish.
Watch it happenIllustrative translation workflow: read the source content, prepare an English draft, and leave it ready for editorial review. Published content is unchanged.
Agents need more than a prompt.
Give them structure, context, and rules.
Agents do the work.
Your rules define the boundaries.
First, the agent explores your content and relationships. Then a menu PDF arrives in the conversation: it reads the file, prepares dish drafts, and connects them to the existing menu. Your published content stays unchanged.
A conversation starts it.
Structured content makes it real.
Event details, photos, and a menu become connected Event and News drafts through MCP. The hotel website shows the result. Publishing remains a separate decision.
Every piece of content connects.
Your model brings it together.
Explore a connected content model through Northstar Collection, our fictional hospitality example. Every category has a place, every relationship carries context.
A model agents can discover.
Categories, typed fields, and relationships describe what content means. Agents read that structure before they write.
Context that stays connected.
Content is linked and reusable. An agent can follow existing relationships and extend the model without flattening everything into a page.
Rules beyond the prompt.
Tool permissions, tenant scope, validation, and version states are part of the system agents work with.
Production starts
with explicit rules.
Drafts, review states, validation, and publishing permissions give content changes a defined path to production.
- Draft
Work in a draft.
Create and edit a draft while the published version stays in place.
- Review
Review the changes.
Move a version into review. Check the content and its validation results.
- Publish
Publish with permission.
Publish with the right permissions and keep previous versions available.
More than one language. Manage content versions per language.
More than one project. Organize content across tenants.
Your rules. Your content.
Your choice of frontend.
Entity holds the structure and the rules. People and agents work within them. Your frontend consumes the content through the API.
Two ways in.
Give your assistant the context to create and update content.
EntityCMSYour business object, modeled as an entity. Its relationships carry the context.
Northstar
Connected teams. Shared work.
Northstar
Connected teams. Shared work.
{
"name": "Northstar",
"category": "Organization",
"relations": {
"contact": "Alex Morgan",
"location": "London",
"service": "Content ops",
"media": "network.jpg"
}
}The same content, ready for your integration.
Same entity. Your website’s design.
Fields, categories, and relationships give every change a defined structure.
Agent tools operate with explicit roles and tenant access.
Draft, review, and publish states keep changes and release decisions explicit.
One illustrative business object. Three delivery views.
Your frontend. Your implementation.
Built for agents.
Grounded in rules.
The content infrastructure for your next production system.
Structure, relationships, and controlled publishing.