Skip to content

Where AI may run

The problem. A data processing agreement says "processed in the EU". A developer switches to a newer model that happens to run in the US, and nobody notices until an audit. With Vidai, where a call may go is decided in the gateway: a call to a model outside the area, or off the approved list, is refused before it leaves, and the refusal says why.

Three controls

Control What it does Edition
Approved for use (Models & routing › Models) The list of models any call may reach. Once it has entries, every other model is refused at the gateway, for everyone, and no emergency override lifts it Every edition
Region rules Keep calls from a level (the organisation, an environment, a team, an application, an agent) within an area, such as the European Union. Only models that run within it are offered or used Enterprise
Compliance routes Send calls for a model to a compliant deployment of it (for example its EU deployment), always, with no exemptions Enterprise

What Enterprise includes depends on the features your licence includes. On Community, the approved list and each team's and agent's Model access decide which models may be called; choose models whose providers run where you need them.

Provider agreements a region rule can require Enterprise

Each provider can record its agreements: a GDPR data processing agreement, a HIPAA business associate agreement, a PCI DSS attestation, each with a reference and an optional end date. A region rule can say Also require these agreements: calls under it then reach only providers in the area that hold each one today. An agreement past its end stops counting, and the models it covered say so.

Where a model runs

A model runs where its provider is placed, unless the model says otherwise. A provider placed nowhere, or "global", meets no region rule: "may run anywhere" isn't "runs in the EU". Before you set a region rule, check that your providers are placed.

What a refused call looks like

In Request logs, a call a region rule refused reads Region rule, names the rule, where it's set and the named policy it belongs to, and both areas: "Refused: processed in US, outside EU." The app gets a refusal in its own SDK's error format.

Good to know

  • These rules reach AI calls sent through the gateway only, not your other systems.
  • Region rules have no watching mode: a region rule in an observing policy isn't in force until the policy enforces.