Skip to content

Platform

Joch's "platform" section explains where Kubernetes fits underneath Joch and how the deployment story works. The primary architectural treatment lives in Architecture; these pages focus on the operations side: how to install, where Kubernetes ends, and how local / Docker / cluster modes compose.

Sections

  • Kubernetes Role

    Why Kubernetes is the right substrate underneath Joch, and why raw Kubernetes is not sufficient as the agent product surface.

    Read the Kubernetes role

  • CRDs and Controllers

    How Joch resources can be implemented as Kubernetes CRDs with operators, and what controllers reconcile.

    Read the CRD design

  • Deployment Modes

    Local developer mode, Docker Compose, Kubernetes, and managed SaaS — same resource specs, different runtime.

    Compare deployment modes

  • Product Strategy

    Backend-agnostic CLI, the same specs across environments, room for managed SaaS without forking the model.

    Read the strategy

Platform rule

Users describe agent intent. Joch compiles that intent into the right infrastructure objects for the selected backend.

User-facing            Agent, FrameworkAdapter, Tool, MCPServer, Memory, Policy, Eval, ...
Control-plane          Joch controllers and compiler
Infrastructure-facing  Kubernetes Jobs, Deployments, Services, Secrets, ConfigMaps,
                       or Docker containers, or local processes

Operators run:

joch run support-triage --task "Triage the queue"

— not handwritten Kubernetes Jobs with model, prompt, memory, policy, and trace export wired together.