Minerva unified control for mixed fleets
Stark Defence
This is what turns Minerva from a drone app into a battlefield operating layer. STANAG 4586 is NATO’s common ground station standard for unmanned aircraft, and MAVLink is the lightweight command language used across many drones and ground control systems. Supporting both means one interface can ingest feeds, send commands, and coordinate missions across older NATO compatible aircraft, cheaper MAVLink based drones, and Stark’s own strike systems instead of forcing a military to replace its installed fleet first.
-
In practice, this means an operator can work from one screen instead of juggling separate vendor consoles. A recon drone can spot a target, an artillery radar can confirm where fire is coming from, and a third party loitering munition can be tasked to strike, all inside the same control workflow.
-
The closest comparison is the command layer built by groups like WB Group and Shield AI. WB bundles drones, loitering munitions, radios, and TOPAZ command software into a connected fires network, while Shield AI is pushing Hivemind as platform agnostic autonomy software that can be integrated onto outside aircraft. Minerva is taking a similar interoperability path for mixed fleets.
-
This also matters commercially. Militaries rarely buy an all new fleet in one shot. Software that can control legacy reconnaissance drones and third party munitions lets Stark sell into the installed base first, then pull customers toward its own Virtus systems over time as the control layer becomes the daily operator interface.
The market is moving toward software that sits above heterogeneous fleets and makes them act like one system. As more NATO buyers mix old airframes, new expendable drones, and specialist munitions from different vendors, the company that owns the operator screen and mission logic will have the strongest position to expand from coordination into procurement, data, and autonomy upgrades.