Capabilities
What we build
Most hard programs need the same six things. Buying them from six places is how the seams end up being where the failures live, so we build them to work as one system from the start.
Digital twins
A twin is only worth having if it stays true to the thing it models. We build twins that are fed from the field, versioned like code, and trusted enough to plan against.
- Terrain, structures, fields, and routes, built from survey, imagery, and what the devices on the ground report.
- Fleets of people, vehicles, and machines, with position, heading, health, and history.
- The network itself as part of the model: which links exist, how good they are, and what happens when one drops.
- Rehearsal and what-if runs against the twin before anything moves in the real world.
Autonomy and teaming
Autonomy that earns trust one decision at a time, built to work alongside the people who answer for it.
- Perception, planning, and control loops designed and tested against the twin first.
- Many small systems composing into one capability, so losing a piece degrades the whole gracefully instead of breaking it.
- A person in the loop on every decision that carries consequence, with the authority to see why a system chose what it chose.
- Logs and provenance on every action, so an after-action review has facts instead of guesses.
Situational awareness
A common operating picture is only as good as your confidence in where each report came from.
- Every event signed on the device that produced it, so provenance survives relays and federation.
- Native clients on Android, iOS, and the browser, and interoperability with the TAK tools crews already carry.
- Mission chat sealed under keys the server never holds.
- Built on the same core whether the map shows a battlespace, a farm, or a warehouse floor.
Resilient networks
Assume the link will be contested, degraded, or gone, and design so the mission keeps going anyway.
- Zero-trust overlays that need no open inbound port at the edge and reach devices with no public route.
- Events, the API, and voice all on one TLS port, so a site that allows web traffic allows the mission.
- Map areas loaded ahead of time for the whole area of operations, so the map keeps working where the signal does not.
- Graceful degradation measured against the twin, not assumed.
Post-quantum security
Data captured today can be decrypted later. We ship the post-quantum standards now, in production software.
- ML-DSA-65 signatures on device-originated events.
- ML-KEM-768 with P-256 to wrap keys to each device, and hybrid X25519MLKEM768 offered first on every TLS listener.
- Device keys held in hardware where the platform has it: the Android Keystore, the Secure Enclave, and browser keys that cannot be exported.
- Security by construction: short-lived tokens, refresh tokens that revoke their whole family when replayed, and every device revocable on its own.
Embedded and edge systems
The best software in the world does nothing if the box it runs on cannot survive where it is going.
- Mission and edge computers chosen and qualified for size, weight, power, and the environment they will see.
- Real-time software where timing matters, with the worst case measured rather than hoped for.
- Sensors, radios, and their integration, from the bench to a vehicle.
- Hardware and software designed together, so the twin models the box as well as the code running on it.
Work with us
Your program is one briefing away from a working system
Give us thirty minutes and the problem you are up against. You leave with an honest read on what we can field, how fast, and what a pilot would prove.