Uber Sells Its Entire Stake in Serve Robotics, Ending a Five-Year Autonomous Delivery Partnership

Uber sold its entire stake in Serve Robotics during the second quarter of 2026, disclosing the divestiture in a regulatory filing first reported by Bloomberg on August 11. The sale caught Serve Robotics itself off guard; the company learned of Uber's complete exit once it was officially disclosed, according to a source familiar with the events (TechCrunch).
The exit caps a wind-down that had been underway for over a year. Regulatory filings show Uber reduced its Serve stake during 2025 before completing the selloff in Q2 2026 (TechCrunch).
How the Two Companies Got Here
Serve Robotics traces back to Postmates X, the robotics division of Postmates, which Uber acquired in 2020 for $2.65 billion. Uber spun out the robotics unit as an independent company, Serve Robotics, in March 2021, initially planning to retain roughly 25% of the new entity. By the time Serve hit public markets on April 18, 2024, with a $40 million funding round backed by Uber and Nvidia, Uber held a 16.6% stake and Nvidia 14.3%. An April 2024 regulatory filing indicated Uber's position would drop to about 11% (TechCrunch).
The partnership between the two companies expanded notably in May 2023, when they agreed to deploy up to 2,000 sidewalk delivery robots onto Uber's app across multiple U.S. markets. That followed an earlier pilot launched in May 2022, when Uber Eats tested autonomous delivery with Serve Robotics and Motional. Serve had raised a $13 million seed round in December 2021 to scale its sidewalk delivery operations (TechCrunch).
Operational Friction
The operational relationship began fraying in measurable ways. On Serve's August 6, 2026 second-quarter earnings call, co-founder and CEO Ali Kashani disclosed that delivery volume through Uber had grown for 17 consecutive quarters from Q1 2022 through Q1 2026, before reversing in Q2 due to lower-than-expected robot utilization. Kashani also said the two companies hold "differing views about the operating model to scale their shared autonomous fleet, including fleet coordination and merchant integration." Serve subsequently stated it does not expect to renew its partnership agreement with Uber when it expires in early 2027 (TechCrunch).
Serve is one of more than 30 autonomous vehicle technology companies Uber has either partnered with or invested in over the past several years, making this exit a data point within a much broader portfolio strategy. Uber's approach to autonomous delivery and mobility has been consistently capital-light: partner broadly, take minority stakes, and let the underlying companies bear the cost and risk of hardware development and fleet operations. The Serve divestiture fits a pattern Uber has followed elsewhere. In 2020, the company offloaded its shared scooter and bike unit, Jump, in a complex deal with Lime rather than continuing to operate micromobility hardware directly.
What the Utilization Data Signals
The 17-quarter growth streak followed by a Q2 reversal in delivery volume is the operational signal worth scrutinizing. Sustained quarter-over-quarter growth across more than four years suggests the integration between Serve's robots and Uber's marketplace was functioning at a meaningful level; the reversal indicates that something structural changed, not merely a seasonal dip. Lower-than-expected robot utilization points to the core economics of sidewalk delivery: each unit must generate enough completed deliveries per active hour to cover depreciation, maintenance, remote monitoring, and dispatch overhead. If utilization drops below that threshold, scaling the fleet further erodes unit economics rather than improving them.
The disagreement over fleet coordination and merchant integration is, in this context, more telling than a simple contractual dispute. Fleet coordination touches dispatch logic, routing, and how robots interact with Uber's broader delivery marketplace, where human couriers, car-based delivery, and autonomous vehicles compete for the same order flow. Merchant integration involves how orders are handed off at the restaurant or store end, a workflow that was designed for human couriers and requires adaptation for a robot that cannot walk inside, navigate a counter, or confirm pickup verbally. Reconciling these two stacks is not a partnership negotiation problem; it is an integration architecture problem, and differing views on how to solve it suggest the companies were never aligned on the technical roadmap needed to reach 2,000 deployed units.
The fact that Serve learned of the final selloff through disclosure rather than direct communication is itself worth noting. For a partner of five-plus years with an active commercial agreement running through early 2027, the absence of advance notice suggests Uber treated the stake purely as a financial position to be managed, not as a strategic relationship requiring coordinated exit. That is consistent with Uber's broader portfolio approach but inconsistent with the public framing of a deep partnership.
Serve now faces the prospect of operating without its primary distribution channel. The company has Nvidia's backing and its own direct relationships, but the Uber app provided demand aggregation at a scale that sidewalk delivery companies struggle to replicate independently. The runway to early 2027, when the partnership agreement expires, gives Serve time to build alternative channels, but the utilization problem that triggered the volume reversal will need to be solved regardless of which marketplace dispatches the robots.
For Uber, the exit is consistent with a strategy of maintaining optionality across the autonomous delivery and mobility landscape without tying outcomes to any single partner. With 30-plus AV relationships in flight, the company can afford to let individual bets run their course. Whether sidewalk delivery specifically matures into a viable at-scale category, or settles into a niche serving dense urban corridors and campus environments, is an open question that neither this divestiture nor the utilization data alone can answer.


