Business¶
The business section covers how Joch is positioned in the market, why the position is defensible, who buys it, how it is sold, and how the open-core split protects both adoption and revenue.
-
Product
What we sell, what we give away, what is open source, and what is commercial.
-
Moat
Why the control-plane category is durable and what makes Joch hard to replace.
-
Competitive Landscape
Where Joch sits relative to vendor SDKs, observability tools, MCP gateways, and platform engineering products.
-
Revenue Models
Pricing, packaging, free tiers, and the open-core boundary.
-
Target Audience
The buyers, decision-makers, champions, and end users that adopt Joch.
-
Go-To-Market
The wedge, the motion, partnerships, and the sequence of releases.
-
Open-Core Strategy
What is Apache-2.0, what is commercial, and how the boundary stays honest.
-
Roadmap
The published, sequenced delivery plan.
In one paragraph¶
Vendor SDKs let teams build agents. Joch is the control plane that lets organizations operate them — across SDKs, vendors, runtimes, and teams. The open-source core is generous and complete enough to run real fleets; the commercial product (joch cloud) adds multi-tenant SaaS, hosted control plane, premium connectors, and SLAs. The moat is the cross-SDK metadata graph plus AOS-conformant policy and audit history, which compound the longer Joch is in place.