The Software Solution Automakers Have Long Anticipated May Finally Be Here
In a move that could reshape the future of automotive development, QNX and Vector have announced a groundbreaking collaboration aimed at simplifying the complex, costly software foundations powering the next generation of vehicles.
By Tim Stevens, Writer
Illustrated by Ryan Lugo
Photography by Manufacturer & Motor Trend Archive
Published December 12, 2025
We stand at one of the most transformative junctures in automotive history. While the shift toward electrification certainly commands attention, the seismic change underway is the rapid evolution toward the software-defined vehicle (SDV).
What sounds like a straightforward transition from discrete hardware components to over-the-air (OTA) updatable algorithms has morphed into a persistent source of frustration for many of the industry’s leading automakers. The escalating demand for ever-evolving functionality clashes with a tangled web of regulations and requirements, creating a nearly untenable situation that could paradoxically lead to future vehicles offering fewer features, not more.
ADVERTISEMENT – CONTINUE READING BELOW
Fortunately, a potential solution is emerging. Hardware virtualization experts at QNX and middleware maestros at Vector have joined forces to introduce what they term the Foundational Vehicle Software Platform. If this platform lives up to its promises, it could eradicate many of the most intricate and challenging aspects of automotive software development.
The Pivot to the Software-Defined Vehicle
The concept of the software-defined vehicle is not entirely novel. However, as this low-level concept has moved to the forefront of vehicle design, its definition has undergone a significant transformation.
ADVERTISEMENT – CONTINUE READING BELOW
“It’s a term that has been around for about seven or eight years,” notes John Wall, President of QNX. “I believe that in the last few years, it has come to signify something very specific. For me, it really underscores the increasing dependence of the vehicle on software for its features.”
In certain organizations, the transition to SDVs has been heralded as a panacea for an organization’s challenges, promising a dramatic reduction and simplification of in-vehicle hardware while simultaneously providing a platform that keeps vehicles relevant in the market for longer durations.
ADVERTISEMENT – CONTINUE READING BELOW
“I think a primary driver of SDV in traditional automotive companies is the ability to continually enhance the vehicle over time, introduce new features, and potentially monetize those new features within the vehicle,” Wall explains.
However, beneath these lofty promises lies a troubling reality that has left the software divisions of some manufacturers in disarray.
The Organizational Overhaul Automakers Didn’t Foresee
Achieving new heights in software capability requires more than just advanced code. For some legacy automakers, it necessitates a complete organizational reset.
“Currently, they are struggling, particularly with their development processes,” states Matthias Traub, a member of the board of directors and CTO at Vector. “This also applies to the cultural perspective. They are transitioning from a traditional waterfall-based process with clearly defined roles.”
The waterfall approach is a legacy software development methodology characterized by projects with distinct tasks, roles, and deadlines. This model proves inadequate in the increasingly dynamic automotive software landscape.
“Now, the imperative is to move toward a genuine DevOps approach,” Traub continues. “This involves smaller teams assuming responsibility for the entire lifecycle, encompassing design, build, software development, testing, and so on.”
sdv
QNX’s Wall also points to a flawed belief among many companies that they must develop every line of code in-house. “I think this is where many of them have faltered,” he admits.
Feeling compelled to own the entire software stack forces developers to write code for even the most rudimentary functions, such as securely transmitting data over the car’s built-in modem or rendering pixels on the vehicle’s displays. Companies whose core competency lies in building cars have instead found themselves developing layer upon layer of software that customers will never directly interact with.
“Their energy should be concentrated on features that delight their customers, not on operating systems and networking stacks,” Wall asserts.
Beyond the challenge of a rapidly ascending software stack, the sheer breadth of modern software regulatory frameworks presents a formidable hurdle. The checklist of considerations for developers grows ever longer.
“You have elements like the software bill of materials, the provenance of your software, what’s happening in the U.S., concerns about Chinese code,” Wall elaborates. “There are numerous factors to contemplate. It’s a highly dynamic situation.”
A New Platform Emerges
Evolving regulations not only impose shifting targets for initial compliance but also necessitate ongoing updatability and responsiveness to vulnerabilities.
“The industry is at a tipping point where software complexity threatens to outpace innovation,” Traub warns. He expresses concern that if this trend persists, the next generation of vehicles may actually offer fewer features than those currently on the road.
Complex regulatory environments are an area where QNX has repeatedly drawn upon its extensive experience. The company’s foundational operating system is deployed in diverse applications, ranging from nuclear power plants to military aircraft.
SDV Award main image
“Many of the security requirements originated from the medical field, and we encountered them slightly earlier, influenced by the Biden administration’s directives,” Wall recalls.
ADVERTISEMENT – CONTINUE READING BELOW
The Foundational Vehicle Software Platform is built upon this deep reservoir of expertise. It comprises a suite of interfaces and tools from QNX and Vector designed to streamline modern automotive software development. This platform leverages the extensive history of both companies in abstracting and simplifying the complexities inherent in integrated systems development. In the automotive context, this translates to providing secure, reliable, and certifiable hardware integration.
“We are endeavoring to eliminate many of these difficult aspects by consolidating them and offering a single source of truth for the platform,” Wall states.
QNX and Vector have collaborated on various projects for years, but their close partnership on the new platform has spanned the last 18 months. While still an evolving and ongoing initiative, it is already demonstrating considerable promise in terms of both simplification and performance.
Traub reports that solutions operating on the platform have achieved up to a 50 percent reduction in CPU load compared to custom-developed code. Latency—the delay between a system request and the corresponding response—was reduced by 85 percent, and overall data transmission rates more than doubled.
“And we are only at the beginning,” Traub emphasizes. “Eighteen months is a relatively short period, and I am confident that we will unlock significantly more acceleration potential.”
By optimizing software performance, vehicles can operate more efficiently on simpler hardware, potentially leading to reduced manufacturing costs.
ADVERTISEMENT – CONTINUE READING BELOW
Mercedes Benz Vision AVTR Concept 47
A Promising Trajectory, Albeit Early Days
Although the Foundational Vehicle Software Platform from QNX and Vector is still in its developmental stages, its targeted approach to addressing the key pain points of the modern software industry is already gaining traction.
“It’s truly remarkable to observe the number of companies inquiring about our solution,” Traub notes. “Previously, our list comprised only a handful of names. Now, it extends to two handfuls or more.”
The extensive client base of the two companies ensures that the platform will be refined to meet diverse requirements.
“Because Vector and QNX serve such a broad spectrum of customers worldwide, we gain valuable insight into roadmaps,” Wall explains. “We develop a clear understanding of what the automakers require.”
As for when these resulting products will debut on the roads, the timeline may be closer than anticipated. “If you had asked me at the inception of this project, I would have predicted 2029 or 2030,” Wall shares. “However, we have witnessed an acceleration of progress recently, so I believe it could occur sooner than that.”
