When most people hear "BlackBerry," they picture the iconic smartphone that once dominated boardrooms. But today, BlackBerry's most valuable asset operates behind the scenes, embedded in the safety systems of 275 million vehicles worldwide. Meet QNX: the real-time operating system (RTOS) that controls everything from antilock brakes to advanced driver-assistance features. Even though QNX accounts for roughly half of BlackBerry's revenue, its name rarely makes headlines. For over two decades, John Wall has been with the company, watching QNX grow from a niche player to an automotive backbone. Here's everything you need to know about this unsung hero of modern driving.

What exactly is BlackBerry's QNX, and why does it matter for cars?

QNX is a certified, real-time operating system designed for safety-critical environments. Unlike a general-purpose OS like Windows or Linux, QNX prioritizes deterministic behavior—meaning it guarantees that a critical task, such as applying brakes, will finish within a specific time window. This makes it ideal for automotive systems where a split-second delay could be deadly. QNX powers not only infotainment displays but also the electronic control units (ECUs) that manage steering, braking, and engine control. Major automakers like Ford, BMW, and Toyota rely on QNX to meet the rigorous safety standard ISO 26262. In essence, QNX is the invisible guardian that ensures your car reacts correctly in an emergency, reducing the risk of software-induced accidents.

How does QNX generate half of BlackBerry's revenue?

BlackBerry's QNX division operates on a licensing and royalty model. Automakers and tier-1 suppliers pay upfront license fees for the QNX software development kit (SDK) and then pay per-unit royalties for every car that rolls off the assembly line using QNX. With over 275 million vehicles already on the road containing QNX—and millions more added each year—these royalties create a steady, recurring revenue stream. In fiscal 2022, QNX contributed roughly $200 million in revenue, representing about half of BlackBerry's total. The division also benefits from long-term contracts, as automakers tend to stick with a certified OS once they've validated it for safety. This business model gives BlackBerry a resilient anchor in the volatile tech landscape.

Who is John Wall, and what is his role at BlackBerry QNX?

John Wall is the head of BlackBerry's QNX division and a veteran of the company for nearly his entire career. He joined QNX Software Systems—then an independent firm—in the 1990s and stayed through its acquisition by BlackBerry (then RIM) in 2010. Wall now serves as Senior Vice President and General Manager of BlackBerry's IoT and QNX business. He often jokes that when he tells people where he works, they still think he means the old smartphone brand—and they have no idea about the embedded software that actually props up the company. Wall is responsible for the division's product strategy, customer relationships, and safety certifications. Under his leadership, QNX expanded from infotainment to safety-critical domains, becoming the de facto OS for automotive electronics.

Why is QNX so well-known inside the automotive industry yet virtually unknown to the general public?

QNX operates as an embedded system—it doesn't appear on any consumer label or user interface. Drivers interact with the car's dashboard or infotainment screen, but the underlying OS is invisible. Moreover, BlackBerry's public identity remains tied to its smartphone legacy, even though that hardware business ended years ago. As a result, most consumers never hear the name QNX. In contrast, industry insiders recognize QNX as the gold standard for reliability. The lack of public awareness also stems from BlackBerry's marketing strategy: it rarely promotes QNX directly to end users, focusing instead on licensing to B2B partners. This quiet success story contrasts sharply with the flashy consumer brands that dominate tech headlines.

How does QNX compete with alternatives like Linux or Android Automotive?

While Linux offers flexibility and open-source cost benefits, QNX differentiates itself through deterministic real-time performance and deep safety certifications. For safety-critical functions such as brake-by-wire or lane-keeping assist, automakers often prefer a certified microkernel RTOS like QNX because it can prove worst-case execution times. Android Automotive, on the other hand, focuses on infotainment and lacks the rigorous safety pedigree needed for mission-critical vehicle controls. Some automakers use a hybrid approach: QNX for safety domains and Android for infotainment. However, QNX has also expanded into the latter through its QNX Hypervisor, which can run multiple operating systems concurrently. In the long run, QNX's advantage lies in trust—once a safety system is certified, switching to an unproven OS is costly and risky.

What does the future hold for BlackBerry QNX in an era of software-defined vehicles?

The shift toward software-defined vehicles (SDVs) actually plays into QNX's strengths. As cars become rolling computers with over-the-air updates, the need for a secure, certified real-time OS grows. QNX is already used in prototypes for autonomous driving systems and digital cockpit domains. BlackBerry is also leveraging QNX for non-automotive uses, such as medical devices and industrial robotics, though automotive remains its core. Challenges include competition from AUTOSAR and increasing interest in open-source real-time solutions. Yet BlackBerry continues to invest in safety certifications and security enhancements, including its QNX SDP 8.0 release. With over a billion dollars in contracts pending, QNX is poised to remain a key revenue driver for BlackBerry and a silent partner in hundreds of millions of future cars.

How did John Wall end up spending his entire career at the same company?

John Wall joined QNX in the mid-1990s when it was a small Waterloo-based software company making a real-time OS for embedded devices. He started as an engineer and later moved into management. He enjoyed the technical challenges and the niche market, which allowed him to see the impact of his work. When BlackBerry acquired QNX in 2010, Wall decided to stay, partly because the new parent company shared a similar Canadian roots culture. Over the years, he turned down offers from other tech giants, preferring the stability and focus of QNX. He recounts that many outsiders don't understand his work—they still associate BlackBerry with phones—but he takes pride in the invisible safety that QNX brings to millions of vehicles. For Wall, QNX isn't just a job; it's a mission to keep people safe through reliable software.