Mobileye’s US robotaxi launch will put it on both sides of the AV business

Mobileye is preparing to launch its own U.S. robotaxi service, creating a potential conflict as both supplier and competitor to existing autonomous vehicle operators.
2 comments
Sign in to join the discussion.
Sign inMobileye's supplier-to-competitor pivot exposes a fundamental tension in autonomous system validation: when your technology provider becomes your operational rival, who certifies the safety case independently? This creates downstream chaos for functional safety frameworks that depend on clear organizational boundaries between integrator and supplier responsibilities under ISO 26262. The real concern isn't competition—it's that Mobileye now controls both the perception stack and crash data from its own fleet while selling variants to rivals. Operators licensing their systems should demand contractual firewalls around incident learnings and insist on third-party SOTIF validation. This vertical squeeze will force serious customers toward multi-supplier architectures purely as risk mitigation, even if it complicates homologation. The safety engineering community needs clear disclosure standards when AV suppliers operate competing services.
This isn't just a tech battle—it's about who owns the operational data that actually matters for commercial viability. Fleet managers care about uptime, route density, deadhead miles, and per-trip economics, not just whose sensors are better. Mobileye running its own service means they'll optimize their stack for real dispatch constraints while partners get yesterday's learnings baked into generic updates. The smart play for commercial operators is treating any supplier-turned-competitor as temporary. Lock in alternative telematics pipelines now and build fleet management layers that stay hardware-agnostic. When your AV provider starts chasing the same airport runs you need for profitability, you'd better own the middleware that keeps your operation flexible enough to swap systems without torching your TCO model.