MIT packages and an AGPL Studio core
Contentrain uses an open-core model: MIT packages create the developer adoption channel, while the AGPL Studio app provides the team collaboration and commercial surface.
MIT packages
Six MIT packages create the developer channel
The open-source package set covers the CLI, MCP server, JavaScript query SDK, shared rules, agent skills, and shared types. This gives developers a complete local path before Studio enters the workflow.
- CLI for init, validate, generate, normalize, serve, and Studio commands
- MCP for local and HTTP agent operations
- SDK, rules, skills, and types for runtime and agent quality
Studio
The AGPL Studio app is the commercial surface
Studio is larger because it handles team problems: authentication, workspaces, projects, chat, content editing, branch review, media, CDN, forms, webhooks, billing, and usage. That is where SaaS and license revenue can live.
- Nuxt 4 application with server APIs
- Workspace, project, member, billing, and usage modules
- Enterprise bridge and licensed feature paths in the codebase
Standards
Shared standards keep both sides aligned
The packages and Studio share the same vocabulary around model kinds, fields, validation, and content files. A local project should not become a different product when it graduates to Studio.
- Shared types and schema concepts
- Rules-based validation and content quality
- Generated query access for application runtimes
Funnel
Open source is the wedge, not the end of the funnel
The strongest adoption path is practical: run init, normalize real strings, generate client access, and ship. Studio becomes relevant when a second person needs to review, approve, localize, or deliver content.
- Developer trust through local-first tooling
- Team upgrade through review and permissions
- Commercial expansion through delivery and enterprise controls
Portability
No lock-in is the strategic trust signal
Content lives as files and code can import generated clients. That makes Contentrain easier to adopt in AI-built apps because the system is visible to both developers and agents.
- Plain JSON and Markdown content state
- Git history as the audit log
- Platform-independent runtime consumption
Common questions
Why not make everything MIT?
The MIT packages create adoption and trust. Studio solves collaboration, delivery, billing, and enterprise problems that can fund the ecosystem.
Can teams use only the MIT packages?
Yes. A solo developer or technical team can run local workflows without Studio. Studio becomes useful when collaboration and governance become recurring needs.
What is AGPL used for?
The Studio app is AGPL in the open-core model, with commercial SaaS and licensing options for teams that need managed or enterprise operations.
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.