Skip to content

For evaluators and buyers

You're deciding how your organisation will govern AI. Vidai gives you one place to set who may use which models, what data may reach them, where calls may run and what they may cost, applied to every call as it happens and recorded as proof. It runs on your own infrastructure.

Your problem today

Teams use several providers, each through its own SDK and its own keys. Nobody has a single view of what AI the organisation uses, what it costs or what data it sends. Policies exist on paper; whether each app applies them is anyone's guess. When the board, a regulator or a customer asks for proof of control, the answer is a project.

Life with Vidai

  • One place for all AI traffic. Every app, agent and person calls models through the gateway with a Vidai key. Changing the base address is the only change to their code.
  • Rules acted on, not just watched. Model access, Guardrails, region rules, budgets and routing are decided on every call before it reaches a model.
  • Every call recorded the same way: who made it, which model answered, what each rule did and what it cost.
  • Proof on demand. A tamper-evident audit log in every edition; sealed records and an auditor report an auditor checks alone with Enterprise.
  • Yours. The gateway, the Control room and their database run where you choose, with your providers and your keys.

Home's This month at a glance: spend in euros and dollars, saved by routing, share of calls checked, calls refused by policy

What you'll look at

  • Dashboards for admins, FinOps and compliance, each answering its own question.
  • Request logs: open any call and read its story, from the key that made it to the rule that acted.
  • Policies: what you intend, for whom, read as sentences.
  • Evidence: tamper evidence Verified, and the downloads an auditor asks for.

Policies: each policy with its state as an icon and a word, and who it covers, what it does and where, read as sentences

Request logs: a call blocked because it carried a card number, with the guardrail that found it and the policy it belongs to

Two editions

Community is a complete governance platform on its own: people, roles, keys, model access, Guardrails with pattern checks, routing and fallback, regulations and retention, the tamper-evident audit log, cost and budgets, Request logs and dashboards. Enterprise adds single sign-on, VidaiGuard, region rules, sealed evidence on both sides with the auditor report and evidence pack, coverage per control, the Compliance officer role and dashboard, recompute, and data out to your BI and SIEM tools. What Enterprise includes depends on the features your licence includes. Moving between editions loses nothing. See Editions and licences.

Speed

The gateway adds well under a millisecond. In its 0.9.0-beta.5 run it carried 47,200 calls a second at a 0.58 ms median: one machine, 32 concurrent callers, every call recorded, a mock provider; not a published benchmark.

The team Vidai stands in for

A platform team building a gateway, and then running it: translation, failover, pricing, policy, evidence, dashboards and access, each its own project. See The stack nobody chose.

Your reading path

  1. The problems we take on, one page each.
  2. A day with Vidai: five real flows through the product.
  3. How Vidai works and the parts.
  4. Get started: a first call through the gateway, seen in Request logs with its cost.
  5. Editions and licences.