Integrated Autonomy Kits Across Vehicles

This view points to a winner take most market structure, because the company that controls the vehicle kit, the sensors, the onboard compute, and the autonomy software can make the whole system work reliably in rough real world conditions, then reuse that same core stack across defense and commercial vehicles. At Forterra, that means one autonomy kit can move from missile launchers to yard trucks without rebuilding the product from scratch.

• In practice, integration matters because autonomy fails at the seams. Forterra describes ground autonomy as an edge computer system on the vehicle, tied to sensor fusion, communications, maintenance, safety, and production logistics. That is why hardware is not just a customer acquisition wedge, it is part of the product itself.
  1 sacra
• The comparable model is Anduril, where a core software and sensing base was turned into multiple hardware products. The underlying pattern is to spend heavily upfront on a product, then sell fixed price systems instead of billing engineering hours, which creates more repeatable deployment and better margins than services style defense contracting.
  2 sacra 3 sacra
• Drone companies show the same split. Skydio pairs upfront hardware sales with recurring software, because customers need the aircraft, the control stack, and the workflow software to fit together. Pure software layers can exist, like DroneDeploy, but they capture value after the vehicle is already in the field, not at the point where autonomy performance is won or lost.
  4 sacra

Going forward, more robotics markets should consolidate around companies that own the full deployment stack and can ship complete systems at scale. The advantage will go to teams that can turn integrated products into standard kits, then spread them across adjacent vehicle categories faster than software only or hardware only rivals can catch up.