Skip to content

Control Your AI

Unpredictable AI agents need deterministic control. Automate guardrails with an AI governance loop to enforce trusted Kyverno policies across every model call and tool execution.

aicontrols · gateway
timeidentitydecisionrequestlatency
40:16.713maya@example.comAllowLLM claude-opus-5-56746ms
40:16.556maya@example.comObservedTOOL Bash0ms
40:15.928release-agentDenyTOOL kubectl delete↳ block-destructive-ops-production3ms
40:13.430sam@example.comAllowLLM gpt-6-astra5262ms
40:12.712sam@example.comAllowMCP github.create_pull_request412ms
40:09.510priya@example.comDenyLLM claude-sonnet-5-5↳ content-safety-credentials2ms
Illustrative data · not a live tenant6 of 10,000+ events · 2 denied · live

Securing workloads at

AI proposes.
Policy enforces.

AI agents analyze traffic across every control point to draft policies and explain risks. Agents recommend. Humans approve. The Kyverno CEL policy engine enforces. Every decision logs to a unified audit report.

One policy engine. Multiple Control Points.

  1. Control point 01

    Pipeline

    Catch violations at the source. Block non-compliant PRs before merge.

    Secure artifacts at build time—validated, signed, and attested before deployment.

    Nirmata Scanners
  2. Control point 02

    Admission

    Control what enters the cluster. Enforce rules at the API server before resources run.

    Reuse the validate, mutate, and generate rules you run today—extended to agents with no second engine.

    Enterprise Kyverno
  3. Control point 03

    Sandbox

    Contain what agents can touch. File and exec policy with granular network restrictions.

    Container sandboxing keeps each agent inside the files, commands, and network destinations its policy allows.

    Container sandboxing
  4. Control point 04

    Gateway

    Secure every model call, MCP connection, and agent interaction across the wire.

    Evaluate every prompt, tool call, and model response in real time—typically single-digit millisecond overhead.

    AIControls Gateway
  5. Control point 05

    Runtime

    Kernel-level detection and behavioral enforcement for active workloads.

    eBPF-powered sensors monitor running workloads to enforce policies and detect shadow AI.

    Nirmata Runtime
  • One audit report
  • One policy set
  • One set of skills

Agentic layer

Judge

Fallback only

Fires only when no policy matches on a call. Returns a bounded verdict — never blocks on its own.

Feeds into:Gateway

Checked against your policies first — Judge only sees calls with no matching rule. One bounded, logged verdict; it can’t override a policy or block by itself.

Analyst

Standing review

Reviews every decision across the fleet. Drafts policy and config changes — a human always promotes them.

Feeds into:PipelineAdmissionSandboxGatewayRuntime

Runs across every decision in the fleet, not just Judge’s fallback cases. Drafts the fix — nothing takes effect until a human promotes it.

↑ hover or tap a card for more detail ↑

Free threat model · For security and platform teamsAI agents went from one worker pod to host-level access across multiple clusters in under 13 hours. No attacker was involved.The threat model for agents already running in your clusters: 9 attack paths, the coverage matrix, and 8 questions to ask of your own cluster.Get the free threat modelFree PDF · Instant download · 32 pages

Start where your problem is.

Govern your clusters, your AI agents, or both — one engine, one syntax, one audit log, no matter where you start.

Governing your clusters

Every cluster. Every deployment.

  • Policy-as-code across every cluster and namespace
  • Standard open-source engine — no proprietary syntax
  • Start in audit mode, then switch to active blocking

Fleet-wide governance from day one — on the engine you already run.

Explore cluster governance

Governing your agents

Every AI call. Every agent action.

  • Identity, authorization, and limits on every call
  • Centralized policy definition enforced at the gateway
  • Complete audit log for every tool an agent touches

Extends your existing Kyverno policies to the AI stack — not a new system to learn.

Explore agent governance

Your Kyverno investment compounds in the AI era.

The skills, policy pipelines, and compliance rules your team built for Kubernetes carry directly over to AI workloads.

Project Status
CNCF Graduated
Monthly Downloads
7M+
Open Source, No Lock-In
Apache 2.0

Customer testimonial

“We found agents in our clusters nobody had told us about. That’s the part that kept me up. Now nothing reaches a model without an identity attached and a policy decision behind it.”
— Platform Lead · Large Retailer

Field performance

We now have identity-based authorization in front of every AI call — enforced with the same Kyverno policies already enforced across our clusters.

Read the solution brief

Unify your governance from clusters to AI.

Talk to us about governing your clusters, your agents, or both — one engine, one audit log, no matter where you start.