Overview
Omnia is a Kubernetes operator plus a set of services that run AI agents in your own cluster. You describe an agent as custom resources, and the operator deploys and scales it.
What you get
Section titled “What you get”| Capability | How it works |
|---|---|
| Agents as resources | An AgentRuntime references a PromptPack and one or more Provider resources. The operator creates the agent pod: a facade container and a runtime container. |
| LLM providers | A Provider selects the vendor and credentials. claude, openai and gemini are among the supported types. |
| Tools | A ToolRegistry declares tools of type http, openapi, grpc, mcp, client or platform. |
| Autoscaling | An AgentRuntime scales with the Kubernetes HPA (the default) or KEDA. KEDA with minReplicas: 0 scales to zero. |
| Sessions | Session API stores conversations in PostgreSQL. |
| Console | The dashboard is a separate Deployment that lists agents, sessions and costs. |
Core, dev mode and Licensed
Section titled “Core, dev mode and Licensed”Omnia has three states, set by enterprise.enabled and whether a licence is present.
| State | Configuration | Behaviour |
|---|---|---|
| Core | enterprise.enabled: false | Enterprise features are absent. |
| Dev mode | enterprise.enabled: true, no licence | Every feature is on, with a banner on every service. |
| Licensed | enterprise.enabled: true and a licence | Every feature is on, silently. |
No state blocks on a missing or expired licence. See Licensing & Features for what Enterprise adds.
Where to go next
Section titled “Where to go next”- Learn: Getting started deploys your first agent. Production setup hardens an install.
- Do: Scale agents, Set up observability, Configure dashboard auth, Install with a licence and Develop locally.
- Look up: AgentRuntime, Provider, ToolRegistry and Helm values.
- Understand: Architecture, Sessions and Arena Fleet.