For security

Every AI call through infrastructure you run.

Provider keys never sit in apps, every call is recorded the same way, content is checked inside your network, and one switch stops all AI traffic. Nothing phones home.

Vidai Control room · Settings
Stopping every AI call with one switch, with the reason recorded.

Your problem today

AI spread across tools nobody controls.

Prompts, provider keys and customer data sit across apps and tools nobody fully controls. Every new AI tool needs its own security review, a leaked key means a scramble across teams, and depending on one provider is a risk nobody planned for.

Life with Vidai

Self-hosted

Vidai and its database run in your infrastructure, with your providers, your own models too, and your keys. The licence is checked offline.

Keys held centrally

Provider keys stay in the Control room. Apps hold Vidai keys with an owner, environment, models, rate limit and expiry, suspended, rotated or revoked in seconds.

Every call recorded

Who made it, which model answered and what each rule did. Reading a call's content needs a role of its own, and every read is recorded.

Content checked in house

Personal data, secrets and prompt injection found before the call leaves. VidaiGuard's models run beside Vidai, so your data isn't sent elsewhere to be checked.

Providers you can swap

Apps call model names your organisation chooses, so moving to another provider is a change in the Control room, not in code.

Events in your SIEM

Audit events, refused and blocked calls sent as they happen, signed, never containing prompts or responses.

What you'll use

Your answers, in the Control room.

Keys

Every key, its owner and its limits.

Who holds each key, what it may call, when it expires and when it was last used. Suspend one without touching anything else.

Vidai Control room · Keys
Every key with its holder, environment, expiry and last use.
Every key with its holder, environment, expiry and last use.

Request logs

Personal data swapped for stand-ins.

The model sees stand-ins; the answer comes back with the originals restored. The call record shows what was found and what was done.

Vidai Control room · Request logs
A call whose personal data was swapped for stand-ins before it left.
A call whose personal data was swapped for stand-ins before it left.

Settings · Integrations

Events to your SIEM, as they happen.

Splunk, Sentinel, Elastic or a signed webhook. Events arrive in order and are retried until accepted.

Vidai Control room · Settings
Event destinations for your SIEM, with their state and a test send.
Event destinations for your SIEM, with their state and a test send.

Settings · Single sign-on

Your identity provider decides who gets in.

Entra ID, Okta or Keycloak, with teams and roles following people's groups, and multi-factor sign-in for everyone else.

Vidai Control room · Settings
Single sign-on set up with an OpenID Connect identity provider.
Single sign-on set up with an OpenID Connect identity provider.

The work Vidai takes on

A sovereignty and security review for every new AI tool, and the key rotation drills that follow each leak.

VidaiGuard, signed events to your SIEM and single sign-on come with Enterprise. Community has pattern-based guardrails, the tamper-evident audit log and multi-factor sign-in.

Related

How we start together

Start with one team, on your own AI traffic.

After a 20-minute demo, we agree a two-week pilot with you: one app or team, your traffic, your infrastructure.
  1. 01

    Pick one app or team

    Point it at the Control room. One configuration change; nothing else changes.

  2. 02

    Watch for two weeks

    Every call priced, checked and recorded. Rules start in observe mode.

  3. 03

    See the evidence

    What it cost, what it caught and what it would have stopped, from your own traffic.