For compliance and risk
Rules applied to every AI call, with the evidence.
You answer for what data reaches which model, where it is processed, how long records are kept, and the proof. Vidai applies your rules in the path of every call, shows each regulation control by control, and produces the evidence when the auditor asks.
Your problem today
Policies on paper.
Life with Vidai
Policies that act on traffic
Named policies built from guardrails, region rules and routing, read as sentences and reaching every key below where they apply. Observe first, see what enforcing would have done, then enforce.
Data kept out of models
Personal data, card numbers, secrets and prompt injection found, then masked, swapped for stand-ins and restored in the answer, redirected or blocked.
Calls kept where they must stay
Region rules and approved destinations decide where each call may be processed.
Regulations, mapped
Choose GDPR, the EU AI Act, ISO/IEC 42001, HIPAA, PCI DSS and others. Vidai sets the retention each needs and shows every control as enforced, observed, partly in place or a gap.
Exceptions on record
Every exception carries a reason, an owner and an end date, and shows on the dashboard until it ends.
Evidence on demand
An auditor report and an evidence pack for any period, sealed and signed. Never "compliant": your auditor decides.
What you'll use
Your answers, in the Control room.
Policies · Regulations
Each regulation, gaps first.
How the regulations you follow are covered by what's in force now, control by control, with your own processes listed beside them.
Policies
Observe, then enforce.
A policy starts by recording what it would have done. When the findings look right, one change makes it act.
Guardrails · Findings
What the checks found, ready to review.
Every finding by category, with the call behind it, to confirm or mark as a false positive.
Proof · Evidence
Tamper evidence, verified.
The records' seals checked daily and on demand, and the downloads an auditor asks for, prepared in minutes.
The work Vidai takes on
Audit tooling, and the evidence-gathering project before every audit.
Coverage per control and the evidence downloads come with Enterprise. On Community, an organisation admin follows regulations, sets retention and runs pattern-based guardrails, and the audit log is tamper-evident.
How we start together
Start with one team, on your own AI traffic.
- 01
Pick one app or team
Point it at the Control room. One configuration change; nothing else changes.
- 02
Watch for two weeks
Every call priced, checked and recorded. Rules start in observe mode.
- 03
See the evidence
What it cost, what it caught and what it would have stopped, from your own traffic.