BlackBerry announces Jarvis, a tool for automakers that scans connected car software for security flaws; may be used later in healthcare, industrial automation
Context & Ripple Effects
Jarvis lands mid-arc in BlackBerry's retreat from devices into embedded software: two years earlier the company committed $75M to an Ottawa autonomous vehicle testing hub around QNX, and three years later it would extend that footprint with the AWS partnership to co-develop the IVY vehicle data platform. Jarvis adds a security-scanning layer on top of the same automotive installed base.
What makes it durable is that QNX's reach extends well past cars — the [[a:969731|critical QNX flaw later disclosed to affect more than 200 million cars plus hospital equipment]] showed both the scale of that footprint and why automated flaw-hunting matters to BlackBerry's credibility as its steward.
First-order effects
- Automakers building connected-car software on or alongside QNX gain an automated vulnerability scan during development, giving BlackBerry a new revenue line attached to its existing OS relationships rather than handset sales.
Second-order effects
- Rivals in automotive cybersecurity tooling face pressure to bundle scanning with their own embedded offerings, while suppliers of medical and industrial devices — where BlackBerry says Jarvis may next apply — become a second customer pool for the same tooling.
Third-order effects
- If the pattern holds, embedded-OS vendors evolve from license sellers into security-and-analytics platforms layered over their installed base — the trajectory that culminates years later in QNX being positioned as an operating system for robots, with the stock re-rating on that software story.
The trend: BlackBerry is converting its QNX installed base from licensed embedded software into a recurring security and data platform spanning vehicles, healthcare, and industrial automation.