Uber and May Mobility announced a robotaxi partnership in May 2025. They planned to start in Arlington, Texas, by the end of that year, then expand to other US markets. May would supply hybrid Toyota Sienna vehicles, initially with onboard safety operators. Uber would offer eligible rides through its app.
The companies described an ambition to deploy thousands of vehicles over the following years. That was a plan, not a fleet order or a count of vehicles ready to serve Uber riders. May already had a separate autonomous transit service in Arlington. Its earlier work there did not mean the Uber service had launched.
The useful part of Uber’s model is the division of work. May develops and operates the driving system and vehicles. Uber brings demand, trip matching, payments, and customer support. The hard question is whether the combined service can keep vehicles busy after accounting for safety staff, remote assistance, charging, cleaning, maintenance, and empty repositioning. The partnership announcement did not publish those costs or utilization figures.
Uber also works with Waymo and other autonomous suppliers. More partners give Uber options, but each has a different operating domain, safety case, and fleet capacity. Signing suppliers is easier than integrating enough reliable vehicles into a citywide ride service.
September 2026 update: Arlington missed the original 2025 target. In a September 2026 company update, May said it was targeting commercial Uber operations in Arlington in Q4 2026 or Q1 2027. It listed commercial service with Lyft in Atlanta and two Minnesota locations, but not with Uber in Arlington. That is a material change to the launch case, and it remains a target rather than a completed launch.
May’s delay is a reminder that a multi-partner strategy can diversify Uber’s technology exposure without removing deployment risk. The next meaningful evidence is an actual Arlington launch, its driverless operating scope, and sustained paid ride volume.