Start with OSS when you need:
- explicit contracts and generated surfaces you still own
- incremental adoption inside an existing codebase
- runtime governance, integrations, and safe regeneration without a managed operating product
Studio bridge
Start with the open system first: contracts, generated surfaces, runtimes, integrations, and safe regeneration. Move to Studio when a team wants the product-facing workflow, decision loop, and managed operator surface on top of that foundation.
What stays open
contracts, code, generated surfaces
Studio is additive. It does not replace the OSS source of truth or ask teams to abandon their contract layer.
decision workflows that turn product evidence into proposed spec changes
governed execution loops and task packs on top of the OSS contract layer
operator surfaces for teams that need a managed workflow instead of raw building blocks
deeper product-facing workflows that sit above the open system without replacing it
If your team wants a concrete authoring control plane on top of the OSS foundation, start with the Builder control-plane docs and the workbench host guide before you dive into the larger Studio product surface.
The OSS site keeps this section intentionally short. Deep Studio product guidance belongs in the Studio app docs.