Packaging, not upsell fog
The open system is how teams start. Studio is how some teams operate.
Pricing should reflect the product split honestly. The OSS layer is the open foundation. Studio is the paid operating surface when the team wants a packaged workflow on top.
Current GTM
Earn trust in the open, then earn the right to sell the operating product.
This page should make the ladder clear: prove the OSS foundation first, then package the workflow that removes operational drag for teams that need more.
Free and open
OSS/Core
Use the open system when you want explicit contracts, safe regeneration, and standard outputs the team owns.
- Contracts, generation, runtime adapters, harnesses, and agent tooling
- Incremental adoption inside existing codebases
- Local and CI-friendly workflows
- No forced hosted runtime or locked delivery path
Operating product
Studio
Use Studio when you want the product layer for evidence, drafting, review, exports, and follow-up.
- Packaged operating loop on top of the same open system
- Opinionated team workflows and governance surfaces
- Faster coordination for teams running real product or ops loops
- Design partner and rollout paths for teams with live complexity
Design partner path
For teams already carrying real AI-native complexity.
The design partner path exists for teams that need the operating layer now and are willing to shape it with us. That is not “enterprise later” positioning. It is a practical way to learn from the hardest live workflows first.
Apply as a design partnerSee the operating layer built on top of the open system.
Studio packages the workflow for evidence, drafting, review, export, and follow-up. It should feel like the best product built on top of ContractSpec, not a different story.
FAQ
Questions teams usually ask before they pick a side.
The OSS foundation stays free. Teams can adopt contracts, generation, runtime adapters, and the core package ecosystem without crossing into a paid product loop.