Use Git as the storage and audit layer for content
Content stays in your repository as JSON and Markdown. Branches, commits, diffs, and merge rules remain visible.
Storage
Git can be the content storage and audit layer
Contentrain stores structured content as files that developers, agents, CI, and reviewers can inspect. The CMS behavior comes from models, validation, generated access, and Studio operations around those files.
- Plain JSON and Markdown content
- Model schemas in the repository
- Git commits and branches as the audit trail
Schema
Models make files safe to edit
A Git-native CMS still needs structure. Contentrain models define required fields, field types, i18n behavior, and content kinds so file-based content does not become arbitrary JSON.
- Singleton, collection, document, and dictionary model kinds
- Required fields and typed field definitions
- Validation before generated access or delivery
Runtime
Generated SDK access removes parsing work
Applications should not hand-roll file parsing for content. The SDK generates query access so frameworks can consume content predictably across locales and build modes.
- Generated JavaScript client
- Locale-aware query API
- Framework integration skills for modern stacks
Editing
Studio adds the missing non-developer workflow
Git alone is not enough for content teams. Studio provides editing, chat, media, review, roles, and delivery surfaces while keeping Git as the source of truth.
- Content panels for each model kind
- Chat-driven governed operations
- Branch review and moderation
Portability
You keep the exit option
Because content remains in the repository, teams are not locked into a proprietary database to access their own content. Studio adds convenience and delivery without hiding the underlying state.
- Portable file content
- Provider-independent architecture
- SaaS and self-managed options
Common questions
Is Git enough for non-developers?
Not by itself. That is why Studio exists: it gives non-developers a usable interface while preserving Git-backed review and validation.
How is this different from a headless CMS?
Contentrain starts from repository-native content and AI-agent workflows, then adds Studio for teams. Many headless CMS products start from a hosted content database.
Can content still be delivered through an API?
Yes. Studio adds CDN and API surfaces when runtime delivery is needed.
Next paths
Continue through the content system
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.