Editions and licences¶
A licence problem should never become an outage. Vidai comes in two editions, and whatever happens to a licence, calls keep flowing and nothing is deleted: at worst, Vidai runs with fewer features until it's renewed.
Two editions¶
Community is a complete governance platform on its own: people, teams, roles, keys, providers and models, model access, guardrails with pattern checks, routing and fallback, regulations and retention, the tamper-evident audit log, prices, cost and budgets, rate limits, Stop AI traffic, Request logs and dashboards, and multi-factor sign-in.
Enterprise adds features for larger organisations. What it includes depends on the features your licence includes; among them:
| Feature | What it adds |
|---|---|
| Single sign-on | Sign in with your identity provider; groups mapped to teams and roles |
| VidaiGuard | Once set up, Vidai's own models check content beside your gateway, alongside pattern checks; guardrails are complete on patterns either way |
| Region rules | Keep calls in an area for the organisation, an environment, a team, an application, a person or agent, or a key |
| Tamper evidence on both sides | Sealed, signed records, checks, the auditor report and the evidence pack |
| Coverage per control | Each regulation's controls shown as enforced, observed, partly in place or a gap |
| Compliance officer | The role and its dashboard |
| Service accounts | Accounts and API tokens for your own systems |
| Serious incidents | The incident register |
| Recompute | Price past calls again after a price change |
| BI push and event webhooks | Data to your BI tools; events to your SIEM |
Each feature's page in these docs is marked Enterprise, and says what a Community reader has instead where it matters.
Your licence, and Your edition¶
Organisation admins and viewers open Settings › Licence: the edition, the licence (Evaluation, Community or Enterprise), when it expires, the customer reference to quote, and Limits: how many people, keys, agents and service accounts you use against what the licence allows, with Nearly at the limit from 90%. Under What your edition includes, each feature reads Included, Needs a licence (Enterprise, but your licence doesn't list it) or Needs the Enterprise edition. Versions lists the version of each part, for support.
Anyone else opens Your edition from Search or jump to… and sees their edition and what it includes, so a user can tell at once whether a feature they've read about is theirs.

When a licence ends¶
flowchart LR
A["Licence in force"] --> B["Ends in N days<br/>(notice)"]
B --> C["Expired: everything keeps<br/>working for a grace period"]
C --> D["Grace over: Enterprise features<br/>paused, lower limits"]
D -->|renew| A
- Nothing is deleted. After the grace period, Enterprise features pause and limits are lower; service accounts' tokens stop, but the accounts and their roles stay. Renewing brings everything back.
- At a limit, nothing existing stops working; only creating more of that kind is refused, and Home says so.
- Moving between editions loses nothing. Upgrading needs no migration: features appear as the licence lists them.
- The licence is checked where Vidai runs, with no call home. Whoever runs your Vidai servers installs the key; the Control room never asks for one.
Related¶
- The parts
- Needs attention and notices: licence notices
- People and roles