Validiti Validiti
In Development Validiti Audit · Cross-product compliance aggregator

One pane of glass. Across every Validiti product.

DMS records what entered the system. Titus records what touched the binary. Accelerate records what was answered. Provenance records what was claimed. Media records what was captured. Audit aggregates all of them into one signed, tamper-evident chain-of-custody view — for compliance, regulators, and incident response.

6+
Source feeds
end-to-end
Chain of custody
read-only
Aggregator
on-prem
Single tenant
↓ What it is

What Validiti Audit is

Three statements, no jargon.

01

A read-only aggregator that subscribes to the signed event streams from every Validiti product you run. It does not generate evidence; it gathers and correlates evidence the products already produce.

02

One question, one answer. "What happened around this customer / case / file / claim?" returns a unified timeline pulling from DMS, Titus, Accelerate, Provenance, Media, and PCI — with signature verification on every step.

03

Built for the conversation that already shows up: SOC 2, HIPAA, FedRAMP, internal audit, regulator request, breach disclosure. The right answer is to hand them a verifiable trail, not a screenshot of a dashboard.

What Audit aggregates

Each Validiti SKU emits its own signed evidence stream. Audit subscribes to whatever you run; missing products simply don't appear in the timeline.

DMS

Document chain — what entered the system

Every document ingested through DMS emits a link-hash chain entry. Audit pulls these as the inbound provenance for every customer / case / matter touchpoint.

Titus

Binary integrity — what touched the engine

Titus emits a signed event for every file modification, integrity scan, and runtime defense action. Audit aggregates these as the operational integrity record.

Accelerate

Inference provenance — what was answered

Accelerate emits a signed record for every answered query: brain version, cache tier hit, evidence used, response sent. Audit pulls this as the AI-output trail.

Provenance

Claim labels — what was sourced

Provenance emits per-claim VERIFIED / PARTIAL / NO_SOURCE labels. Audit aggregates these to show which claims in which output had what evidence behind them.

Media

Visual / acoustic chain — what was captured

Media emits per-asset origin and tamper-verdict events. Audit ties these to the documents and outputs they support, so the chain runs from camera to claim.

PCI

Local memory state — what was loaded

PCI reports loaded brain versions, persona files, and local query state. Audit uses this to reconstruct the runtime context any answer was produced under.

Use cases

Where a unified, verifiable trail across Validiti products earns its keep.

Regulator request

Hand them a sealed timeline

Reproduce the full evidence chain for any inbound document, AI output, or media artifact: source → processing → runtime → response. Each step independently verifiable.

Internal audit

Sample-driven verification, no spreadsheets

Auditor picks any case ID. Audit returns the trail. Findings are about the state of evidence, not the state of your record-keeping.

Incident response

"What did the system do during the window?"

Pull every signed event in a time window. Cross-product. Tamper-evident. The forensic question stops being "do we have the logs" and becomes "what do they show".

SOC 2 / HIPAA / FedRAMP

Continuous evidence, not periodic theater

Mapping from each control to the underlying signed events. Auditors verify the chain instead of trusting written attestations.

Pricing

Audit is sold as a per-tenant aggregator. Every Validiti SKU you run feeds it free; you pay for the aggregator itself.

Single tenant
$499
per month
One Audit instance, one organization, all your Validiti SKUs feeding in. On-premises, single-machine, sealed binary.
Enterprise
Custom
contact us
Custom regulator integrations, on-call audit forensics, control-mapping templates for your framework. contact@validiti.com

Built-in guarantees

Every Audit deployment ships under the same protection envelope. Validiti Titus is in every Validiti SKU as the ultimate defense of source code.

What every install gets, on day one

  • Sealed binary. Audit ships as a stripped, signed native module. The package self-verifies its identity at first import; any mismatch refuses to load.
  • Machine-bound activation. One license, one machine. Moving to a new host requires deactivating the old one.
  • Validiti Titus runtime defense. The Titus watcher monitors the Audit aggregator continuously. Any tamper trips a defensive shutdown in milliseconds — you don't audit the auditor in flight.
  • Read-only by construction. Audit subscribes to signed event streams. It cannot modify, redact, or rewrite the source-product evidence; tampering at the aggregator does not change the underlying chain.
  • Single-tenant data plane. No cross-customer mixing in the data layer. The multi-tenant tier is a control-plane convenience over per-tenant aggregator instances.
  • Same engine on every tier. Single, multi, enterprise — identical engine, identical protection. We don't downgrade defenses to save cost.
  • U.S.-headquartered, U.S. only at launch. Single legal jurisdiction.