Decision context
Bring policy outcomes, session evidence, and integrity results into the same review. Your team can examine the record behind a reported decision.
Evidence integrity
Check whether recorded evidence has changed
When someone asks why your agent did what it did, the record has to hold up. Each finalized decision record carries integrity proof, and your auditor or regulator can check an exported package on their own machine, without taking your word or ours.
Signed evidence packagesIndependent verificationRole-based access
Give reviewers a record they can examine
Export integrity
The verifier compares exported files with a signed inventory. Changed, missing, or extra files prevent the package from passing verification.
Agent handoffs
What happened between agents? Session lineage connects their recorded activity with the governance context available at each step.
Check the record and protect access
Signed evidence packages
Each package includes a signed inventory of exported files. A trusted public key lets reviewers check its signature independently.
Proof tied to the record
Follow the proof reference included with the evidence. A reviewer outside your team checks the exported files and signature with a public key, and each record's fingerprint against Azure SQL Database Ledger or the Solana blockchain. They don't have to trust VeriProof.
Separate access controls
Signing keys and decision records have separate access controls. Role-based permissions define who can review evidence and administer the service.
Sealed records
Sealed evidence has no ordinary edit action. Integrity checks help reviewers detect changes to the recorded content.
Integrity proof for each record
Choose the proof provider for your environment
Keep verification in Azure with the default Azure SQL Database Ledger option. Need a public reference? Choose Solana when your environment is created.
Private verification in Azure
Store each session’s fingerprint in an append-only Azure SQL Database Ledger table. Verification checks the ledger against separately protected database digests to detect changes.
Your auditor gets read-only verification access, separate from the access that records evidence, and checks each fingerprint in Azure. Nothing is published to a public network.
Public verification with Solana
Publish a fingerprint for a group of records to Solana. Anyone with the reference can inspect the public transaction.
VeriProof sends fingerprints only. Decision content, personal data, and protected health information stay in your deployment; verification uses the public Solana network.
One verification option per environment
The proof provider is fixed after the environment is created. Choosing the other provider requires a new environment with its own proof history. Private Enterprise runs entirely in your own Azure subscription, integrity ledger included.
Bring evidence into your review workflow
Gather scoped evidence with MCP
An authorized agent can collect the integrity records and evidence summaries available to its assigned role, applications, and audit engagements.
Verify an export independently
The Verify CLI checks the package signature, file inventory, record fingerprints, and provider references. It does not require a VeriProof account.
Verification your reviewers can run
The verifier checks three things: the package signature, the exported files, and the proofs that tie them to the source records. The signing key comes from a channel the deployment operator does not control.
A pass means the record is what it claims to be. Whether the decision inside it was a good one is still your reviewer's call.
Keep visual evidence connected and verifiable
Key screen evidence
See what the agent saw at a recorded step. Policy-selected, masked screen captures stay connected to that point in Flow View.
Images in the review
Supported images appear in the evidence PDF, so reviewers can examine visual context alongside the decision record.
Attachment integrity
Attachment fingerprints and masking status help reviewers check each capture and its connection to the recorded step.
Keep delayed proofs visible
Temporary provider errors trigger retries. Reconciliation finds sessions still awaiting proof and queues them again, with pending records kept distinct from verified results.
The tamper-evidence whitepaper explains the recovery process.
Match evidence access to the work
Customer access stays within the tenant and the user's permissions. Auditor access follows the assigned engagement scope; administrative records show changes to settings and access.
Data protection
Private Enterprise, coming soon
Private Enterprise, coming soon to Azure Marketplace, will run entirely in your own Azure subscription, with your data and its integrity ledger, completely separate from VeriProof SaaS. Your organization will own and operate the installation.
Sensitive data controls
Apply the tenant and SDK redaction policies your workflow needs. Evidence exports retain the masking status for review.
Encryption
Encryption protects stored records and data in transit. Key material is kept outside the evidence store.
Bring the evidence questions your team needs answered
Tell us which deployment you are considering and what your reviewers need to verify.