The core
Proofence Engine
The verification, risk, policy and signed-evidence backend behind Proofence products. It informs decisions; it never authorizes an action itself.
Input
Output · claim · document · action
Context
Models · sources · policies · signals
Proofence Engine
Verify · score · orchestrate
Trust result
Score · evidence · explanation
Its role in the platform
Verification is one of five independent responsibilities.
Responsibilities
What the engine does, and what it does not.
The Proofence Engine verifies, scores and signs. It does not authorize actions: that boundary keeps it testable and keeps responsibility with the systems that act. Its internal methods are proprietary; what it delivers is transparent.
Verification & evaluation
Test outputs, claims, and actions against independent models and grounded sources.
Trust scoring
Produce calibrated, explainable trust signals—never a bare, unexplained number.
Risk & policy evaluation
Score risk and evaluate a request against versioned, domain-specific policy, recording which rules applied.
Signed evidence
Emit signed, structured records of inputs, evidence and rationale that can be checked later.
Advisory, never authorizing
Return findings, not permission. Enforcement before execution belongs to Proofence Gate.
Built for accountable AI
Proofence Engine sits between AI systems and the decisions they influence. Rather than treating a model output as a final answer, the engine treats it as a claim to be examined: it assembles evidence, scores risk, evaluates the claim against policy and returns a result that a person can read, contest and check later. Every stage is designed to be inspectable, so a result is never a black box that teams are asked to simply trust.
The engine coordinates several complementary checks instead of relying on a single signal. It grounds claims against source evidence, compares perspectives across models and calibrates a trust score intended to reflect genuine uncertainty rather than false confidence. When signals disagree or confidence is thin, the engine says so in its result instead of forcing a verdict.
Policy evaluation lets organizations express their own standards for acceptable AI behavior and see how a request measures up against them. The engine records which rules applied and why, and preserves that reasoning as signed evidence. What happens next is decided outside the engine: by the calling system, by a person, or, for agent actions, by an enforcement point such as Proofence Gate.
That boundary is deliberate. An engine that only informs decisions can be reasoned about, tested and audited on its own terms, and the systems that act on its findings stay responsible for acting. Each product built around it keeps its own job. AtlasProof by Proofence is the governance and commercial control plane. AirTrustOS by Proofence assesses AI readiness. Proofence Gate enforces before execution.
A note on confidentiality
The Proofence Engine relies on proprietary methods for scoring, orchestration, and evidence handling. This page describes what the engine does and the guarantees it targets—not its confidential internals. Products built around it, such as AtlasProof by Proofence, use its findings without revealing the underlying implementation.
Bring verifiable trust to every AI decision.
Set up governance in AtlasProof by Proofence, or talk to us about verification, readiness assessment, or a Proofence Gate pilot.