Free open-source packages. Studio plans for teams.
Pricing should match the adoption path: free MIT packages for developers, Studio plans for team workflows, and enterprise licensing for controlled infrastructure and advanced operations.
Bring your own AI key
Connect your own Anthropic account on Pro and Enterprise — pay for AI usage at cost.
Open source
$0 MIT packages
MCP, CLI, SDK, types, rules, and skills. No account needed.
Install CLI- Local-first workflows
- Normalize hardcoded strings
- Generated SDK
- Local review UI
Starter
$9 per month
For solo developers and small projects using Studio.
Start trial- 3 seats
- 150 AI messages/month
- Studio-hosted AI key
- CDN delivery
Pro
$49 per month
For teams that need collaboration and higher limits.
Start trial- 25 seats
- 1,500 AI messages/month
- Bring your own AI key (BYOA)
- Conversation API access
Enterprise
Custom cloud or self-managed
For organizations needing dedicated support, SSO paths, white-label, and custom limits.
Talk to sales- Unlimited seats and custom limits
- Enterprise self-managed licensing
- SSO and white-label roadmap
- Dedicated support
Usage limits and overages
Each paid Studio plan includes a monthly allowance for metered usage. Turn on overages in Studio to keep working past your plan's limits — otherwise usage pauses until the next billing cycle.
| Metered usage | Starter | Pro | Enterprise | Beyond your plan |
|---|---|---|---|---|
| AI messages | 150 / mo | 1,500 / mo | Unlimited | $0.03 each |
| API messages | 100 / mo | 3,000 / mo | Unlimited | $0.05 each |
| MCP Cloud calls | 5,000 / mo | 150,000 / mo | Unlimited | $0.005 each |
| Form submissions | 100 / mo | 3,000 / mo | Unlimited | $0.01 each |
| CDN bandwidth | 2 GB | 60 GB | Unlimited | $0.10 / GB |
| Media storage | 1 GB | 15 GB | 100 GB | $0.25 / GB |
Overage pricing is per unit, in USD, and requires an active paid subscription. Seats are fixed per plan (Starter 3, Pro 25; Enterprise is custom). The open-source packages have no usage limits.
Open source
The free tier is the open-source developer wedge
Developers should be able to prove value before procurement. The MIT packages let them initialize projects, normalize strings, validate content, generate SDK access, and run local agent workflows.
- CLI, MCP, SDK, rules, skills, and types packages
- Local-first workflows for individual developers
- A direct path from hardcoded strings to governed content
Open source
MIT MCP, CLI, SDK, rules, and skills. No account required.
Studio
Studio pricing starts when collaboration starts
The commercial value appears when content work involves more than one person: workspaces, members, roles, review branches, chat operations, media, forms, webhooks, and delivery surfaces.
- Workspace and project operations
- Content editor and reviewer workflows
- Branch health, diff review, and merge controls
Pro
Team collaboration, higher limits, BYOA, and the Conversation API.
Usage
Usage-based value comes from AI and delivery
Studio has code surfaces for workspace AI keys, managed agent usage, billing, overages, CDN delivery, media processing, and APIs. Pricing can align to the operational load that teams actually create.
- BYOA and managed agent usage paths
- Usage and overage settings
- CDN, media, forms, and conversation API surfaces
Bring your own AI key
Use a Studio-hosted key or connect your own Anthropic account — your usage, your control.
Enterprise
Enterprise licensing is for controlled infrastructure
Some teams need self-managed deployment, private infrastructure, licensed enterprise features, and stricter operational controls. That belongs to enterprise conversations rather than the open-source entry path.
- Self-managed Studio deployment
- Enterprise bridge and license checks
- Support for infrastructure-sensitive teams
Enterprise
Dedicated support, SSO, white-label, and custom infrastructure.
Buying path
The pricing page should teach the funnel
The right message is not only plan comparison. It should explain why a developer starts free, why a team upgrades to Studio, and why an enterprise buys a license instead of rebuilding governance internally.
- Developer proof through npx contentrain init
- Team upgrade through Studio review and delivery
- Enterprise upgrade through self-managed governance
$ npx contentrain init
✓ Detected stack: nuxt
✓ Created .contentrain/
✓ MCP server configured for your IDE
→ Git is now your content source of truth
# next: contentrain scan ./src
Common questions
Can we start without paying?
Yes. The MIT packages are the starting point for local development, validation, normalize, generated SDK access, and agent workflows.
What should Studio plans charge for?
Studio should charge for collaboration, roles, review, managed agent usage, delivery, media, forms, webhooks, usage controls, and enterprise deployment needs.
Why keep pricing tied to the open-source path?
Because open-source usage is the adoption channel. Pricing should capture the moment where a solo workflow becomes team governance or production delivery.
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.