The Software Breakthrough Automakers Have Been Eagerly Awaiting Could Be Here
QNX and Vector’s collaboration promises to streamline the complex and costly software foundations underpinning the next generation of vehicles.
By Tim Stevens
Writer
Ryan Lugo
Illustration By Manufacturer
Photographer
Motor Trend Archive
Photographer
December 12, 2025
We are currently navigating one of the most transformative periods in automotive history. This transformation is not solely driven by the shift to electrification, which continues to present its own set of challenges, but rather by the rapid embrace of the software-defined vehicle, or SDV.
While the concept might sound straightforward—a transition from discrete hardware components to over-the-air (OTA) updatable algorithms—it has evolved into a persistent source of frustration for many of the industry’s leading automakers. The escalating demands for increasingly sophisticated features must now be delivered through a convoluted framework of regulations and requirements. This complex interplay has created a nearly untenable situation, one that could potentially lead to future vehicles offering fewer features rather than more.
Fortunately, a potential solution is beginning to emerge. The hardware virtualization experts at QNX and the middleware specialists at Vector have joined forces to create what they are calling the Foundational Vehicle Software Platform. Should this platform deliver on its promises, it could effectively eliminate many of the most intricate and challenging aspects of automotive software development.
The Shift Toward Software-Defined Vehicles
The term software-defined vehicle is not entirely new. However, as this foundational concept has moved to the forefront of vehicle design, its meaning has undergone a process of evolution.
“It’s a term that’s been around for about seven or eight years,” stated 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 fact that the vehicle is becoming increasingly reliant on software for its features.”
In some automotive organizations, the transition to SDVs has been promoted as a potential panacea for various development challenges, promising a significant reduction in hardware complexity and a simplified overall architecture, all while establishing a platform that allows vehicles to maintain their relevance in the market for extended periods.
“I think one of the primary drivers behind the SDV movement in traditional automotive companies is the ability to continuously enhance the vehicle over time, introduce new features, and potentially monetize these new functionalities within the vehicle,” Wall elaborated.
However, beneath these promising aspirations lies a concerning reality that has led to significant upheaval within the software divisions of some manufacturers.
The Organizational Overhaul That Automakers Didn’t Anticipate
Achieving advanced software capabilities requires more than just sophisticated code. For certain traditional automakers, it necessitates a complete organizational reboot.
“At the moment, they are struggling, especially with their development processes,” noted Matthias Traub, a member of the board of directors and CTO at Vector. “This struggle extends to the cultural perspective as well. They are transitioning from a traditional waterfall-based development process with clearly defined roles.”
The waterfall approach is a legacy software development methodology characterized by its sequential nature, where progress flows downward through distinct phases such as requirements, design, implementation, and testing. This linear model proves ill-suited for the increasingly dynamic landscape of automotive software development.
“Now, the imperative is to move towards a genuine DevOps approach,” Traub continued. “This involves smaller teams that assume responsibility for the entire development chain, encompassing design, building, software development, testing, and so forth.”
QNX’s Wall highlighted another common misconception among many companies: the belief that they must develop every line of code in-house. “I think that’s where many of them have faltered,” he observed.
The drive to control the entire software stack compels developers to write code for extremely fundamental functions, such as securely transmitting data over the vehicle’s integrated modem or rendering pixels on the car’s displays. Companies whose core competency is building vehicles 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 enhance the customer experience, not on operating systems and networking stacks,” Wall asserted.
If the ever-growing complexity of the software stack were not concerning enough, the sheer breadth of modern automotive software regulatory frameworks presents a formidable challenge. The list of requirements that developers must navigate continues to expand.
“You have elements like the software bill of materials, understanding the provenance of your software, and considerations related to U.S. regulations, such as restrictions on Chinese code,” Wall elaborated. “There are numerous factors to consider. It’s a truly dynamic situation.”
The Emergence of a New Platform
Evolving regulations not only impose shifting targets for initial compliance but also necessitate ongoing efforts in terms of updatability and vulnerability response.
“The industry is reaching a tipping point where software complexity threatens to outpace innovation,” Traub warned. He expressed concern that if this trend persists, next-generation vehicles might actually feature fewer capabilities than those currently on the road.
Complex regulatory environments are precisely the kind of challenges QNX has repeatedly addressed in the past. The company’s foundational operating system is utilized in a diverse range of applications, from nuclear power plants to military aircraft.
“Many of the security requirements originated from the medical field, and we encountered them somewhat earlier, influenced by the Biden administration’s initiatives,” Wall noted.
The Foundational Vehicle Software Platform is built upon this extensive expertise. It represents a cohesive set of interfaces and tools developed by QNX and Vector, designed to streamline modern automotive software development. The platform leverages the long-standing capabilities of both companies in abstracting and simplifying the intricate aspects of integrated system development. In the automotive context, this translates to providing secure, reliable, and certifiable hardware integration.
“We are endeavoring to eliminate many of these difficult issues by consolidating them and offering a single source of truth for the platform,” Wall explained.
QNX and Vector have collaborated on various projects for years, but their close partnership on the new platform has spanned the last 18 months. Although still an evolving and ongoing initiative, it is already demonstrating considerable promise, not only in terms of simplification but also in performance metrics.
Traub reported that solutions running on the platform have achieved up to a 50 percent reduction in CPU load compared to custom-written code. Latency, defined as the delay between a system request and its response, was reduced by 85 percent, and overall data transmission rates more than doubled.
“And we are just at the beginning,” Traub remarked. “Eighteen months is not a very long time, and I am confident that we will achieve even greater performance enhancements in the future.”
When software operates more efficiently, it can run faster on less complex hardware, potentially leading to reduced vehicle manufacturing costs.
A Promising Path Forward, Despite Its Nascent Stage
The Foundational Vehicle Software Platform from QNX and Vector is still in a developmental phase. However, by addressing many of the contemporary pain points in the software industry, it is already gaining significant traction.
“It’s truly remarkable to observe the number of companies inquiring about our solution,” Traub commented. “Previously, we had only a handful of names on our list. Now, that number has grown to two handfuls or more.”
The diverse clientele of these companies ensures that the platform is being developed to meet a wide array of requirements.
“Because Vector and QNX work with so many customers—virtually every customer worldwide—we gain valuable insight into the industry roadmap,” Wall noted. “We develop a clear understanding of what the car manufacturers need.”
Regarding the timeline for seeing these new products on the road, the timeframe may be closer than initially anticipated. “If you had asked me at the start of this project, I would have estimated 2029 or 2030,” Wall said. “However, we’ve seen recent acceleration, so I believe it could be sooner than that.”
