Kyvvu

AI compliance

Compliance that happens at runtime, with the evidence built in.

The AI Act, GDPR and DORA ask what your AI systems actually do. Kyvvu turns obligations into rules that are checked on every agent step, and records each check as evidence.

customer-agent · task 4e18kyvvu 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

Obligations are about behaviour. Evidence is usually about paperwork.

  1. 01

    Proving oversight, run by run

    Human oversight and record-keeping for high-risk systems are runtime obligations. A procedure document shows intent, not that it happened on Tuesday's runs.

    AI Act Art. 12/Art. 14

  2. 02

    Several regimes, one agent

    The same agent can fall under the AI Act, the GDPR and, in finance, DORA. Each brings its own controls, and they all have to hold at once.

    AI Act/GDPR/DORA

  3. 03

    Evidence assembled after the fact

    When an auditor asks, teams reconstruct what happened from scattered logs. It's slow, and it's only as good as what someone thought to log.

    audit readiness

In practice

Obligations, enforced on real steps.

Each example maps one obligation to one policy, and shows it deciding.

A high-risk decision waits for a person

A credit agent, classified as high risk, prepares a decision and tries to write it to the core system. Human oversight means a person approves first.

credit-agent · task 8b05kyvvu engine · in-process

Illustrative scenarios. Each one is decided by a single policy from the open policy library, as the engine evaluates it. References to laws and regulations are our reading of them, to show how a policy maps to an obligation. Not legal advice.

How Kyvvu helps

From obligation to rule to record.

  1. 01

    Standard packs to start from

    OWASP agentic, the EU AI Act, GDPR, DORA and MiFID II, healthcare and data exfiltration packs from the open library, next to your own rules.

    open policy library

  2. 02

    Obligations become rules

    Each compliance pack maps articles to policies, in YAML your compliance and engineering teams can read together.

    AI Act/GDPR/DORA/MiFID II

  3. 03

    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

  4. 04

    The same answer every time

    Verdicts are deterministic: the same path gets the same verdict, so a decision can be replayed and explained.

    deterministic verdicts

Compliance

Each obligation points at lines in the record.

Select an obligation to see which part of one recorded task proves it.

Questions

Common questions.

01

Does Kyvvu make us compliant?

No tool does on its own. Kyvvu enforces the runtime controls and records the evidence; your classification, documentation and governance are still yours. The packs are our reading of the law, not legal advice.

02

Which regulations do the packs cover?

The EU AI Act (high risk, and minimal and limited risk), the GDPR, DORA and MiFID II for financial services, and NEN 7510 and HIPAA for healthcare. See the policy library.

03

Can we add our own internal rules?

Yes. Your own manifests sit next to the standard packs and are enforced the same way.

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.

Read up

How runtime enforcement maps to the AI Act

Which articles a runtime layer can evidence, and which it can't.

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