Source: TechCrunch / Forterra, July 7, 2026 — Original article
Forterra's Lancer autonomous ground vehicles have spent nine months in real combat deployment in Ukraine — not a demo video, but publicly verifiable deployment data: 100+ vehicles, 1,100+ missions, 2,500 miles driven, 777,440 pounds of supplies transported, and 52 casualty evacuations.
Key details worth noting
1. The vehicles are primarily teleoperated — not "autonomous to destination." 2. As Forterra's founding growth officer Scott Sanders put it: "You don't know until you hit the reality of combat."
The battlefield is not a demo hall
Lancer is based on a Polaris ATV, fitted with Forterra's own sensor and compute stack. It is gasoline-powered and carries 750 kg of cargo — compared with Ukrainian-made UGVs that are battery-driven with a 250 kg max payload. Ukrainian soldiers' reviews were blunt: "This thing is the most important UGV in Ukraine — awesome, we all want more."
But the battlefield is real: several Lancers are permanently stuck in deep mud, where vehicles get immobilized and methodically hit by Russian forces. Starlink antennas were retrofitted later — an important detail: the original product didn't account for Ukraine's need for Starlink. This was localization, not getting it right at the research stage.
The deployment is funded through US defense budgets — the standard playbook of "using the Ukraine war to feed back into US military transformation." Drones have made the battlefield a "no-go zone everywhere": with FPV drones watching from above, any exposed person is a target. Sergeant Major Corey Wilkens said it directly: "You have nowhere to hide, you're very easily attacked."
"Autonomous" isn't that autonomous
Forterra itself says the vehicles are currently mainly teleoperated. Why? The vehicles can navigate diverse terrain autonomously, but cannot yet identify unexpected enemy threats on the battlefield and react in real time. As one Ukrainian soldier put it: "It needs to react in real time under enemy fire — current autonomy can't do that."
This is the real state of embodied AI today: terrain navigation is ~70% solved, threat identification is essentially unsolved. An autonomous car avoiding an illegally parked vehicle and identifying an unfamiliar enemy squad camouflaged in bushes are two different difficulty levels — even frontier models lack the reaction speed and judgment reliability for the latter.
Forterra's approach after 20 years in autonomous vehicles: a hybrid using classical robotics for vehicle control and path planning, with generative AI interpreting the surroundings — a consensus recipe in the embodied AI world, but never validated on a battlefield.
What the numbers actually mean
- 100+ deployed: not "a few prototypes" — catalog-level product quantity
- 9 months: normalized operations, not a three-month showcase
- 2,500 miles, 1,100+ missions: roughly 2.27 miles round-trip per mission — logistics supply distances
- 777,440 pounds: ~353 tons, close to 18 fully loaded trucks
- 52 casualty evacuations: more than one per week on average — the most important number: directly life-saving applications
- $500 million: Forterra's cumulative funding (YZ Venture Capital, Moore Strategic Partners, etc.)
- Teleoperation-first means "autonomy" is currently semiautonomous; without reliable threat identification within two years, these products remain "camera-equipped RC cars."
- Both Russian and Ukrainian forces are developing counter-UGV methods; vehicles with Starlink antennas present an obvious electronic warfare vulnerability.
- Battlefield learning data is vast but inaccessible — Ukraine won't release combat video as training data, closing the "train on real combat" loop and leaving simulation plus limited field testing, the old problem of simulated-trained models lagging behind RLHF-trained ones.
"Lost in combat" is an inevitable part of this. Ukrainian forces say they need a cheaper version — expensive vehicles won't be pushed forward aggressively.
The competitive landscape
Scout AI raised $100 million in April to "train foundation models for war," including ground unmanned platforms. Field AI and Overland AI are also testing UGVs with the US military. At least four US companies have pushed autonomous ground vehicles to battlefield-testable status — a density signaling that VC and DoD both believe this is commercializable.
The AI coding connection
Lancer's hardware stack uses general software engineering toolchains — remote updates and remote diagnostics, essentially the OTA paradigm for software products. Forterra emphasizes "toolchain reliability," which is not fundamentally different from SRE work.
The demand for AI coding engineers at such companies may grow the way SaaS vendors demanded engineers. Next-generation "AI-native defense" hires Python, ML, and AI Safety engineers rather than mechanical/control engineers. This talent flow — and the potential customer base for AI coding tools — may lie not in large internet companies but in defense tech, AI pharma, and AI for science: fields combining software products with hardware deployment.
Limitations and open questions
Why this matters
Embodied AI has been "demo better than product" for years. Forterra's numbers are the first set of follow-up-question-worthy figures from genuinely dangerous physical environments — this data scarcity itself is news. The bet: another US defense tech company publishes similar combat data within three months. Longer term: this is AI's first credible "accident rate" statistics in the physical world, not just a "it runs" demo. The next story is whether those rates can be driven down to human-acceptable levels.