Kyvvu

Energy and industry

Agents that help run the business, with a person in the loop.

Energy companies, manufacturers and other large enterprises are putting agents on planning, maintenance, procurement and supply chain work. Kyvvu makes sure those agents ask before they delete records, run code or send data out, whatever sector you are in.

procurement-agent · task 5c21kyvvu engine · in-process
  1. step.messagePOSTsmtp/externalblock
Blocked: outbound send after personal data was read in this taskTry it: click the highlighted step to take it off the path

The problem

Agents get close to operations.

  1. 01

    Systems of record

    Agents read and write the ERP, the maintenance system and supplier data. A wrong delete or update there is expensive to undo.

    ERP/maintenance/suppliers

  2. 02

    Changes need sign-off

    In asset-heavy businesses, changes to records and systems normally pass a person. An agent should follow the same rule.

    approval before change

  3. 03

    Many sites, many agents

    Business units and sites each build their own agents, on their own platforms. Central teams need one set of rules across all of them.

    one policy, every agent

In practice

The rules you already apply, enforced on agents.

A clean-up waits for the planner

A maintenance agent tidies up old work orders. Your rule says deletions need a person's approval. The agent tries without it first.

maintenance-agent · task 3d90kyvvu engine · in-process

Illustrative scenarios. Each one is decided by a single policy from the open policy library, as the engine evaluates it.

How Kyvvu helps

One set of rules across every site.

  1. 01

    Judges the whole path

    Every action is checked against everything the agent did earlier in the task, and blocked before it runs if the sequence is dangerous.

    allow/warn/block

  2. 02

    One policy, every agent

    The same rules for plain Python, LangChain, LangGraph, CrewAI and Claude Code agents, in the cloud, on-prem or air-gapped.

    Python/LangChain/CrewAI/Claude Code

  3. 03

    Hosted or yours

    Use platform.kyvvu.com, or run the platform in your own infrastructure, on-prem or air-gapped, on Enterprise & Public.

    hosted/self-hosted/air-gapped

  4. 04

    Rules people can read

    Policies are short YAML files in your own git, reviewed and versioned like code. Every verdict in the trace names the rule that decided.

    policies as code

  5. 05

    A record of every step

    Each task is recorded as an ordered trace of its steps with the verdict on each, hash-chained when it reaches the platform.

    logs/traces

  6. 06

    Nothing breaks on day one

    Only critical policies block; high, medium and low ones warn. Start a new rule as a warning and make it critical once you trust it.

    shadow/suggest/enforce

Questions

Common questions.

01

Is Kyvvu only for regulated sectors?

No. The policies are about what agents do, not about which regulator you answer to. Banks and insurers use the same engine as any other large enterprise.

02

Can it run where our agents run?

Yes. The engine runs inside the agent's own process, in the cloud, on-prem or air-gapped, and your policies stay in your own git.

03

Do we have to change how our agents are built?

No. Kyvvu works with Python, LangChain, LangGraph, CrewAI and Claude Code agents, and with agents in any language through the local engine.

Get started

Every agent has to ASK before it acts.

Start with one agent

See it on your own agents

A 30-minute demo with someone who builds Kyvvu: your agent, your rules, and the policy that decides each step.

See it on your agents

Bring one agent to a demo

A 30-minute demo with someone who builds Kyvvu: your agent, your rules, and the policy that decides each step.

Want to see other teams and sectors? All use cases.