Skip to content

For security

You're responsible for what leaves the network. With Vidai every AI call goes through a gateway you run, provider keys never sit in apps, every call is recorded, and one switch stops all AI traffic on every gateway node.

Your problem today

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

Life with Vidai

  • Self-hosted. The gateway, the Control room and their database run in your infrastructure, with your providers (your own Ollama or vLLM too) and your keys. The licence is checked offline; nothing phones home.
  • Keys held centrally. Provider keys live on the gateway. Apps hold Vidai keys that carry their owner, environment, models, rate limit and expiry, and can be suspended, rotated with a grace period or revoked in seconds.
  • Every call recorded the same way, with 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. Guardrails find personal data, secrets and prompt injection in what's sent; VidaiGuard's models run beside your gateway, so your data isn't sent elsewhere to be checked.
  • Providers swappable. Apps call model names your organisation chooses, so moving to another provider is a change in the Control room, not in code.
  • One switch. Stop AI traffic stops every AI call on every gateway node, with a reason, and shows each node took it.
  • Events in your SIEM. Audit events, refused and blocked calls sent as they happen, signed.

Settings › Gateway: Stop AI traffic, with each gateway node's state

What you'll use

Keys › Everything I look after: every key, who holds it, its environment and its state

Request logs: a call whose personal data was pseudonymised before it reached the model, and the policy that did it

VidaiGuard, signed events to your SIEM and single sign-on are part of the Enterprise edition; what Enterprise includes depends on the features your licence includes. Community has pattern checks, the tamper-evident audit log and multi-factor sign-in.

The team Vidai stands in for

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

Your reading path

  1. Your data, someone else's infrastructure and Sending your data to someone else to check your data.
  2. The parts and Keys.
  3. Guardrails and Regions and data residency.
  4. Safety switches and Audit log.
  5. Integrations: email, BI and events.