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.
How adoption scales
Prove the contract layer in your codebase first.
Adopt the open-source packages without an account, hosted runtime lock-in, or per-operation fees. Move into Studio only when your team wants managed evidence, review loops, and coordinated operations on top.
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 program works directly with teams running multi-surface AI workflows in production today, pairing open contract adoption with early Studio operating capabilities.
Apply as a design partnerSee the operating layer built on top of the open system.
Studio packages the team workflow for evidence, drafting, review, export, and follow-up directly on top of your existing ContractSpec definitions.
FAQ
Questions teams usually ask before they adopt.
The OSS foundation stays free. Teams can adopt contracts, generation, runtime adapters, and the core package ecosystem without crossing into a paid product loop.
Studio is the operating layer: the packaged workflow for evidence, drafts, review, export, and follow-up on top of the same open system.
Specifications and runtime boundaries belong in code your team owns and inspects directly. Paid packaging focuses on Studio workflows that remove operational coordination work for teams.
Teams already running AI-heavy product or ops workflows, especially those who feel drift, unsafe regeneration, or coordination pain across multiple surfaces.