WhitepaperSovereignty

Sovereign cloud: architecture patterns

In-country, air-gapped and in-region AI — how sovereignty becomes a property of the architecture

4 min read · 3 pp PDFUpdated September 2026 · v1.0
Download the PDF

A4 · no form, no email required

Talk to us about it
Glass panels standing in a steel rack, one of them royal blue

Sovereign Cloud is the deployment for estates that must prove where data lives and who can reach it: the control plane runs in-country, on your own cloud, on-premises or fully air-gapped, with an offline update channel and no call-home. Whale AI runs on in-region models inside the perimeter, and the audit trail is WORM-backed, so sovereignty is a property of the architecture rather than a clause in a contract.

Air-gapped
Deployment class with signed offline update bundles and no outbound connectivity
In-region AI
Whale AI Abyss on local models — zero external calls
5 + in-country
SaaS regions (SIN · BOM · DXB · FRA · LAX), or BYOC / on-prem anywhere

The pattern, end to end

  1. 1

    Pattern 1

    The platform is deployed inside national borders — BYOC, on-premises or fully air-gapped.

  2. 2

    Pattern 2

    An air-gapped control plane runs with no outbound connectivity; updates arrive as signed offline bundles.

  3. 3

    Pattern 3

    Residency rules are enforced on every resource and record; directorates are segregated under central policy.

  4. 4

    Pattern 4

    In-region models deliver Whale AI without data leaving the jurisdiction.

  5. 5

    Pattern 5

    Sovereignty is evidenced on demand from the WORM-backed audit trail and residency controls.

Sovereign Operations — the module behind it

Segregation under central policy

Ministries, directorates or agencies operate their own estates with autonomy inside national guardrails — one policy plane, many isolated domains.

Air-gapped classes

The most sensitive estates run fully disconnected with an offline update channel; hybrid classes connect to sovereign clouds such as AWS GovCloud, Azure Government and Google Distributed Cloud.

Hardened by default

FIPS-validated cryptography, MFA mandatory on every role, PAM with session recording always on, residency enforced and evidenced.

Offline-tolerant edge

Remote sites keep operating under headquarters-grade policy when disconnected and reconcile when they reconnect.

How it is operated

  1. 1

    Classify estates

    Assign each estate a deployment class — in-country connected, sovereign cloud, or air-gapped.

  2. 2

    Segregate and govern

    Directorates get isolated domains; policy, identity and audit remain central.

  3. 3

    Evidence continuously

    State-audit evidence and compliance packs (FedRAMP / IRAP / StateRAMP-style) are generated from the WORM-backed trail.

What national regimes demand, and the control that answers

RegimeWhat it demandsControl
National data-residency lawData, inventory and audit records stay inside the border, provablyIn-country deployment classes; residency enforced per resource and evidenced from the audit log
Security accreditation (FedRAMP / IRAP / StateRAMP-style)Control evidence assembled to an accreditation frameworkCompliance pack export from the WORM-backed audit trail; FIPS-validated crypto
Air-gap mandates for classified estatesNo outbound connectivity, controlled update pathAir-gapped deployment class with signed offline update bundles
Privileged-access rulesEvery administrative session attributable and reviewablePAM always-on with session recording; MFA mandatory on every role

The Government Edition sovereignty layer

  • Full Enterprise platform, sovereign/air-gapped deployment
  • PAM always-on, MFA mandatory, FIPS-validated crypto
  • Immutable audit log (WORM), data residency enforcement
  • Compliance pack export (FedRAMP/IRAP/StateRAMP-style accreditation evidence)
  • Sovereign cloud connectors: AWS GovCloud, Azure Gov, GDC, national clouds

Sovereign hyperscaler regions

AWS GovCloud, Azure Government, Google Distributed Cloud and national sovereign clouds connect through the same connectors and are governed by the same policy plane as private and air-gapped estates. Whale AI runs on in-region models with no external calls; on the Government Edition it runs fully offline.

Questions from accreditation and procurement teams

01

How do updates reach an air-gapped estate?

Signed release bundles are transferred through your approved process and verified on import. Nothing calls home, and there are no forced upgrades on sovereign estates.

02

Does Whale AI work without internet?

Yes. The Government Edition runs Whale AI Abyss on in-region models inside the perimeter, with no external calls.

03

Can we connect sovereign hyperscaler regions?

Yes — AWS GovCloud, Azure Government, Google Distributed Cloud and national sovereign clouds connect through the same connectors, governed by the same policy plane.

04

How is it procured and priced?

Tender- and empanelment-ready on 3–5 year fixed-bid terms, priced as the Enterprise base plus the sovereignty layer, directly or through accredited implementation partners.

05

How do updates reach an air-gapped deployment?

As signed release bundles transferred through your approved process and verified on import. There is no call-home and no forced upgrade on sovereign estates.

06

Which accreditations does it support?

Compliance pack export produces evidence for FedRAMP-, IRAP- and StateRAMP-style accreditation; the platform itself holds ISO/IEC 27001, 27017, 27018, 27701 and ISO 22301 certifications.

Next step

Take this from paper to your own estate.

A 45-minute working session with a solutions engineer: one of your accounts connected read-only, the parts of this document that matter to you shown on your real resources.