/engine/sovereignty

Isolation is enforced at the data layer, not promised contractually.

In-country, on-premise, or fully offline. A deployment that cannot reach the internet is a supported configuration, not a compromise.

Where it runs

In-country

Hosted inside your jurisdiction, on infrastructure your regulator already accepts.

Who holds it

On-premise

Installed in your own estate. Updates arrive on your schedule, and the configuration ships with the licence.

What it needs

Fully offline

Enforced offline mode, verified with the network removed. A closed corpus does not need the internet to answer.

Running dark

Enforced offline mode blocks outbound access at the runtime before anything loads. There is no web search tool in the system to disable — one was never built. Training-data recall is not treated as fact and cannot be cited.

Operator access

Each institution’s data is isolated beneath the application, so a coding mistake degrades to “sees nothing” rather than to a leak. Operator access is separated by privilege and audited.

Request the sovereignty brief Back to the engine