The Software Fix Automakers Have Been Waiting For Might Be Here
QNX and Vector’s collaboration promises to streamline the complex, costly software foundations behind the next generation of cars.
By Tim Stevens
Published: December 12, 2025
We’re in the middle of one of the most transformative periods in automotive history. No, it’s not the shift to electrification, though that’s certainly causing no shortage of consternation. It’s the rapid race to embrace the **software-defined vehicle (SDV)**, a paradigm shift that’s reshaping the very DNA of car manufacturing.
What on paper sounds like a simple switch from discrete hardware components to over-the-air (OTA) updatable algorithms has become an endless string of headaches among some of the industry’s biggest automakers. Increasing demands for ever-evolving functionality must be delivered through a tangled web of regulations and requirements. The result is a nearly untenable situation that could see future cars offering fewer features, not more.
Thankfully, there’s a potential solution coming. The hardware virtualization gurus at QNX and the middleware maestros at Vector have teamed up to create what they’re calling the **Foundational Vehicle Software Platform**. If it delivers on its promises, it could eliminate many of the most complex and challenging aspects of **automotive software development**, potentially saving the industry billions and accelerating the timeline for the **next-generation EV**.
### The Software-Defined Shift: More Than Just a Buzzword
The term **software-defined vehicle** isn’t exactly new. But as this low-level concept has sprung to the forefront of vehicle design, its meaning has been evolving.
“It’s a term that’s been around for seven or eight years,” John Wall, the president at QNX, explains. “I think in the last few years, it’s really come to mean something very specific. I think for me, what it really signifies is that the vehicle is getting more and more dependent on software for features.”
In some organizations, the shift to SDVs has been pitched as a sort of panacea for all an organization’s woes, enabling a dramatic reduction and simplification of hardware within the car—all while providing a platform for vehicles that can stay relevant on the market for longer.
“I think one of the main factors driving SDV in the traditional car companies is the ability to continue to enhance the vehicle over time, and to be able to add new features, and to be able to monetize those new features within the vehicle,” Wall adds.
But behind all those promises lurks a troubling reality that has left the software organizations of some manufacturers in a shambles. The promise of **future car features** delivered via OTA updates is being overshadowed by the sheer complexity of the underlying **vehicle software architecture**.
### The Organizational Overhaul Automakers Didn’t See Coming
Achieving new heights in software doesn’t just require more advanced code. For some traditional automakers, it requires an entire organizational reboot.
“At the moment, they are struggling, especially in the development processes,” says Matthias Traub, a member of the board of directors and the CTO at Vector. “Also from a cultural perspective. They are coming from a clear waterfall-based process with clear roles.”
The waterfall approach is a legacy software development methodology designed around projects with well-defined tasks, roles, and deadlines. That doesn’t work so well in an increasingly dynamic automotive software landscape, especially for **new EV models** that require continuous integration and deployment.
“Now it’s time to go towards a real DevOps approach,” Traub notes. “So you have smaller teams, which have the responsibility for the whole chain, so the design, the build, the software development, the test, and so on.”
QNX’s Wall points out another common pitfall: the misguided belief among many companies that they need to develop every piece of code in-house. “I think that’s where a lot of them have fallen down,” he admits.
Feeling the need to own the entire software stack means developers writing software to do extremely basic functions like securely sending data over a car’s built-in modem or painting pixels on the car’s displays. Companies that just want to build cars have instead found themselves writing layer upon layer of software that their customers will never see.
“Their energy should be focused on features that delight their customers, not on operating systems and networking stacks,” Wall stresses. This “not invented here” syndrome is proving to be one of the biggest barriers to the **SDV transition**, leading to bloated codebases and delayed product launches.
If a software stack growing taller by the minute isn’t scary enough, the breadth of modern software regulatory frameworks can be a massive challenge. The lists of things developers must be aware of just keeps getting longer.
“Things like the software bill of material, the provenance of where your software came from, you have what’s going on in the U.S., no Chinese code,” Wall says. “There are a lot of things to think about. It’s a really dynamic situation.”
### A New Platform Emerges to Tackle Automotive Software Complexity
Evolving regulations provide a moving target for initial compliance, but they also require ongoing updatability and response to vulnerabilities. This is a critical challenge for **vehicle cybersecurity** in the connected car era.
“The industry is at a tipping point where software complexity threatens to outpace innovations,” Traub warns. If this continues, Traub worries that next-generation cars might actually have fewer features than those on the road today, a grim prospect for consumers who expect more from their **modern vehicles**.
Complex regulatory environments are an area that QNX has navigated repeatedly in the past. The company’s foundational operating system can be found in everything from nuclear power plants to military aircraft, demonstrating its capability to handle the most stringent **automotive safety standards**.
“A lot of the security requirements came from the medical field, and we saw them a little bit earlier, based on the Biden administration, some of the things that they put in place,” Wall recalls.
The **Foundational Vehicle Software Platform** is built on that expertise. It’s a series of interfaces and tools from QNX and Vector designed to streamline modern **automotive software development**. It builds on both companies’ long history of abstracting and simplifying complicated aspects of integrated systems development. In an automotive sense, that means providing secure, reliable, and certifiable hardware integration, a crucial step for **autonomous vehicle software** development.
“We’re trying to remove a lot of those difficult things to deal with by bringing them together and providing one source of truth for the platform,” Wall states.
QNX and Vector have been working together for years on various projects but have worked closely together for the past 18 months to develop the new platform. Although still an evolving and ongoing project, it’s already showing solid promise not just in terms of simplification but performance, too.
Traub reveals some impressive early metrics: “Solutions running on the platform have seen as much as a 50 percent reduction in CPU load compared to custom-written code. Latency, the delay between one system making a request and getting a response, was reduced by 85 percent, and overall data transmission rates more than doubled.”
These are game-changing numbers for the **connected car industry**, where every millisecond of latency counts and every watt of power saved extends EV range.
“And we are just at the beginning,” Traub adds optimistically. “Eighteen months is not so long, and I’m sure at the end there will be much more acceleration available.”
When you speed up your software, you can run faster on simpler hardware, potentially reducing the cost of vehicle manufacturing in the process. This could be the key to unlocking the **affordable EV market**, making advanced features accessible to a wider range of consumers.
### A Promising Path Forward, But It’s Still Early
QNX and Vector’s Foundational Vehicle Software Platform is still in an evolving state, but by addressing so many of the modern software industry’s pain points, it’s already finding traction.
“It’s really amazing to see how many companies are asking us about our solution,” Traub remarks. “Before, we had only one handful of names on our list. Now it’s two handfuls or more.”
The breadth of the company’s clients will continue to ensure that the platform hits all the right marks for the **automotive industry 2026** landscape.
“Because Vector and QNX work with so many customers, just about every customer in the world, we get a good view of a road map,” Wall explains. “We get a good view of what the car companies want.”
And when will we start to see the resulting products on the road? It might not be that far off. “If you had asked me at the beginning of this project, I would have said 2029, 2030,” Wall says. “We’ve seen things accelerate recently, though I think it could be sooner than that.”
This accelerated timeline could mean that the **next-generation EV** features we’ve been promised could arrive sooner than expected, transforming the driving experience for consumers worldwide.
### The Road Ahead: From Complexity to Clarity
The journey toward the **software-defined vehicle** has been fraught with challenges, but the collaboration between QNX and Vector represents a significant step forward. By providing a foundational platform that abstracts away complexity and streamlines development, they are enabling automakers to focus on what truly matters: creating compelling features that delight customers.
The implications of this platform extend far beyond mere convenience. It holds the potential to democratize **advanced automotive technology**, making **cutting-edge vehicle software** accessible to a wider range of manufacturers and consumers. As the platform matures and its capabilities expand,
