DCS Labs · Defence & security

Proof that holds when the network doesn’t.

Forces are being connected, automated and contested at once. Across the lab we build one thing for them: evidence of every order, decision and change that survives jamming, outlives today’s cryptography and can be checked by an ally without touching your network.

R-Series for Defence Four lanes
SignaturesHybrid post-quantum
Designed forDenied, disconnected links
StatusIn development

An adversary listens, spoofs, jams and waits. The record has to survive all four.

01 Four lanes

Defence across the lab.

R-SERIES · FORCES

Orders, autonomy, firmware, QKD

Signed orders verified before action; bounded autonomy and sealed on-board receipts under electronic warfare; firmware checked before flashing; QKD with post-quantum authentication; and a choice of hybrid ML-DSA-65 or ML-DSA-87 (the defence profile, in development).

R-Series for Defence → COSRYX · ORBIT · SPACE SEGMENT

Spacecraft that prove what they obeyed

Commands signed on the ground and checked on board, signed autonomy changes during link loss, and mission logs verified on the ground by two independent verifiers.

COSRYX · ORBIT → IOT / OT · BASES AND INFRASTRUCTURE

Bases, ports, power and water

Post-quantum migration for the plants and device fleets that forces depend on, with a gateway for devices that cannot change and evidence at every step.

IoT / OT →
DRONE TRACK · FUTURE

A trust layer for autonomous systems

Secure command link, command authorisation, firmware signing, a signed black box and defined link-loss behaviour. Electronic-warfare hardware through partners. Starts only under a specific programme’s terms.

Future direction
02 Domains

Sea, air, land, uncrewed, command, supply.

Where a receipt adds value. These are design targets, not deployments we have completed.

NAVY

Naval forces

Ship-to-shore orders, long patrols with intermittent links, combat-system changes on record.

AIR FORCE

Air and airborne C2

Taskings receipted end to end; airworthiness records that last the airframe’s life.

ARMY

Land forces and armour

Orders across tactical radio; vehicle firmware checked before flashing.

UNCREWED

Drones and autonomy

Signed mission bounds; every decision sealed on board, even when jammed.

COMMAND

Headquarters and C2

Nation-held keys; AI-assisted planning with the human approval on record.

LOGISTICS

Supply chain

What was shipped, flashed and repaired, from factory to field.

03 One theatre

From the order to the after-action review.

Theatre01 / 05
01 · ORDERS

Every order leaves a signed trail.

Signed with Ed25519 and ML-DSA-65, checked by ship, armour, aircraft and drones before they act.

02 · LINK DENIED

Jammed, but not blind.

The drone acts only inside bounds its commander signed in advance, and seals every decision on board.

03 · RESTORED

The backlog comes home intact.

Every entry and the chain are checked on arrival, so a gap, an edit or a reordering shows up.

04 · FIRMWARE

Nothing unsigned is flashed.

A tampered image is refused, and the refusal is itself a receipt.

05 · AFTER ACTION

An ally verifies without your network.

The chain goes to a coalition partner, who checks it offline with the issuer’s public keys.

04 Clear lines

What we build, and what we don’t.

WE BUILD

The trust layer

  • Signed, chained receipts for orders, decisions and changes
  • Offline verifiers anyone can run
  • Key lifecycle, epochs and revocation
  • Post-quantum migration with evidence
WE DON’T

Weapons, or your decisions

  • No weapons, targeting or fire-control logic
  • No electronic-warfare hardware of our own
  • No keys held by DCS: the nation holds them
  • No certification claimed before it is granted

Defence engagements proceed only under the required government permissions, export rules and tender terms of the country concerned. Deployments can run fully on-premises and air-gapped.

Working on a defence programme? Architecture, live demonstrations and detailed status are shared in a private technical briefing, under NDA. Write to hello@dcslabs.ai.

Request a technical briefing