Kyvvu

Banking

Agents that move money need four eyes too.

Banks are putting agents into payments, lending, onboarding and operations, under DORA, MiFID II and the AI Act. Kyvvu enforces your controls on every action those agents take, and records each one.

trading-agent · task 3d19kyvvu engine · in-process
  1. step.resourcePOSTtrading/executeblock
Blocked: automated execution after an external market data readTry it: click the highlighted step to take it off the path

The problem

Every control you have assumes a person did it.

  1. 01

    Four eyes, one agent

    Segregation of duties and four-eyes checks are built around people. An agent that prepares and executes a payment breaks the pattern.

    segregation of duties

  2. 02

    Credit is high risk

    Creditworthiness assessment of natural persons is a high-risk use under the AI Act, with human oversight and record-keeping duties.

    AI Act Annex III

  3. 03

    DORA wants control and evidence

    Agents are ICT systems acting on your behalf. Supervisors will ask how their risks are managed and how incidents are found.

    DORA ICT risk management

In practice

Bank controls, enforced on agent actions.

A payment prepared and sent by the same agent

A payments operations agent prepares a transfer and tries to execute it. Your four-eyes rule says a person approves first.

payments-agent · task 7b14kyvvu 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

What Kyvvu gives a bank.

  1. 01

    A financial services pack

    Human approval for financial writes, approval integrity, market data taint, trading hours and loop limits, mapped to DORA and MiFID II.

    DORA/MiFID II pack

  2. 02

    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

  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

    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

  5. 05

    Into the tools you already run

    Traces ship to the SIEM you already run on Enterprise & Public, so agent activity sits next to the rest of your security data.

    SIEM export

  6. 06

    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

Evidence for supervisors, from the enforcement itself.

Every check is recorded as it's made, so the runtime evidence for the EU AI Act and DORA is a by-product of running Kyvvu. You don't have to assemble it separately.

Questions

Common questions.

01

Can we run it on our own infrastructure?

Yes. The engine always runs inside your agents. On Enterprise & Public, the platform runs in your own infrastructure too, on-prem or air-gapped.

02

Is Kyvvu used in regulated organisations?

Yes. Kyvvu is in production at regulated Dutch enterprises.

03

How do we buy it?

Enterprise & Public is an annual contract, invoiced, with purchase orders and tender documents supported. Start with a demo on one of your agents.

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.

The policy pack

DORA and MiFID II, as policies

Read the financial services pack: each policy, the article it maps to, and the YAML.

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