What we speak
The platform connects multi-vendor sensors and effectors to NATO command systems through the standards NATO is building interoperability on. This has been validated live, not only described.
Standards and protocols
| Standard | Role | Status |
|---|---|---|
| SAPIENT (Protobuf/JSON, BSI Flex 335) | Sensor and effector messaging ingress | Live verified with NATO's LCI-X and NCIA, June 2026 |
| CoT / ATAK | Situational awareness egress | Live |
| SAPIENT HLDMM | High level data model egress | Live |
| MAVEN/MSS (Palantir) | ML and data fusion | Live |
| C2 / CRC / CAOC | Command systems | Live |
| Link 16 | Tactical data link | Live |
| ASTERIX | Air surveillance data | Live |
| Stone Soup | Tracker core | Live, open source |
The connector library
A connector translates a specific sensor or system's native format into the platform's ingress format. New connectors are commissioned as new sensors and systems are onboarded. Each one then stays in the library for reuse by the next company that needs it. Connector code for the open ingress layer is available through Context Foundry under Apache 2.0.
Security and identity
Identity and access is Keycloak based and Kubernetes native. Role based access runs under NATO Unclassified protocols, with dynamic credentials and least privilege applied by default. Every action taken by every connected company is auditable, which is what makes multinational work possible at all.
Certification path
Conformance validation, for companies that need to prove their capability reaches operational systems, runs through DEFINE AI Foundry.