Resilient Distributed Autonomy for Vehicles
Scott Sanders, Chief Growth Officer at Forterra, on autonomy for every vehicle
This reveals that Forterra is not just building a self driving vehicle, it is building a battlefield computer that can keep working after networks break. In practice that means each vehicle has to sense, decide, and keep moving locally, instead of waiting for instructions from a remote control room. That same design shows up in Forterra’s commercial yard products, where vehicles also operate on weak or inconsistent networks and still need to move freight safely.
-
Forterra describes an autonomous ground vehicle as a fully integrated computer system at the edge, with onboard sensor fusion, communications, positioning, and maintenance logic. The hard part is not only driving, it is packaging all of that compute into hardware that survives shock, vibration, and field conditions on real vehicles.
-
This architecture also explains Forterra’s dual use path. In defense, a convoy vehicle may lose infrastructure because an enemy jams or destroys it. In a container yard, a terminal tractor still has to coordinate trailer moves even when site connectivity is weak. Both markets reward autonomy that can run locally and fail gracefully.
-
The closest large scale comparison is Anduril, which is also pushing resilient autonomy and mesh networking across distributed systems. The competitive line is moving away from a single command brain and toward platforms that let many assets share data when available, but still complete missions when communications and GPS are denied.
The next phase of defense autonomy will favor companies that can turn vehicles, drones, and sensors into self sufficient nodes instead of thin clients. That shifts value toward full stack players that own onboard compute, vehicle integration, and the software layer that lets fleets collaborate without depending on perfect connectivity.