OEM Integration vs In-House Vehicles

This is a packaging battle as much as an autonomy battle. Forterra is set up to drop its autonomy stack into vehicles a military or industrial customer already buys from established manufacturers, which matters when a unit runs a patchwork fleet and wants one supplier to automate several vehicle types. Overland can move faster on product design because it controls the whole machine, from autonomy software to retrofit kit to purpose built vehicles like ULTRA and IBEX.1 2 3 4 5 6

• Forterra's route into mixed fleets comes from OEM channels and integration work. Its commercial partnership with Kalmar puts Forterra autonomy into terminal tractors that Kalmar sells and supports through its own network, and Forterra has also publicized defense integrations with major vehicle makers like BAE Systems.1 2 7 8
• Overland's advantage is tighter hardware and software co design. Its SPARK kit retrofits existing vehicles, but the company also sells complete robotic vehicles, which lets it decide sensor placement, compute, power, operator interface, and chassis layout as one system instead of adapting to an OEM's existing design.4 5 9
• That creates two different operational promises. Forterra can appeal to programs that need autonomy across a fleet of trucks, tractors, or military platforms already in service. Overland can appeal when the buyer wants a finished robotic vehicle that is ready to field with fewer integration dependencies and a more uniform support burden.3 4 5 6 9

Going forward, the winners will be the suppliers that turn demos into repeatable fielding. Forterra is pushing toward a model where autonomy becomes an option on many partner vehicles. Overland is pushing toward a model where the robot and the autonomy arrive as one product. Defense buyers are likely to use both patterns, depending on whether the mission starts with an existing fleet or a new platform.2 3 4 5 6 9