Sovereign AI
You're not choosing a model. You're choosing a jurisdiction.
You know where your data is stored. Do you know whose laws can compel the data your AI calls pass through? Vidai keeps that decision yours, from inside your own network.
- A call from the UK goes to a model in the EU. A region rule allows it.
- The same call to a model in the US is refused before it leaves, and the refusal says why.
- Where the provider is headquartered matters too: its home law can reach data it holds abroad.
The gap
Which laws can reach your AI stack.
01
The contract stops at the API
Your residency agreement governs where your data is stored. It has no force over the model your application then calls, which answers to whatever legal regime its provider does.
02
Reach follows the provider, not the data
Major jurisdictions can compel a provider headquartered under them to disclose data, wherever in the world it's held. Where you stored it stops being the question.
03
Agents multiply it
A fifty-step agent loop that touches customer records and policy documents crosses that line fifty times, not once.
The four sovereignties
Control at every layer that matters.
Jurisdictional sovereignty
The data that crosses a legal boundary is the data you chose to let cross, masked and policy-checked, and nothing else.
Infrastructure sovereignty
Inside your cloud account, data centre or a fully air-gapped network. No telemetry. You own the deployment and the upgrade cadence.
Vendor sovereignty
Adding or switching a model is a configuration change, not a procurement cycle. One security review covers every provider.
Regulatory sovereignty
One boundary keeps AI inside the compliance regime you already operate under, with no new third party in the data path.
Why not a hosted service
A hosted service in the path adds to the exposure.
One more jurisdiction in the path
A hosted service routes every prompt through someone else's infrastructure before it reaches the model. Its legal regime becomes one more party that can be compelled.
It has to see your traffic
A hosted service sees your traffic to operate and bill it. Vidai has no telemetry and no usage callback, and you can verify that on the wire.
Their uptime becomes yours
A hosted hop in front of every AI call is a critical third party you don't control: the concentration risk supervisors now ask about.
Small enough to be yours
The part in your AI traffic is a single engine of about 25 MB. It runs inside your network, or fully air-gapped, without a new cluster to run.
Air-gapped → Your data centre → Data protection → The Sovereign models add-on →
VidaiAssistant · A separate product from Vidai
An expert assistant for work that can't go to the cloud.
Running locally, no network
Every claim, with its evidence.
A sources card appears before the answer, so you see what was found and how strongly it matched. A confidence mark sits on every answer.
Everything about VidaiAssistant →
Backed by evidence, or it refuses
Every claim is tied to a numbered citation you can click through. When the evidence isn't there, it says INSUFFICIENT EVIDENCE rather than inventing an answer.
It reads the drawing
Schematics and figures are captioned and indexed when a knowledge pack is built, so a small offline model can answer from a diagram, and cite the figure.
Build a pack once, use it anywhere
One portable, versioned file with the corpus, the index and how it was built. Build it on a workstation; open it on a laptop with no network.
Air-gapped by construction
An egress lock, a per-pack policy that forbids any non-local model, no telemetry, and content encrypted at rest.
The pack library
Every pack carries its own provenance.
Quality score, version lineage and egress policy are shown on the pack itself, not buried in settings.
How we start together
Sovereignty without a rebuild.
- 01
Pick one app or team
Point it at the Control room. One configuration change; nothing else changes.
- 02
Watch for two weeks
Every call priced, checked and recorded. Rules start in observe mode.
- 03
See the evidence
What it cost, what it caught and what it would have stopped, from your own traffic.