Govern the content your AI ships into code.
Contentrain turns hardcoded UI text, docs, and structured content into a Git-native content layer. Developers start with MCP, CLI, and SDK packages. Teams scale with Studio.
$ npx contentrain init
Scanning project graph...
Found 523 hardcoded strings in 47 files
Creating governed models...
✓ marketing/hero (singleton)
✓ ui-labels (dictionary)
✓ feature-cards (collection)
Review branch ready: cr/normalize/extract/marketing
The operating model
One contract. Two adoption surfaces.
The MIT repo gets structured content into Git. Studio helps teams review, operate, and deliver that content.
Normalize is the wedge
Start with the mess already in the codebase.
Most teams do not wake up needing a CMS. They wake up with hardcoded copy, no translation path, and AI agents editing strings directly in source files.
See normalizeScan
Find user-visible strings with project context.
Extract
Create models and content files in Git.
Review
Approve branches before changes become production content.
Launch map
Choose the route that matches your intent.
Solution
Repeatable content infrastructure for every client project
Agencies can start each client with the same Git-native content workflow, template-driven models, Studio review, and delivery surface.
Solution
Govern the content your AI coding workflow creates
AI coding makes product surfaces faster to ship, but it also spreads copy, labels, docs, and locale strings across components. Contentrain gives that output structure, review, and reuse.
Solution
Let non-developers change content without losing Git control
Editors, marketers, translators, and reviewers can work through Studio while developers keep branches, diffs, validation, and source-of-truth control.
Solution
One content contract across web, docs, mobile, and backend systems
Platform teams can standardize content operations around plain JSON, generated SDK access, CDN delivery, and provider-backed Git workflows.
SEO and GEO routes
Use cases, comparisons, integrations, and templates.
Use cases
Comparisons
Integrations and templates
Claude Code, Cursor, Windsurf, GitHub Copilot, Cline, Continue, Aider, Any MCP client, Nuxt, Next.js and more. Starter templates mapped for expansion.
Start local. Scale to Studio.
Build a governed content layer before content becomes product debt.
Developers can start with the MIT packages. Teams can move into Studio when review, roles, delivery, and licensing matter.