Minerva as Battlefield Operating System

This reveals the real wedge is not selling more drones, it is becoming the software layer that sits above whatever drones, radars, and sensors a military already owns. Minerva matters because it can run on a tablet, laptop, vehicle server, or cloud stack, stay usable offline, and talk to third party systems through STANAG 4586 and MAVLink, which turns mixed fleets into one controllable network instead of a pile of disconnected tools.

• The closest comparison is Lattice because the pattern is the same, start with command and control software, then use that software as the control point for more hardware. Anduril describes Lattice as powering autonomous systems across land, sea, and air, and past research shows it uses that software to pull through towers, drones, and other systems.
  2 sacra 4 anduril 5 sacra
• Vendor agnostic is strategically important because militaries rarely replace fleets all at once. Minerva can already control legacy reconnaissance drones, artillery radars, and third party loitering munitions, so Stark can sell into an existing force structure instead of asking a buyer to rip out current vendors before getting value.
  1 sacra
• The business model shifts from one time kit sales toward recurring licenses with better economics. A similar playbook is emerging across defense autonomy, with software platforms like Quantum Systems' Mosaic licensed annually to orchestrate any vendor's drones, because software can carry 60%+ gross margins versus roughly 30 to 40% for hardware.
  6 sacra 7 sacra

The next step is for defense drone companies to split into hardware vendors and operating systems. If Minerva keeps winning mixed fleet deployments, Stark can become the control layer European militaries standardize on, which would make each new drone, sensor, or autonomy module added by a customer increase Stark's software revenue without requiring Stark to manufacture all of it.