Live · Pre-Action Verification Platform

Verify before
systems act.

Pre-action verification for AI agents, GRC chains and critical decisions. EVE verifies the chain behind an action and returns what the evidence supports.

EVE proves the chain. The organisation acts on it.

▶ Try Pre-Action APISee Governance Demo →
System wants to act→EVE verifies the chain→Verified outcome→Customer policy→Execute
Explore
Powered by the same verification engine

Verify before any system acts

The same verification engine across AI agents, governance workflows, software delivery and cryptographically verifiable evidence.

Pre-Action Verification API

AI Agent Pre-Action

Before an AI agent acts, verify the governance chain behind the action. One API call returns a verified chain outcome and a customer-policy outcome. Your workflow decides and enforces.

One API callVerified chain outcomeCustomer policy outcomeFail-closed by design
Learn more
Governance Chain Verification

EVE Verified GRC

Evidence-chain verification for governance workflows. Verify whether a chain was authorised, owned and monitored — for DORA, ISO 42001, TPRM and third-party risk. Surfaces gaps; humans decide.

EU AI ActDORA / ICT third-partyISO 42001TPRM / vendor access
Learn more
Developer Preview
Code-Change Verification

CodeGate

Before AI-generated code reaches the codebase, verify it in a sandbox and apply only on explicit human approval. Proposals go to a lab; nothing touches production without confirmation.

Sandbox validationHuman-approved applyAtomic writeFail-closed
Developer preview · internal
Cryptographic Seal Verification

Document Verify

Verify cryptographically sealed EVE documents. Confirm integrity and trace any document back to its original data source. Any modification produces a different hash.

SHA-256 sealSource traceabilityTamper detectionOffline-verifiable
Learn more

Supports governance requirements such as human oversight, record-keeping and traceability under the EU AI Act (Art. 12–14), DORA, ISO 42001 and TPRM. EVE provides verifiable evidence and surfaces gaps — it does not certify compliance, and the organisation acts on the result.

Built for two audiences

Choose your starting point

For developers

Build AI agents

Add one verification call before your agent acts. EVE returns a verified chain outcome and a customer-policy outcome; your workflow decides and enforces.

REST APILive democurl exampleFail-closed by design
Try Pre-Action API →
For enterprise

Govern critical workflows

Verify evidence chains, approvals and authority before critical decisions. EVE surfaces what the chain supports across the systems you already run.

DORAISO 42001TPRMAI governance
Explore Governance →
How EVE works

One verification chain. Every critical action.

EVE verifies each link in the chain behind an action and returns what the evidence supports. The system decides what happens next \u2014 EVE does not execute.

The chain
01
Identity
Who or what is requesting the action.
02
Authority
Whether it is authorised to act here.
03
Approval
Whether the required approval was given.
04
Policy
What the customer-defined rules say.
05
Evidence
Whether the chain is supported, partial or missing.
06
Decision
A verified chain outcome is returned.
▶
Execute
The customer workflow acts on the result. EVE does not execute.
The engine
Witness Mode
EVE observes and verifies. It does not act on the system’s behalf. Every verdict is a record, not an instruction.
Deterministic Core
Given the same inputs, approved premises and rule versions, the engine produces the same result — every time.
Evidence Chain
Each action is modelled as a chain of evidence: identity, authority, approval, scope and monitoring.
Cryptographic Sealing
Outcomes are hash-sealed and reproducible. Any change to the underlying evidence produces a different hash.
Witness
Mode
SHA-256
Sealing
Deterministic
Core
Append-only
Ledger
Why determinism

Principles

Formal Expansion
Fixed rules derive new conclusions as premises are approved. The core is stable. Knowledge expands only when new premises pass approval.
Witness, Never Decide
EVE observes, verifies and reports. It does not make autonomous decisions, classify incidents, assess materiality or determine compliance. Humans decide. EVE surfaces what the evidence, rules and signals support.
Deterministic Core
Same input, same approved premises and same rules produce the same output. No randomness in critical paths. No hidden decision-making. No unsupported conclusions.
Cryptographic Truth
Every sealed output is verifiable. Every approved claim links to its source. Every record can be checked without trusting the system that produced it.
Governance Signals
Human approval is necessary, but not always sufficient. EVE surfaces authority, accountability and approval-scope gaps as deterministic governance signals. EVE does not decide what the signal means. A named human owner decides.
"
Like a formal system: the inference rules are fixed, and conclusions are derived from approved premises.
The core is stable — knowledge expands as new premises pass approval.
— The Determinism Manifesto

The Symbol

The e in EVE stands for Evidence & Verification Engine. It also references Euler’s number (e), reflecting the platform’s foundation in reproducible reasoning, formal systems and deterministic verification. The symbol represents a simple idea: critical decisions should be supported by verifiable evidence rather than assumptions.

The Engineering

EVE is built around deterministic verification. Given the same inputs, approved evidence, policy and rule versions, EVE produces the same verification outcome. If required evidence is missing, EVE returns NO_ANSWER. If authority, accountability or approval scope cannot be verified, EVE surfaces the governance signal rather than guessing. EVE verifies the chain. Organisations decide how to act.