# Support and Enterprise ota’s open core stays Apache 2.0 and remains the public source of truth for the CLI contract, repo/workspace schemas, JSON output, and docs. Enterprise direction should extend that core, not replace it or hide it behind a separate product truth. ## Open core first - the public CLI and contract stay usable without paid infrastructure - repo and workspace schemas remain part of the open core - JSON output and docs remain public integration surfaces - governance stays explicit and maintainer-led rather than pretending the enterprise layer owns the product truth ## Good enterprise candidates - hosted control plane for policy, audit, and fleet-level coordination - private adapters or backends - organization policy packs and approvals - support, onboarding, and migration services - compliance retention and reporting ## Enterprise teaser The likely serious enterprise path is not “more commands hidden behind a paywall.” It is: - hosted policy distribution and approval workflows - fleet-level readiness visibility across repos and workspaces - audit history, retention, and operator reporting - private integrations for internal infrastructure - commercial support and rollout help ## Keep separate from the core - the CLI contract - repo/workspace schemas - JSON output shape - public docs and examples ## Operating rule If a feature needs to be paid, keep its contract boundary explicit and do not mix it into the public open-core schema unless that is strategically unavoidable.