Why Vidai¶
Every organisation using AI has to answer for two things: what it costs, and whether it complies: with the regulations it follows and with its own rules on what data may go where. Vidai governs both in the path of every AI call: it decides each call before it reaches a model, applies your rules, and records the proof.
These pages tell that story the way you live it: the problem first, then what usually happens, then what changes.
The problems we take on¶
Each page names a problem teams running AI live with, shows it handled, and gives the proof.
| The problem | What changes |
|---|---|
| Adopting governance means rewriting your apps | A base URL and a key; nothing else in your code changes |
| Every provider wants you on its SDK | Keep your SDK, call any provider; translated both ways |
| A rule written once isn't a rule applied everywhere | One rule reaches every app below it; lower levels only tighten |
| You can't see what your AI does without instrumenting it | Every call recorded the same way, with no tracing code |
| Governance lives in documents, not in traffic | Data masked, pseudonymised or blocked as calls pass |
| Proving it to an auditor | A signed report an auditor checks alone |
| Sending your data to someone else to check your data | VidaiGuard runs beside your gateway |
| Nobody knows what AI costs until the invoice | Every call priced within minutes; budgets that act |
| Model names change under your apps | Apps call a name you choose; no code changes |
| Providers fail and rate-limit you at the worst moment | Keys shared out, failing models rested, fallback chains |
| Control that costs you speed | Well under a millisecond, every call recorded |
| Your data, someone else's infrastructure | Your infrastructure, your providers, your keys |
The bigger picture¶
- The stack nobody chose: what grows around a "simple" homemade AI gateway once it meets an organisation, piece by piece.
- A day with Vidai: five short stories, each a real flow through the product.
What Vidai brings you¶
Find yourself, see what changes for you, and leave with your own reading path.
| You are | Read |
|---|---|
| Evaluating Vidai, or buying for your organisation | For evaluators and buyers |
| A developer connecting programs | For developers |
| An organisation admin | For organisation admins |
| A group admin running a department or client team | For group admins |
| Someone who uses AI at work | For users |
| In Finance or FinOps | For Finance and FinOps |
| A compliance officer, DPO or risk lead | For compliance officers |
| An auditor | For auditors |
| In security (CISO) | For security (CISO) |
| Someone who needs to see but not change | For viewers |
| Running Vidai's servers | For operators |
Then, for how the pieces fit: How Vidai works.