Concepts: the mental model¶
Each page here explains one idea: what problem it solves, what it is, how it fits with the rest, and what you see in the Control room. Read How Vidai works first: it's the one picture everything else hangs on. The words are defined once in the Glossary.
Start here¶
- How Vidai works: the whole picture, in one diagram and a short read.
- The parts: what runs where, where your data lives, how fast a change takes effect.
Who is calling¶
| Concept | What it's for |
|---|---|
| Organisation, teams and sub-teams | Access, cost and rules follow the org chart |
| People and roles | Each person gets exactly the reach their job needs |
| Applications and agents | A cost, a refusal or an incident lands on a system with an owner |
| Environments | Test and production kept apart |
| Keys | One credential per caller; provider keys never sit in apps |
| Service accounts and API tokens | Your own systems manage Vidai with accountable credentials |
Models and where calls go¶
| Concept | What it's for |
|---|---|
| Providers and models | The AI services you already pay for, offered from one list |
| Model names and aliases | Stable names, so a model change is never a code change |
| Provider keys and resilience | Rate limits, outages and key rotations absorbed |
| Translation between API formats | Any SDK to any provider |
| Model access | Who may call which model, decided once |
| Routing and fallback | The right model for cost, region or reliability |
| Regions and data residency | Calls processed only where law or contract allows |
Rules and policies¶
| Concept | What it's for |
|---|---|
| Rules at levels | A rule written once reaches everything below; nothing loosens it from beneath |
| Guardrails | Personal data, secrets and unsafe content stopped before a model sees them |
| Policies and regulations | A regulation turned into rules that act on every call |
| Exceptions, overrides and approvals | Justified exceptions without loosening the rule for everyone |
| Rate limits | One runaway caller can't starve everyone else |
| Safety switches | Everything stopped in seconds, and resumed exactly as before |
Money¶
| Concept | What it's for |
|---|---|
| Prices and the rate card | Every call priced correctly, with no spreadsheet |
| Cost | Who spent what, with numbers Finance can bill from |
| Budgets | Surprise bills stopped before they happen |
Seeing and proving¶
| Concept | What it's for |
|---|---|
| Request logs and the call record | "What happened to this call?" answered in seconds |
| Dashboards and the impact report | Each role sees the story it answers for |
| Needs attention and notices | Problems reach whoever can fix them |
| Audit log | Who changed what, from where and why |
| Tamper evidence | Proof an auditor checks without trusting you |
| Retention, legal hold and subject requests | Records kept as long as the law needs, and no longer |
| Risk and AI systems | The AI systems that matter most, reviewed on time |
| Access reviews and incidents | Access shown to be right; a register of what went wrong |
Around Vidai¶
| Concept | What it's for |
|---|---|
| Integrations: email, BI and events | Vidai's data and alerts in the tools you already run |
| Editions and licences | What you have, and that a lapse never breaks traffic |
| Glossary | Every word on screen, defined once |