Open-source tools for developers. Studio workflows for teams.

Govern the content your AI ships into code.

Contentrain turns hardcoded UI copy, docs, and structured content into a Git-native system that AI agents can safely operate. Start locally with MCP, CLI, and SDK packages; add Studio when teams need review, roles, media, and delivery.

Open Studio

Contentrain turns scattered interface strings into structured, governed content.

MIT packages 24 MCP tools 4 model kinds 27 field types 15 agent skills AGPL Studio core GitHub + GitLab providers MIT packages 24 MCP tools 4 model kinds 27 field types 15 agent skills AGPL Studio core GitHub + GitLab providers

The Problem

Your content was already scattered in time. AI makes it spread faster.

UI copy, docs, and locale strings already live across components and files. AI agents now create and change them faster multiplying the same governance problem.

Hard to review
Hard to audit
Hard to localize
Hard to scale

Scattered component, documentation, and locale files connected by fragmented workflows and warning markers.

One governed content system

Agent generates. Human approves. Git records every change.

The same typed content models power local developer tools and Studio workflows. Start in the repository, then add editing, roles, and review without moving content to a separate source of truth.

Developer Tools

MCP, CLI, SDK, types, rules, and skills for bounded, framework agnostic content operations inside your repository.

Explore developers

Contentrain Studio

Structured editing, roles, and review for teams working on the same Git-backed content models, with media and delivery where enabled.

Explore Studio

Contentrain Studio

Ask for a change. Studio finds and updates the content.

No more digging through models and fields to find the right content. Just tell Studio what you want to change, and its project aware AI finds and updates it within your Git-backed workflow.

Explore Studio View Studio docs

Contentrain Studio interface for editing and reviewing governed content.

From hardcoded copy to governed content

Start with the mess already in the codebase.

Most teams do not wake up needing a new content platform. They wake up with hardcoded copy, no reliable translation path, and AI agents editing strings directly in source files.

See normalize

Scan

Find user-visible strings with project context.

Extract

Create models and content files in Git.

Review

Approve branches before changes become production content.

Choose your path

Start with the workflow you need today.

Choose the path that matches how you work now. Expand into the same Git-native content system as your product and team grow.

View pricing

Repeatable content infrastructure

Reuse models, Git workflows, and Studio review across client projects.

Govern the content your AI ships

Turn AI-generated UI copy, docs, and locale strings into structured content you can review and reuse.

Let non-developers edit without losing Git control

Editors work in Studio. Developers keep branches, diffs, validation, and source-of-truth control.

One content contract for web, mobile and APIs

Deliver structured content to web, docs, mobile, and APIs from the same Git-backed system.

Control by design

Governance is part of the workflow. Not an add-on.

Content stays in Git. Models constrain its structure. Bounded tools, validation, branches, diffs, and review keep changes inspectable before they reach production.