Rule of the house
Your country's data stays in your country unless a named human authorizes it to leave.
Every outbound connection is inspected before it crosses the line. Domestic traffic passes. Foreign traffic is held until someone with a name and a reason releases it. Click any crossing to open the record.
Crossing ledger
Every device, every destination, every decision. Nothing here is a summary — it is the record a reviewer would read.
| Device | What it is | Destination | Jurisdiction | Data | Calls/day | Bytes/day | State |
|---|
Deny-by-default: a destination is unreachable until it appears on the allow list with an owner and a reason. Blocking here writes the rule; it does not ask the vendor's permission.
AI passport
A model does not run until it can produce papers. Fill the record, get the determination.
Four determinations: Sovereign verified · Limited external connectivity · Foreign dependency detected · Unauthorized foreign transfer. The bottom strip is the machine-readable line — it carries the same determination in a form a gateway can check without reading the page.
Sovereign gateway
Sits between the person and the model. Identity is replaced before anything leaves; the outside model gets the question, never the person.
Before — what was typed
After — what actually leaves
The token map stays inside the border. The gateway can rejoin the answer to the person on the way back; the outside model never held the identity in the first place. This panel runs entirely in your browser — nothing typed here is transmitted anywhere.
AI bill of materials
A domestic model on a foreign runtime is not a domestic system. Set the jurisdiction of every link in the chain.
Three ways to stand up a sovereign deployment
Pick the level the mission requires, not the level the vendor prefers.
Country locked
- Connected, but storage, inference, backups and keys stay domestic
- Approved domestic regions only
- Foreign egress denied at the gateway
- Fits most business and school use
Sovereign private
- Customer owns the infrastructure
- The model comes to the data; the data never goes to the model provider
- Vendor has no operational access
- Fits healthcare, legal, finance, state agencies
Black — air-gapped
- No public internet, no cloud telemetry, no remote registry
- Models delivered by hand and verified by hash
- Fits defense, intelligence, elections, critical infrastructure
- Disconnected inference is already ordinary practice
Five things people run together, and shouldn't
| Term | The question it actually answers | What it does not cover |
|---|---|---|
| Data residency | Where does the data physically sit? | Who can reach it, and where it may travel |
| Operational sovereignty | Who can operate and access the system? | Whether it survives losing the vendor |
| Technological sovereignty | Does it keep running without a foreign vendor? | Who controls the models and keys |
| AI sovereignty | Who controls models, prompts, inference, training, keys, compute, logs, administrators? | Where the system is permitted to talk |
| Network sovereignty | Where is this system allowed to communicate? | Nothing — this is the one usually left out |