Run the core yourself, license the enterprise layer when needed
Self-hosted Contentrain lets teams run Studio and the content governance stack on controlled infrastructure while keeping the Git-native model, MCP workflows, and open-core upgrade path.
Deployment
Run the same Git-native operating model yourself
Self-hosting is valuable because the content model does not change. Studio still operates content through schemas, files, validation, branches, commits, and review paths.
- AGPL Studio codebase
- Git-backed content operations
- Branch and diff review surfaces
Infrastructure
Own the infrastructure integrations
The Studio codebase includes Supabase, Redis, S3-compatible storage, GitHub integration, billing hooks, media processing, and delivery surfaces. Self-managed teams can place those pieces under their own operational policies.
- Database and auth integration points
- Object storage and media processing paths
- Repository provider and webhook surfaces
AI operations
Keep AI key strategy under your control
Workspace AI keys, managed usage surfaces, and provider abstractions make key ownership a deployment decision. Some teams can bring provider keys; others can use managed paths in the SaaS product.
- BYOA workspace key management
- Usage and overage controls
- Provider-level boundaries
Enterprise
Use enterprise licensing when operations exceed AGPL fit
The open-core path should be clear: community users can inspect and run the core, while enterprise customers pay for licensed features, support, and self-managed operational requirements.
- Enterprise bridge in the Studio codebase
- License checks and enterprise feature paths
- Commercial support for controlled environments
Developer path
Self-hosting still benefits from the MIT packages
The local packages remain useful even when Studio is self-managed. CLI, MCP, SDK, rules, and skills keep developer workflows portable across local development, CI, and hosted operations.
- Local CLI and MCP workflows
- Generated SDK access
- Shared validation and agent rules
Common questions
Is self-hosting only for enterprise customers?
No. The AGPL Studio core supports self-managed use, while commercial licensing is the path for teams that need enterprise terms, support, or licensed capabilities.
Does self-hosting change the content format?
No. The content remains Git-native JSON and Markdown governed by Contentrain schemas, validation, and generated access.
Can self-hosted teams still use the open-source packages?
Yes. The MIT packages are useful in local development and CI even when Studio runs in controlled infrastructure.
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.