Private Beta · Q4 2026

Cipher OS

A zero-trust encrypted communications platform. Post-quantum hybrid cryptography, mesh-radio routing, and chain-of-custody audit on every packet. Pre-alpha running in the lab today.

Request Beta Access Specifications
Cipher OS · Session 7A3F PQC-HYBRID
21:04:07INITHandshake with mx-07
21:04:07KYBERML-KEM-1024 established
21:04:08OKHybrid channel active
21:04:12TX0x94a3…c12f · voice
21:04:12ACK47 ms · 2 hop
21:04:24AUDITLedger block #88124
21:04:30LINK42 nodes · 0 loss
What it does

Comms that survive contact.

Cipher OS replaces legacy encrypted comms stacks with a modern, zero-trust architecture. Every packet is authenticated, forward-secret, and auditable. Building in Wales under UK-sovereign chain of custody.

01

Post-Quantum Hybrid

ML-KEM-1024 paired with X25519. Survives quantum adversaries; compatible with classical key exchange today.

02

Mesh-Radio Routing

Self-healing mesh between nodes. No fixed infrastructure. Traffic finds a path even when cells and satellites fail.

03

Chain of Custody

Every packet writes an immutable audit record. Commanders retain defensible proof of transmission origin and handling.

04

Voice · Data · Sensor

One protocol for all three. Priority-tagged traffic with deterministic latency targets under load.

05

Runs Anywhere

Cipher Terminal, STIG-hardened Linux, allied tactical kits. One key-management plane across every endpoint.

06

Air-Gapped Pairing

QR-based first-trust establishment. No cloud. No external PKI. Operator-owned root of trust on every node.

Protocol flow

How a packet gets from operator to operator.

The four-phase Cipher OS handshake and packet delivery. Operators never think about any of this — it happens in the background every time the green light blinks on a Cipher Terminal.

CIPHER OS · HANDSHAKE + DELIVERY OPERATOR A CIPHER OS · NODE A MESH NODE CIPHER OS · NODE B OPERATOR B HANDSHAKE KYBER-1024 · X25519 · AES-256-GCM · ML-DSA sig PLAIN CIPHERTEXT CIPHERTEXT PLAIN LEDGER · BLOCK #88124
Protocol · 01–04
Encrypted before it leaves the device. Audited before it arrives.

Cipher OS terminates encryption on-device. Middle-boxes see ciphertext only. Every delivery writes to an append-only local ledger that can be attested to a programme auditor later.

  1. 01HandshakeML-KEM-1024 + X25519 hybrid. Identity proven with ML-DSA signatures.
  2. 02Encrypt on deviceAES-256-GCM with ephemeral keys. No plaintext on the wire.
  3. 03Mesh hopRouted through the nearest available mesh node. Transport is pluggable.
  4. 04Audit writeImmutable ledger entry with hashes of origin, destination, and timing — not content.
Target specifications

Cipher OS 0.9 — current pre-alpha.

Current0.9 pre-alpha · internal onlyprivate beta Q4 2026
Key ExchangeML-KEM-1024 + X25519post-quantum hybrid
SignaturesML-DSA-87 + Ed25519hybrid authentication
SymmetricAES-256-GCM · ChaCha20-Poly1305negotiated per session
Target AssuranceFIPS 140-3 Level 5hardware root of trust required
Target ClearanceUK SECRET · US SECRETevaluation opens 2027
TransportCipher mesh · LTE · SATCOM · Ethernetpluggable transport layer
Target Latency< 50 ms voice · < 200 ms datatwo-hop mesh, typical
DeploymentCipher Terminal · Linux · KVMone binary, three targets
AuditAppend-only ledgeron-device, optionally replicated
OriginWritten in WalesUK-sovereign source · cleared review
Also in the platform

Pair with.

Cipher Terminal →

The hardened handheld that runs Cipher OS natively. Sealed crypto enclave.

Operator Pods →

A pod-grade Cipher appliance ships inside every container, office, and vehicular pod.

DF-5 Tactical →

Cipher OS will be the default datalink for every DF-5 deployment.

Request a Cipher OS assurance brief.

Schedule Briefing