Uber and GM's Cruise open source their self-driving car visualization software, a rare move in the hyper-competitive autonomous world
Why the U.S. Effort to Crush Huawei Isn't Working Duncan Riley / SiliconANGLE : Uber and Cruise open-source their visualization software Uber Engineering Blog : Introducing AVS, an Open Standard for Autonomous Vehicle Visualization from Uber Jacob Bandes-Storch / Cruise : Introducing Worldview — At Cruise Automation, hundreds … Amir Efrati / The Information : The 250 ‘Cruisers’ Who Power GM's Self-Driving Car Unit Kyle Wiggers / VentureBeat : Uber open-sources Autonomous Visualization System, a web-based platform for vehicle data
Context & Ripple Effects
Uber arrives at this release with prior form: back in 2017 it opened up its data visualization tool beyond mapping into network traffic and other datasets, so AVS extends an existing open-source habit rather than starting one. What makes the move notable is who joined in: Cruise, GM's self-driving unit already operating an employee ride-hailing service in San Francisco, shipped its own Worldview viewer alongside Uber's AVS.
The gesture cuts against the grain of a field where even base layers are contested — Bloomberg's reporting on the mapping fight among Google, GM, and Uber shows companies actively working to stop any single rival dominating spatial data. Giving away the lens you inspect your fleet through is a bet that the defensible value sits in the driving stack, not the dashboard. Cruise then doubled down months later by open-sourcing Webviz for robotics data analysis, suggesting the tooling-commons approach wasn't a one-off.
First-order effects
- Engineers at Uber and Cruise — and any team adopting the formats — get shared, web-based tooling for reviewing what their vehicles see, replacing duplicated in-house viewer work at both companies.
- By releasing AVS and Worldview, both firms effectively declare visualization non-core: their competitive effort concentrates on the perception and planning stacks instead.
Second-order effects
- Smaller AV and robotics teams can adopt AVS as a de facto inspection standard, cutting their tooling costs and pressuring better-resourced rivals — including Google, still fighting for position in mapping — to contribute to the commons or accept fragmentation.
- A common viewing format makes logs and engineering know-how more portable across AV companies, eroding one more lock-in point in a market where firms otherwise guard their data jealously.
Third-order effects
- If the pattern holds, the industry settles into a split structure: open tooling and formats underneath, fiercely proprietary autonomy stacks on top — the same boundary being drawn in mapping, where no player wants a competitor owning the base layer.
- Commoditized review tooling lowers the entry cost for new entrants, widening the field beyond the handful of heavily funded programs and shifting differentiation entirely into the driving software itself.
The trend: Self-driving developers are open-sourcing the observation and tooling layer around their vehicles while keeping the autonomy stacks themselves closed.