AI agent governance

Your AI agents are acting.No one can prove what they did.

Flow Forge records what your AI agents do and seals each record so any later change is visible. It runs inside your environment, under your keys.

The mechanism

See it. Prove it. Connect it.

Three things have to be true before a record is worth anything to an auditor. This is all three.

01 · See it

Every agent, with an owner.

Agents are discovered and registered with a named human sponsor. One that is running but was never approved shows up as a standing finding.

02 · Prove it

A record nobody can rewrite.

Every action is hash-chained to the one before it, and each day's root is signed by your own key. A later edit fails verification against copies you already hold.

03 · Connect it

Read-only, in no request path.

Activity is pulled, never intercepted. Nothing sits between your agents and the systems they use, so connecting it cannot break what you already run.

And the limit

It watches. It can raise a hand. It cannot pull the plug.

A rule can notify the people who own the problem and mark an agent suspended in ProofForge’s own record while a human decides. It does not reach into your platform. The decision, and whoever took it, is what gets written down.

Two lines

One decides. One proves.

Product

ProofForge

A flight recorder for your AI agents. Self-hosted, read-only by design, and built so the record can be checked by people who do not have to take your word for it.

Advisory

AI Advisory

Most organisations are not held back by ambition, but by not knowing how to adopt AI safely. We assess where you actually are and build the adoption strategy that follows from it.

Who it’s for

Whoever gets asked first.

Any organisation that lets AI agents act on its behalf: government and regulators, financial services, telcos, healthcare, enterprise IT and managed security providers.

The security lead
who has to answer what the agents did, including the ones nobody declared.
The regulator or auditor
who needs evidence that stands on its own, not assurances.
The CTO shipping agents
who needs governance that does not slow the rollout down.

Evidence of capture, not proof of absence. The packs say so on their face, and nothing here claims to see what it was never connected to.

Latest sealed rootSample

Your visit, sealed.

Each section you reached was written as a record and hash-chained to the one before it, in this browser, and sent nowhere. It is the same construction the product puts around what your AI agents do.

With JavaScript off there is no ledger to show you, so in words: a record that commits to the record before it cannot be changed on its own. Alter one and every record after it stops agreeing with it.

Your AI agents are doing this all day, in a log anyone can edit.