Halo · Defense 01 / 07
Halo is Lagrange's coordination engine for autonomous systems. It maintains shared state, adapts under failure, and keeps systems operating in degraded and adversarial conditions without central control.
What it does 02 / 07
The hard problem is keeping a group of autonomous systems coordinated when conditions are contested, unreliable, or fragmented.
Lagrange built Halo, the coordination engine that solves this. It maintains shared state across distributed autonomous systems, adapts when the network degrades, and reassigns work when systems fail. All without requiring a central command node to be reachable.
It is not mission software. It is not a command-and-control platform. It is the coordination engine everything else runs on.
In motion 03 / 07
Reference Coordination Modes 04 / 07
Multiple autonomous systems share a sensor picture in real time. Each system's view contributes to a single operational picture, even under jamming and partial connectivity.
Autonomous systems maintain network connectivity for each other, dynamically routing around failed nodes and re-establishing links as conditions allow.
A group holds a formation or coverage pattern as individual systems are lost, with remaining systems redistributing position and responsibility.
When a system is lost or tasking changes, work is reassigned across the remaining group. Without operator intervention. Without breaking the mission.
Run a scenario 05 / 07
Pick a mode. Drop assets onto the map. Introduce failure. Watch the system reassign and hold shape in real time.
Deployment 06 / 07
Runs at the edge, on the autonomous platform itself, and off the platform, on a ground station or command node. Hybrid by design. No new runtime to adopt. No orchestration plane to manage.
Designed to integrate with existing autonomy stacks at the SDK level, without requiring core replacement. Built to make the integration tractable for teams already shipping autonomous systems.
Runs on the platform itself.
No core replacement required.
Ground, maritime, manned-unmanned teaming next.
Where we're heading 07 / 07
Autonomous systems are becoming the dominant share of how work gets done. In the military and elsewhere. Halo ships today as the coordination layer.
The path from there runs through field validation, and ultimately fully coordinated autonomy. Halo proves AI execution you can trust and coordinates autonomous action you can rely on. Read the full roadmap →
Halo ships with four reference coordination modes, edge and ground deployment, and SDK-level integration into the autonomy stacks already flying.
First field trials under electronic warfare and GPS denial. Scale past 50 nodes. Anti-spoof membership proof and proof-carrying rules of engagement.
A swarm that splits under jamming and rejoins can prove it made no contradictory commitments. Coalition trust without disclosure. A tamper-evident record of every decision.
The swarm coordinates on succinct proofs instead of trust. Autonomy that cannot act outside its authorized envelope. A prover that runs on the platform itself, in flight.
See Halo run in your operating conditions. We'll walk the coordination engine, the reference modes, and integration at the SDK level.
