Documentation
Docs
Introduction

How Consonant Solves This

We replace the monolithic container with a distributed agent runtime composed of three pillars: Independence, Coordination, and Visibility.

The Three Pillars of Consonant

To solve the production disasters, Consonant fundamentally changes the architecture of multi-agent systems. We provide three core capabilities that work together to create a robust production environment.

1. Independent Agent Runtime (KAgent)

We wrap each agent in a specialized Kubernetes Runtime (KAgent). This gives each agent its own IP address, its own resource quota, and its own scaling policy.

  • Solves Blast Radius (Failures are isolated)
  • Solves Cost Waste (Right-sized resources)
  • Solves Deployment Risk (Independent updates)

2. Automatic Coordination (Control Plane)

Once agents are distributed, they need to talk. Consonant's control plane handles all communication, routing requests based on high-level goals and enforcing policies before any action is taken.

  • Dynamic Request Routing
  • Policy Enforcement (OPA)
  • Automatic Retries & Circuit Breaking

3. Complete Visibility (Observability)

Debugging distributed systems is hard. Consonant instruments everything automatically. Get full distributed traces, inputs/outputs for every step, and cost tracking per agent.

  • Distributed Tracing (OpenTelemetry)
  • Step-by-step Replay
  • Cost Attribution

How it comes together

You define your agents in a manifest, and Consonant handles the rest.

yaml
apiVersion: consonant/v1
kind: Project
metadata:
  name: market-research
spec:
  agents:
    - name: researcher
      image: agents/researcher:v1
      resources: { cpu: "2", memory: "4Gi" }
    - name: writer
      image: agents/writer:v1
      resources: { cpu: "0.5", memory: "1Gi" }
  
  policies:
    - name: budget-limit
      rule: "cost < $10"