CLRK is the Cognitive Loop Runtime for Kubernetes. Run any agent — CrewAI, LangGraph, ADK, OpenAI Agents — in a gVisor sandbox with every byte of egress routed through Envoy. Credentials, cost, and policy live in the infrastructure, not in your agent code.
CLRK is open source today — run it in your own Kubernetes cluster. The fully hosted runtime is on the way. Leave your email and we’ll tell you when it’s live.
Agents run with normal networking inside a
gVisor sandbox. CLRK's userspace
netstack transparently pulls every
connect() through an Envoy fleet
— so credential injection, cost metering,
and policy enforcement are governed at the wire,
not in the agent.
Store the secret on the cluster and bind it to a route. The agent makes its call with no auth header at all — the proxy inserts the real credential as the request leaves the sandbox. Rotate keys, scope them per user, and revoke without ever touching agent code.
# The agent never sees ANTHROPIC_API_KEY. # Envoy attaches it on the way out. apiVersion: clrk.apoxy.dev/v1alpha1 kind: CredentialInjectionPolicy metadata: name: anthropic spec: secretRef: name: anthropic-credentials inject: header: x-api-key routeRef: kind: AIProviderRoute name: anthropic
A declarative, Gateway-API-inspired model. Compose egress rules, budgets, and routes to describe exactly what an agent can reach — enforced by the proxy, transparent to the agent.
EgressGateway
with defaultPolicy: deny-all.
MCPRoute.
Full request/response visibility for every LLM inference and external call — because it all flows through the proxy. Metered, traced, and exportable anywhere.
Per-agent, per-execution, and per-user LLM spend — attributed automatically from the proxy, not reverse-engineered from a provider bill.
Follow a single inbound request through the sandbox and out to every LLM and tool call. Ship to Datadog, Grafana Cloud, Axiom, or any OTLP endpoint.
Point your assistant at Apoxy's MCP server and ask what an agent called, how many tokens it burned, or which upstreams it hit — no dashboards to wire up by hand.
Sandbox, credentials, cost, and policy — handled at the infrastructure layer. No SDK, no rewrites, no agent code changes.