Baidu and BlackBerry announce partnership on autonomous car initiatives, including using BlackBerry's QNX OS in Baidu's Apollo self-driving vehicle platform
Context & Ripple Effects
Baidu has been assembling Apollo as a federation rather than a proprietary stack: the 50-plus-partner alliance of mid-2017 brought in Ford, Bosch, Nvidia and Microsoft Cloud, and the 2016 Nvidia collaboration supplied the AI compute layer. This BlackBerry deal fills the layer below those — the safety-certified operating system that production vehicles actually run on.
For BlackBerry, whose handset business collapsed years ago, QNX licensing is the core of its reinvention as an embedded-software vendor; plugging into Apollo gives it a route into China's self-driving market at scale. Days after this announcement, Baidu followed with the Apollo 2.0 release and Southeast Asia expansion, showing the partner cadence was accelerating.
First-order effects
- Baidu gains a production-grade, safety-certified automotive OS for Apollo without building one in-house, letting it focus development on the autonomy software above the OS layer.
- BlackBerry converts QNX from a legacy infotainment license base into a position inside one of the largest autonomous-driving ecosystems, with Apollo's 100-plus partners as prospective customers.
Second-order effects
- Apollo's existing silicon and cloud partners — Nvidia, Bosch, Microsoft Cloud — now sit atop a BlackBerry-supplied OS, hardening the layered division of labor that makes joining Apollo cheaper than building a full stack alone.
- Rival autonomy platforms must match the certified-OS component: Baidu's subsequent Mobileye partnership shows it multi-sourcing perception too, pressuring competitors to assemble equivalent partner rosters.
Third-order effects
- If the pattern holds, autonomous driving consolidates around open platforms with specialist suppliers per layer — chips, OS, cloud, fleet management (later formalized in Apollo Enterprise) — squeezing out players who insist on owning every layer.
- Legacy tech firms like BlackBerry survive by becoming certified component vendors inside such platforms, a structural template for other post-hardware companies.
The trend: Autonomous-vehicle development is shifting from vertically integrated in-house stacks to federated open platforms, with legacy technology firms repositioning as certified suppliers of individual layers.