Sovereign by construction, layer by layer.
Policy can be broken. Architecture cannot. This page is the technical map of the Sovereign Intelligence Operating System: what runs where, what proves what, and why regulated data physically cannot leave the building. The estate behind it is protected by 104 filed UK patent applications and 2,340 claims.
The stack
Read top down: the surface your teams meet first, down to the silicon it all stands on. Every layer inherits the guarantees of the layer beneath it.
Studios
The work surfaceThe applications your teams live in: departments and messaging, meetings with sovereign minutes, documents and spreadsheets, CRM, projects and tasks, and the specialist studios for finance, legal, engineering and operations. Every studio runs on the same substrate and inherits the same guarantees, so nothing your people do leaves the building.
The assistant
OrchestrationOne assistant surface routes any request to the right studio, brain or automation. It plans, executes and verifies inside the perimeter, and every step it takes is signed and sealed before it commits.
The brains
ReasoningFifty specialised brains, twenty five domain and twenty five operational, coordinated by a deterministic arbiter. Each brain owns a domain; the arbiter routes each query to the best fit brain or composes a quorum across several for high-stakes decisions. Every routing decision is signed to the audit record.
The trust plane
Proof and containmentThe layer that makes sovereignty provable rather than promised. The Open Audit Record seals every action under FIPS 204 ML-DSA-65 post-quantum signatures, verifiable offline in any browser. Hardware identity is rooted in TPM 2.0 with measured boot. Sentinel intercepts destructive actions and quarantines prompt injection before anything commits. The sandbox gateway is the only, operator-commissioned path out.
The runtime
InferenceOn-device inference across CPU, GPU and NPU, with hybrid offload so the operator chooses the balance. No network is required to function: no call-home, no telemetry, no cloud sync. The only packets the system ever sends are those the operator explicitly commissions and signs.
The hardware
Customer-owned groundThe system runs on hardware the customer owns outright: a single sovereign workstation, a fleet across an office, or rack-scale inference in the server room with Pantheon. The estate scales by adding machines, and ownership never moves.
Four properties, held by construction
Offline by architecture
The system never requires a network to function. Sovereignty is a property of the substrate, not a policy promise.
Zero egress by construction
There is no default path out of the building. Egress exists only where the operator commissions and signs it.
Everything signed, everything sealed
Every action is signed before it executes and sealed to a tamper-evident, post-quantum audit record the customer holds.
The operator holds the keys
Keys are generated and kept on customer hardware. No vendor override, no escrow, no remote kill switch.
Three deployment shapes, one codebase
The architecture scales by adding customer-owned machines, never by surrendering custody. Each shape carries identical guarantees.
Sovereign workstation
A single operator, one machine, fully air-gapped. The complete operating system, brains and audit plane on one desk. The shape used for the most sensitive work: casework, deal rooms, incident response.
On-premise estate
The same system installed in your server room, serving your departments across the office network that you own. Multi-user, department-aware, every seat inheriting the same zero-egress guarantees.
Air-gapped enclave
For defence, national security and critical infrastructure: no network path exists at all. The system is built to survive the air gap indefinitely, including audit verification, which needs only a browser and the operator public key.
Architecture is one of three trust surfaces. The control catalogue lives on the security page; the regulatory mappings live on the compliance page.
Walk the stack with the team that built it.
A briefing covers the full architecture against your estate: hardware, isolation, audit and the deployment shape that fits. Nothing you share leaves the room.