Put your agents into production, and keep them under control as the fleet grows
Before an agent acts, it checks the rules for its application. Exceptions reach whoever holds the authority to decide. Every decision maps to the frameworks you answer to, and six roles work from the same records in portals built for their part, so adding an agent doesn't mean adding a process.
Your agents. Your applications. One decision history.
Six portals, built-in handoffs
Everyone who has a say in the agent gets a portal of their own
An agent stays in production only while six kinds of people keep doing their part. Each of them works in a portal built for that part and reads the same records in their own terms, so nobody rebuilds the story for anyone else.
Business OwnerBusiness value and risk
See whether the workflows you own are delivering value, and where operating risk is building.
Governance EngineerRules and policy
Turn business requirements into policy your team can test before it reaches production.
Compliance OfficerRequirements and review
Connect a requirement to the evidence behind a real decision, and see where coverage is missing.
DeveloperApplication connection
Bring the policy check, the human response, and the reported outcome into your application.
AdministratorAccess and operations
Keep access aligned with each person’s work as teams and applications change.
AuditorIndependent review
Follow the evidence without changing the work under review.
The work moves between them, and the answer comes back
An agent action needs a person
→ Reviewer with authority
A rule needs data the agent does not send
→ Developer
A governance engineer changes a rule for a production agent
Explore all five policy outcomesSee how the response changes with the facts.+
For example / Transform
The refund is reduced to the allowed amount.
A support agent requests $200, but the policy caps refunds at $150. VeriProof returns Transform with $150 as the corrected amount. The application issues the smaller refund.
Requested
$200 refund
Result
$150 issued (policy cap)
If several rules match, VeriProof keeps every result and applies the strictest outcome, in this order: Deny, Escalate, Transform, Warn, Allow.
Explore a complex agent workflowFollow parallel checks, human review, and the application response.+
Product walkthrough · Static example data
See a complex workflow become one decision history
A trade needs closer review. Follow the checks and human decision through to the action the trading application takes.
Trade compliance review
23 flow elements8 parallel checks1 bounded recheck1 human decision
Workflow mapHow each step in this workflow connects to the next.
Parallel pathsApplication-defined flow
Select a step for details. Drag the open canvas to move through the flow.
1 of 18
Current stageThe application submits the trade
100%
1The application submits the trade
2The orchestrator starts market checks
3Three market checks run in parallel
4The market findings come together
5The orchestrator starts regulatory checks
6Three regulatory checks run in parallel
7The regulatory findings come together
8Reconciliation finds one evidence mismatch
9The workflow starts one bounded recheck
10Two specialists refresh the disputed evidence
11The refreshed evidence comes together
12The compliance agent confirms the evidence
13Policy escalates to a reviewer
14A compliance officer sets an approved limit
15VeriProof delivers the signed response
16The application rechecks current conditions
17The application continues the saved branch once
18The connected decision history is retained
Platform capabilities
Connect the work behind each agent decision
Governance starts with a business requirement and continues as applications, rules, and risks change. VeriProof gives each team the context to do its part.
01 / Business context
Start with the business requirement
A payment limit means little without the amount, currency, and authority behind it. Bring those facts into the same record as the application’s purpose and accountable owner.
A shared business vocabulary
Use published industry terms and permitted values across application data, rules, and readable evidence.
Visible policy inputs
Inspect the fields an application declares and reports, the rules that use them, and missing or incompatible inputs after a change.
Turn a business requirement into a rule your applications can use. Test it against representative facts, watch it in Shadow when you want to, and enforce it under the approvals your organization sets.
Control before an action
Return continue, warn, replace, request review, or stop at the point where the application can act on the result.
A history of approved changes
Retain the version, test results, and approval history. Reuse central rules across connected applications.
Rules stay central. Your application applies the result.
03 / Human decisions
Give people a useful decision to make
Some work needs a person’s judgment. Let the reviewer set a limit, correct a value, choose a route, or request a revision, with the relevant facts in view.
Responses that fit the work
Configure fields, choices, limits, and instructions. Preview and version the response profile without building a separate form for each agent.
Authority tied to the action
The signed response belongs to the request and policy that were reviewed. Your application checks it before continuing and reports the outcome.
An exception creates work. The shared Inbox brings requests, approvals, and remediation back to the application and evidence that prompted them.
Assignments with context
Set an owner, priority, and due date. Developers can claim requests and submit the evidence the governance team needs.
Ongoing oversight
Review deadlines, reminders, and escalations alongside policy exceptions. Follow application health, business outcomes, and risk decisions into their supporting records.
Example review: a supplier payment and its connected decision history.
05 / Compliance and audit
Make the review part of everyday governance
Choose the frameworks relevant to each application and connect their requirements to controls and supporting records. Gaps remain visible, with owners and follow-up work alongside them.
Requirements connected to evidence
Review framework mappings, run assessments, and track remediation or an authorized business risk decision.
A defined audit scope
Set the applications and dates for an engagement. Auditors can find sessions, review attestations, and record findings within their assigned scope.
Build a focused evidence pack that links the policy version, human response, and outcome reported by the application. Its signed inventory lets an independent reviewer check the exported files.
Proof that can be checked
Verify package signatures, file integrity, and record fingerprints with the Verify CLI. Follow the record’s Azure SQL Database Ledger or Solana proof reference.
Evidence with access and privacy controls
Keep auditor access separate from operational authority. Manage retention, erasure requests, and holds with a recorded history.
Review a case in the portal, investigate it through an assistant, or collect records from the command line. Each route uses the same application context and access permissions.
Most people never need anything else. The Business Owner sees outcomes and the risk decisions waiting for them; a reviewer sees the exceptions assigned to them, with the facts attached.
Through MCP, an authorized assistant can read sessions, rules, compliance records, and assigned work. Reviewers can inspect the case behind a decision without assembling a separate context store.
Use the customer CLI to configure applications, check required policy fields in delivery pipelines, and export permitted sessions. Named connection profiles keep environments distinct.
Send governance records to Splunk for investigation. Share OpenTelemetry traces with Langfuse so engineering and governance teams can follow the same activity. Send reviews to Slack or Microsoft Teams, where reviewers can decide routine ones without leaving the conversation.
Private Enterprise, coming soon to Azure Marketplace
Keep VeriProof in your Azure environment
Private Enterprise will run entirely in your own Azure subscription, completely separate from VeriProof SaaS: the platform, your data, and its integrity ledger (Azure SQL Database Ledger). Your team will own and operate it, using your identity, network, and model deployments.
The Edge Gateway journals session evidence and attachments locally, then batches and retries delivery to VeriProof. Local acceptance and confirmed delivery remain visible as separate states.
Start with the agent that matters most
Evaluate the full system with Developer, free for 60 days. Choose a production plan when your team needs production use, higher volumes, or longer retention.