Hard to find
Content is buried in code, admin panels and old platforms. People and agents search for it, and explain it again, before every change.
One content layer for your team and AI agents, with shared rules, Git history and review built in.
It's spread across code, admin panels and old platforms, and edited by developers, editors and AI agents. Each place has its own rules, so the same work gets done again and again.
Content is buried in code, admin panels and old platforms. People and agents search for it, and explain it again, before every change.
The same text lives in several places. Update one, and the rest drift: pages, languages and channels fall out of sync.
Content tied to one codebase or platform gets rebuilt for the next page, language, app or site.
Editors, developers and agents work in separate places, so routine edits wait on someone technical and every project gets its own admin panel.
Four things keep content in order, whoever makes the change: a developer, an editor or an AI agent.
Content lives in models and fields, outside the code but connected to it. People and agents find it by name, and the same content is reused across pages, languages and apps.
Developers work in code, editors in Studio, agents through MCP, and all of them follow the same rules for each model. Changes are checked against those rules, so content stays consistent everywhere it appears.
Every change is saved in Git, on its own branch. You can see who changed what and when, and earlier versions are never lost.
Agents can draft and propose changes. People review and approve them before anything goes live.
Each product handles one part of the content work, on the same structure. Use the one you need; add others only when the job calls for it.
Pull hardcoded content out of your code, define models, and let agents find and change it through MCP, CLI and SDK.
Read the docs →Your team and agents work on the same content through conversation: ask for a change, attach media, and approve it before it goes live. Run it in the cloud or on your own machine.
Start a free trial →Move a WordPress site to Astro, with its content and templates, into a project you own.
Start with free discovery →A free WordPress plugin that turns your posts, pages, media and interface text into structured Markdown and JSON. Download it as a ZIP or send it to a new branch in your own GitHub repo. Your site stays untouched.
Download Bridge →Website Builder, a documentation app and app store content management, built on the same structure.
A few of the jobs teams and agents hand to Contentrain.
Editors run articles, images, categories and bulk updates by asking for them, and approve each change before it's published.
Try Studio →Add a language without copying pages. Agents fill in the new language on the same content, and editors review it.
Read the localization guide →Deliver a client site whose content the client can manage, without building a custom admin panel for every project.
Start with the open-source tools →Take a WordPress site to Astro with its content and templates, or export the content first and decide later.
Start with free discovery →Guides for common content problems, side-by-side comparisons, and the tools Contentrain works with.
Step-by-step pages for the content work teams run into most.
See how a Git-based content workflow differs from database-first CMS platforms.
Use Contentrain with the AI agents, Git providers and frameworks already in your workflow.
In your code, with your team, or on a WordPress site, there's a way in that fits.
Set up the content layer in your project and give agents a way to work with it.
Ask for changes in conversation and approve them before they go live.
Move your site to Astro, or export your content first with the free plugin.