Sovereign and air-gapped · Enterprise

The whole stack, inside your boundary.

We deploy the stack that runs Admiral Cloud inside your boundary, air-gapped when the operation requires it. Control plane, registry, telemetry, remote-access relays, device PKI and releases all run on infrastructure you own, with no route to us.

Security posture

What leaves your network

Device traffic: Nothing
Telemetry and logs: Nothing
Images and updates: Nothing
Remote-access sessions: Nothing
Releases from Admiral: Signed, pulled or carried in
Licence reporting: Periodic signed export

Fully disconnected sites receive releases by transfer. Nothing has to phone home.

The stack

Six components. All of them run where you say.

Admiral Cloud is one deployment of this stack. A sovereign deployment is the same signed releases on your infrastructure, operated by your team with ours on call.

Control plane

Fleet API, console and rollouts.

Your Kubernetes or VMs, inside your network boundary

We deploy the platform that runs Admiral Cloud into your cluster. Devices enrol against your hostname and never need a route to the internet.

Images

OS builds and container registry.

Your registry, your signing keys

OS images for your fleet are signed with a key set generated for your deployment rather than ours. Devices pull workloads from your registry, and registry fallback points at your mirror.

Telemetry

Metrics, logs and alerting.

Your storage, your retention policy

Device health, logs and alert rules land in storage you run. Nothing is exported for analytics or support unless you send it.

Access

Remote access and EdgeWire relays.

Relays on your perimeter, direct where the network allows

Workload shells and EdgeWire sessions terminate on relays you operate. Identity and session approval stay inside the boundary.

Identity

Device identity and secrets.

Your PKI and recovery-key escrow

Devices are provisioned against a certificate authority and Secure Boot keys generated for your deployment, and disk recovery keys escrow to your store.

Updates

Releases by transfer.

A one-way transfer or a site mirror

Signed releases cross into your network by transfer and roll out from your own registry with the same A/B rollback as any release. Updating a device from USB at a site with no network at all is in development.

Who runs it this way

Fleets that cannot depend on a vendor's uplink.

Defence and government.

Classified and sovereign-cloud programmes that cannot route device traffic through a vendor, and require data residency and a documented chain of custody for every image.

Critical infrastructure.

Mining, utilities, ports and water, where OT networks are segmented from the internet by policy and a vendor outage must not stop a rollout.

Regulated sites.

Hospitals, banks and manufacturing floors whose security teams approve a stack only when they can run it, audit it and switch it off themselves.

The device side is identical: signed read-only OS, dm-verity, TPM-sealed disks, USB policy, no listening ports, hybrid post-quantum TLS to your relays. Security posture

Questions

What security teams ask.

Is this a different product from Admiral Cloud?

No. It is the same AdmiralOS and fleet platform deployed inside your boundary, and the admrl CLI, the MCP server and the API work the same way. Devices trust the keys of the deployment they were provisioned for, so a fleet piloted on Admiral Cloud moves in-house with one reprovisioning pass.

Who operates it?

Your team, with our engineers on a named escalation path. We ship signed releases of the control plane and OS the same way we ship to Admiral Cloud; you decide when to apply them. Fully disconnected sites receive releases by transfer.

Does anything phone home?

Nothing has to. Update checks, telemetry, remote access and registry traffic all go to your control plane. Devices also try a short list of public time servers, DNS resolvers and connectivity probes as fallbacks. With no internet route those attempts fail and change nothing, and we list them for your firewall team during scoping. Licence reporting can be a periodic signed export rather than a live connection.

Which parts are open?

The admrl MCP server is public on GitHub and the API is documented. The EdgeWire transport library and the on-device agent are being prepared for public release so your security team can read what runs on the machine. Under an Enterprise agreement we arrange source access for the rest of the stack.