Volkswagen May Swap Rivian Software for Its China Stack in Europe [U]

Volkswagen could roll the software it uses for its Chinese cars out to its mass-market models in Europe, a move that threatens to sideline Rivian, Reuters reported Monday, citing Manager Magazin. VW declined to comment on the report.

Update, October 28: Rivian Chief Software Officer Wassym Bensaid, who co-leads the joint venture, pushed back on the report on X, saying the Volkswagen partnership is going “incredibly well” and the JV roadmap remains unchanged. He added that the VW ID.1 is on track to launch next year with its single zonal computer architecture, and that he drove it over the weekend.

The system in question is VW’s China Electronic Architecture, developed with Chinese EV maker Xpeng, and it could form the basis for around three quarters of next-generation VW, Skoda and Cupra models. Core brand chief Thomas Schaefer is expected to present the proposal to management was expected to present the proposal to management on Tuesday.

So far VW has kept its software split, using the Xpeng-developed system in China while building a separate platform for the Western world with Rivian. That $5.8 billion joint venture sits at the heart of CEO Oliver Blume’s software strategy and, as Reuters reported in March, is meant to underpin a model revamp across VW’s core brand along with Audi and Scout.

Most of that money is already locked in for Rivian, since VW’s payments for the IP license and JV stake are done, Rivian hit the winter testing milestone in March, and a $1 billion loan from VW closed earlier this month. The final payment is tied to the first salable VW built on the JV’s tech or January 2028, whichever comes first.

The longer-term hit would be revenue. Rivian’s software and services revenue tripled to $1.55 billion in 2025 almost entirely because of the JV, Automotive World reported, and fewer VW cars on the platform would likely mean less of that work over time.

Audi and Scout aren’t part of this proposal, so Rivian keeps a foothold inside VW Group either way, but losing Europe’s highest-volume brands would leave it with a much smaller partnership than the one VW originally signed up for.


Update, October 28: This article has been updated with a response from Rivian Chief Software Officer Wassym Bensaid.

Update, October 26: This article has been updated with details on how the proposal could affect Rivian’s remaining Volkswagen funding and its software revenue from the joint venture.

author avatar
Jose Castillo Founder and Editor
Jose Castillo is the founder of RivianTrackr and has owned and driven Rivians since early in the brand's consumer history. He currently drives an R1S and an R2 in Florida and uses Universal Hands-Free every day. As a credentialed Rivian journalist, he has covered the R2 First Drive in Park City and SXSW firsthand and has spoken directly with Rivian's software and autonomy leadership.
Add RivianTrackr as a preferred source on Google

12 Comments

  1. It seems like the original article in Manager Magazin is pointing at cost as the driving factor. Rivian software is more expensive than the Chinese version. Part of me thinks this is just a negotiating tactic, but if this is true this is a problem that RJ has pointed out before. China has massive structural advantages in both cost of capital and cost of labor compared to American companies. This is a problem not just in the Auto sector but across the entire economy. Have yet to hear a real solution from anyone on this problem.

      • Right. That is kind of why I came to the comment section. The way the article is written sounds like this hurts Rivian is some way regarding the JV “leaving Rivian with a much smaller slice of the company”. But it doesn’t really do anything. If VW wants to use a different software for some of it’s cars then that is fine. Who cares really.

      • While this is true, it’s not the big picture. As the article says, the point is the millions of vehicles throughout Europe that could have had Rivian software/updates but now potentially will not. It’s not an immediate effect and it doesn’t change the joint venture finances…but certainly has to be considered with regard to Rivian’s future viability/success

  2. And really, the story of the day is the acquisition of a small team of experts who can help build real world models based on the real time data drivers create every day. Bringing in smart people and continuing to innovate and leader is Rivian’s future in software. Ultimately, that is where the investment needs to be to stay in the game long term.

  3. Rivian owns half of the joint venture, which generates revenue from every vehicle equipped with its hardware and software. Obviously, this will negatively impact future revenue for both the joint venture and Rivian. But this is 2-3 years away and much can change during that time. I wouldn’t be surprised if the EU eventually restricts Chinese software or hardware. Or the JV starts selling to other OEMs.

  4. Wouldn’t this move restrict US sales? Most of the European vehicles today share a lot with the vehicles VW sells in America. I can’t imagine it making sense to maintain two completely different tech stacks on the same vehicle platform. VW is just a hot mess right now.

  5. What this won’t impact is R2 Euro sales. Look +2yrs down the road in Europe, there are Chinese software stacks sold in EU, then there will be R2 using Rivian software stack. It looks like VW is looking for entry vehicle cost controls, perhaps even for the VW Every1 entry $21k. Reduction of any sizeable amount at this entry vehicle sales point is profit/no-profit for the entire vehicle. Expect entry sub-$30k to get budget software and >$30k to get better (JV) software. By better software -> less games and adverts, more Autonomy+, updates and integration.

  6. As I see it, there are only 2 ways how this plays out. Either VW uses Rivian software on all cars except China, or it will use Xpeng software on all cars except US. Considering China is the bigger market, it’s 1 point to Xpeng.
    Now which software is more mature and closest to Tesla FSD? 1 more point to Xpeng.
    Which is cheaper to implement? Probably Xpeng, as they have demonstrated they can provide VLA2 to their cheapest model. 1 more point to Xpeng.
    I honestly struggle to find any reason why VW needs to keep sticking with Rivian software. VW can have it as backup, but it won’t catchup to FSD in probably 2-3 years, and VW is in crisis mode right now. Did I miss anything?

  7. Did this rumor originate from Jim chanos and the stock shorting team? Are we sure the software in question is not self-driving software which is not part of the JV. X peng is eating Volkswagen’s lunch in Europe it makes no sense why they would buy software from a competitor after partnering with rivian for this very software. I think the software in question is self-driving software and Volkswagen is getting a price on the software from xpeng to negotiate a better price with rivian.

  8. Sounds like a typical short seller half truth report. I can’t believe Jim chanos is back shorting rivian after losing as much as 2200% on his Tesla short.

Leave a reply

Your email address will not be published. Required fields are marked *