Stable Works Talk to us

Battlespace awareness

War Horse

Know which device sent every report. Keep mission chat out of reach of the server itself. Keep the TAK tools your teams already carry. War Horse is situational awareness built for a threat model where the server, the relay, and the network can all be compromised.

The problem with a picture you cannot verify

On most situational awareness servers the transport is encrypted and the payload is not: the server reads every position, every chat line, and every remark. A client certificate proves which connection delivered a message, not which device wrote it, and anything relayed through another server arrives with no provenance at all.

If the server sits on someone else's hypervisor, or a box walks off a table, that is everything the unit ever sent. War Horse starts from that threat model.

  • Signed at the source. Android, iOS, and the browser sign every CoT event they send with ML-DSA-65.
  • Sealed chat. Mission chat is sealed under keys the server never holds, wrapped to each device with ML-KEM-768 and P-256.
  • Post-quantum on the wire. Every TLS listener offers X25519MLKEM768 first, and so does every link to its own databases.
  • Clean revocation. Remove a member and the next sender rotates the mission key to exactly the devices still in it.

See the check

A forged report does not make it onto your map

Every report is signed by the device that wrote it and checked on arrival. Alter one on its way in and the check fails, the report is thrown out, and the picture stays true. TAK clients keep working and show as unsigned.

Interactive demo

Every report is checked. A forged one never reaches the map.

A1 B2 C3 D4 forged

Reports arrive every couple of seconds. Arm the tamper button and watch what happens to the next signed one.

Signature check

Verified 0 Unsigned TAK 0 Rejected 0
  1. Waiting for the first reportStanding by

Simulated in your browser to show the idea. These are not live readings.

What it is

LayerWhat it is
ServerGo. The API, the CoT router, voice, a worker, and the admin tool, in one static image.
AndroidKotlin and Compose, with device keys in the Android Keystore.
iOSSwiftUI, with ML-KEM and ML-DSA from CryptoKit and the device key in the Secure Enclave.
WebA common operating picture in any browser, with keys that cannot be exported.
VoiceA Mumble compatible server, TLS only, with channels gated by mission.
OverlayFlux, for devices with no public route at all.

Built for the field

TAK on day one

ATAK, WinTAK, and iTAK connect with a certificate and show up on the same map. Their events are labeled unsigned, because they are.

Voice inside TLS

Push to talk rides inside the same TLS connection as everything else, so voice gets the same post-quantum key exchange and needs no UDP port.

Night vision

A dimmed phosphor display on every client. The phone apps read a goggle mount over Bluetooth LE and switch to night mode when the goggles come down.

Helmet and vehicle feed

A compact stream for heads-up displays: positions coalesced to one message per unit per second, with alerts and voice activity as they happen.

Who it is for

Teams already on TAK

Keep ATAK, WinTAK, and iTAK in the field and add signed, sealed War Horse clients alongside them, on the same map, at your own pace.

Security and response operations

Anyone who has to prove after the fact who reported what, and when, with a record built from signed events instead of memory.

Programs and integrators

Teams that need a situational awareness core with provenance and post-quantum security already built in, to build their own mission on top.

Work with us

See War Horse on your network

Tell us about your unit, your devices, and the links you have to work with. We will show you War Horse running on the same kind of ground.