Air-Gap Courier
Sealed payloads that cross air gaps as unremarkable images — integrity-checked at every step.
The problem
/ 01Data often must cross physical or logical air gaps — classified enclaves, isolated networks, offline systems. Files are awkward; images look unremarkable and carry their own integrity checks.
What it does
/ 04Seals a payload into an image carrier with optional key encryption.
Verifies a package by id or by carrier round-trip.
Extracts the sealed payload with an integrity check.
Lists courier packages with their payload hashes.
Who it’s for
/ 03- Operations teams moving data across enclaves
- Teams needing discreet transfer with integrity verification
- Security architects designing offline data movement
In context
/ 01The transport layer for sealed artifacts — credentials, receipts, and evidence from sibling products ride in its carriers.
Spec & limits
/ limits| Interface | Input limits | Output artifact | Failure mode | Non-claim |
|---|---|---|---|---|
Studio ephemeral /demo; pilot durable /v1 on your infrastructure. | TBD — verified in pilot acceptance | TBD — verified in pilot acceptance | TBD — verified in pilot acceptance | TBD — verified in pilot acceptance |
Related guide
/ guideSee the air-gap data transfer guide for a deeper problem walkthrough and verification notes — evaluation notes for the live demo and for a private pilot. Also: try the live experiment and read the product overview.
Frequently asked questions
/ 0501 How is a payload sealed so it can cross an air gap?
The payload is sealed into an image carrier with an integrity checksum and receipt; the carrier is moved via removable media, not a network link.
02 What verifies the payload on the disconnected side?
An offline verifier checks the seal and checksum against the source registry hash that was exported alongside the carrier — no network needed.
03 Does this require a permanent software install on both sides?
No — the verifier and sealer are portable binaries run on demand; only the exported registry hash must be carried over.
04 Can the sealed carrier be audited later without re-opening it?
Yes — the receipt and checksum allow an auditor to confirm integrity and provenance without unsealing the payload.
05 How does this differ from encrypting a file and copying it over?
Encryption protects confidentiality; sealing protects integrity and provenance and remains verifiable after the transfer, even when re-encoded.