Blackberry Vector Alloy Kore Solution? Volkswagen Horizon Robotics China JV vs Rivian US JV
youtu.be/C-BpuneLTCY
Hypothesis about a convergence point via Alloy Kore (the QNX Vector joint platform)
Rivian OS 2.0 on the R2 platform might be the catalyst, and how Volkswagen could eventually bridge its fractured global strategy.
1. What Alloy Kore Actually Solves
When QNX and Vector unveiled Alloy Kore at CES 2026, it was designed specifically to end what the industry calls "Siftware"—the fragmented, fragile process of manually layering middleware on top of an OS.
Historically, an OEM would license the QNX OS/Hypervisor for safety, and then spend millions paying Vector (or Elektrobit) to integrate the AUTOSAR middleware stack (which handles vehicle network communications like SOME/IP, diagnostics, and secure routing).
Alloy Kore pre-integrates these two layers out of the box, fully safety-certified up to ASIL D. It provides a clean, standardized, horizontal "plumbing" layer.
The Strategic Value: It allows an automaker to treat the foundational OS and vehicle network as a solved commodity. They can focus 100% of their engineering resources on the Application Layer (the UI, the cloud features, and the autonomy stack) where they actually compete.
2. Rivian OS 2.0 & The R2 Launch: The Logical Pivot
You are spot-on to look at the upcoming R2 and Rivian’s next-gen software architecture as a candidate for this type of stack.
When Rivian launched the Gen 2 R1, they proved they could successfully consolidate their hardware into three massive zonal domain computers. However, as you’ve experienced firsthand, managing that consolidated, mixed-criticality hardware with custom-stitched software introduces massive timing and message-routing bugs.
For the R2 platform, Rivian faces a completely different challenge: Mass Scalability and Cost Reduction.
To build the R2 at a lower price point and scale it globally (including inside millions of future Volkswagen Group vehicles), Rivian cannot afford to spend thousands of engineering hours manually fixing custom software routing bugs.
Moving to a highly optimized, pre-certified foundation like Alloy Kore would make immense sense for Rivian OS 2.0. It keeps Rivian’s beautiful proprietary UI (Android/Linux-based) and their custom autonomy stack on top, but swaps out the messy, homemade "plumbing" underneath for a rock-solid, resource-efficient QNX/Vector foundation.
It drops CPU overhead, slashes latency, and ensures that a bug in an infotainment update can't accidentally starve a critical safety loop of processing power.