// Pricing
The Apache-2.0 core is sufficient for production fleets. Pay for control-plane operations, never for inference.
// Pricing
Pay for control-plane operations, never for inference. The OSS core is sufficient for production fleets.
Full control plane, gateways, AOS exporters, CLI, console — self-hostable end to end.
Hosted control plane to remove the hosting friction. Limits on agents, executions, and retention.
The typical landing tier for engineering organizations.
For regulated industries and large fleets where dedicated hosting matters.
Joch Enterprise ships every Cloud feature in an airgap-friendly distribution with hardened images, FedRAMP packaging, and a dedicated CVE channel.
// How we price
Inference billing stays with the provider. Joch is a multiplier on operations efficiency.
Per-seat undercounts platforms with many automations and few humans. We meter the work.
Basic AgBOM, traces, hooks, gateways, and policies are free forever in the open-source core.
Trace and AgBOM storage is a real cost — we charge for it explicitly, not by feature gate.
// Add-ons
Vetted MCP servers and tools with signing and security review.
per server / month
SOC 2, HIPAA, FedRAMP exports and control mapping.
annual
Bespoke Guardian Agent integration for your tool gateway.
engagement
Joch Registry mirror with private repositories and replication.
annual
// Pricing FAQ
Yes — control plane, gateways, AOS exporters, CLI, console, framework adapters, provider adapters, and the Kubernetes operator are all in the Apache-2.0 distribution. Self-hosted production fleets run on it with no commercial license.
An agent is one record in the Joch inventory — one named, owned, versioned definition. Different versions of the same agent count as one.
Cloud Team includes a generous monthly execution allowance per agent, then meters overage in tiers. The OSS and Cloud Starter tiers do not meter executions at all.
Yes. Joch is portable by design — agent records, policies, and traces export and re-import cleanly. Cloud and Enterprise speak the same control plane.
Never. Provider tokens are billed by the provider. Joch routes the call and records the trace; the bytes flow direct.