Sovereign cloud operations — air-gapped where the mandate requires it.
Run cloud, on-prem and hybrid estates from one control plane inside your own borders — air-gapped where the mandate requires it, with residency and accreditation evidence built into the architecture.
Built for
- Federal Government
- State Authorities
- Ministries
- Defense
- Public Sector
- Air-gapped
- Deployment class with offline updates and no call-home
- FIPS
- Validated cryptography throughout
- WORM
- Immutable, append-only audit log
- In-region
- Whale AI on local models only
Regulatory reality
The regimes, and the control that answers each
National data-residency law
What it demands
Data, inventory and audit records stay inside the border, provably
The control that answers it
In-country deployment classes; residency enforced per resource and evidenced from the audit log
Security accreditation (FedRAMP / IRAP / StateRAMP-style)
What it demands
Control evidence assembled to an accreditation framework
The control that answers it
Compliance pack export from the WORM-backed audit trail; FIPS-validated crypto
Air-gap mandates for classified estates
What it demands
No outbound connectivity, controlled update path
The control that answers it
Air-gapped deployment class with signed offline update bundles
Privileged-access rules
What it demands
Every administrative session attributable and reviewable
The control that answers it
PAM always-on with session recording; MFA mandatory on every role
Use cases
Four workflows, mapped to the modules that run them
- 01
Sovereign, air-gapped governance across agencies
Run an air-gapped Government Edition deployment with no outbound connectivity and an offline update channel, unifying inventory, identity and governance across agencies through a single control plane — directorates segregated, policy central.
- 02
In-country data residency with in-region AI
Pin workloads, inventory and audit records to an in-country region, with Whale AI Abyss on in-region models and no call-home — intelligence that never leaves the jurisdiction.
- 03
Hardened privileged access
PAM is always on with session recording, MFA is mandatory on every role, and identity federation maps your directory to platform roles — privileged access is provably controlled.
- 04
Accreditation evidence on demand
Every action lands in a WORM-backed audit log; compliance pack export assembles the evidence for FedRAMP / IRAP / StateRAMP-style accreditation, with ITSM change control (P0–P4 SLAs) behind it.
Reference architecture
Sovereign digital infrastructure for ministries, agencies and national programmes
The seven-layer Government architecture sheetGovernment & Public Sector architecture — open it here, or full screen to read every label
Fig · Government — reference architecture
5400 × 3120
Government & Public Sector architecture
Sovereign digital infrastructure for ministries, agencies and national programmes
How to read it
- 1Channels & users — The consoles and portals each persona works in
- 2Digital Experience Layer — Catalog, self-service, metering and SLA per service — multi-tenant by design
- 3Unified Platform Core — Nine modules under one console, one identity, one policy and one bill
- 4Integrations — How the platform plugs into the systems the estate already runs
- 5Estates & data — Every estate managed as one, and the data stores that hold the evidence
- 6Request flow — The seven steps every call takes — identity, policy, orchestration, evidence
- 7Deployment modes — SaaS, BYOC, on-premise, sovereign air-gapped and edge — the same build
Gold-marked for Government
Modules that lead
Deployment modes that fit
Plugs into
National identity & SSO · Government service bus · ITSM & service desk · Budget & finance systems · Document & records · API & connectors
Questions
Procurement, hosting and integration questions
01How is the platform procured for government?
Through tender or empanelment on 3–5 year fixed-bid terms, directly or via an accredited implementation partner. The Government Edition is priced as the Enterprise base plus the sovereignty layer.
02Where does it run?
On sovereign on-prem infrastructure, in a private government cloud, or at government edge sites — fully air-gapped where required. Sovereign hyperscaler regions connect through the same connectors.
03Does Whale AI need internet access?
No. The Government Edition runs Whale AI Abyss on in-region models inside the perimeter with zero external calls.
Next step
Bring your Government estate to a working session.
We connect one of your accounts read-only during the session, walk the Government workflows above on your real resources, and leave you with the control mapping for your regimes.