← All mobility signals
Governance

The Foreign Driver

The US bars connected vehicles using China- or Russia-linked driving software, starting with model year 2027. From 17 March 2026, carmakers must attest their cloud-linked systems carry none of it.

What is it?

The origin of a car’s driving and connectivity code is now a condition of sale in the US. Vehicles using covered software from China- or Russia-linked makers are barred from model year 2027, and carmakers must attest their cloud-linked systems are clean of it.

Why now?

The software deadline fell on 17 March 2026. After it, legacy code survives only if its rights were transferred away and no covered supplier touches it again, Venable notes. Suppliers guard source code as their own property, so tracing it runs deep into the chain.

Who’s building it?

Carmakers and tier-one suppliers re-sourcing code, with BIS setting the terms and law firms reading them.

BISCarmakersTier-one suppliersEagle WirelessLaw firms
The full read
Why now, who is building it, where the market goes, and what stays unsettled.
Get weekly →
01 · The market
Who’s in it
Builders — carmakers and suppliers re-sourcing driving and connectivity code.
Buyers — US drivers choosing among models whose software origin is now declared by law.
Gatekeepers — BIS, which reviews declarations and grants specific authorisations.
What’s at stake
The right to sell a connected car in the US, tied to where its driving software was written.
Legacy code, if its rights stayed with covered suppliers.
An 87% share of cellular modules, per Counterpoint.
What’s unsettled
Whether carmakers can trace embedded code their suppliers refuse to share.
How strictly BIS reads declarations and grants specific authorisations.
Whether re-sourced software meets the same validation and safety standard as the code it replaces.
02 · How the demand matureda progression, not a timeline
Novelty
Software origin enters the spec sheet as a legal fact, not a detail.
Retention
Every update must now come from a supplier outside the covered list.
Willingness to pay
Carmakers accept dearer re-sourced parts, such as modules about 10% pricier, to stay on sale.
Category
Vehicle software becomes a sourced good with a declared origin, like hardware.
03 · Where the market goesthe forks, not a prediction
→Clean break or quiet workaround: carmakers rewrite covered code outright, or rely on transferred legacy rights and approved exemptions to bridge the gap.
→Code trading grows as suppliers sell source rights to keep products legal in the US.
→Other markets copy the software-origin test and apply it to cars from their own rivals.
→Hardware limits from model year 2030 widen the rule well beyond code.
It turns on whether origin of code can be proved at all, when automotive software is layered, customised and written across joint ventures and subcontractors.
04 · The Sovereign Device deskadjacent market, moving now
The Sovereign Vacuum
Foreign home robots join a US list.
FCC adds foreign-produced advanced robotic devices to its Covered List.
FCC
The Sovereign Vacuum
Household robots fall inside the scope, lawyers say.
Conditional Approval deadline set for 1 January 2028.
Sidley Austin
AI Behind Borders
States fund AI compute they own outright.
Canada commits roughly $890 million to sovereign AI compute.
Innovation, Science and Economic Development Canada
05 · The Wire
01
The US bars connected vehicles tied to China or Russia.
Bureau of Industry and Security ↗
02
Carmakers must attest their cloud-linked code is not Chinese.
eeNews Europe ↗
03
Legacy code survives only if cut loose by the deadline
Venable LLP ↗
04
Volvo Cars gets US authorization to keep selling despite Chinese owner
TechCrunch ↗
05
Commerce denies Polestar authorization to sell in the US from 2027
Automotive Logistics ↗
The panel on this signal
They agreed on
–The origin of driving and connectivity code is now a condition of sale, enforced through declarations to BIS.
–The software deadline came years before the hardware limits.
–Legacy code survives only when rights move away and covered suppliers stop maintaining it.
The automotive software-provenance engineer disagreed on
–A declaration proves paperwork, not code: layered supplier stacks and reused libraries hide origin that no attestation can fully certify.
Know more about the method →
✦How this signal was built
01 · Panel
A Delphi panel of 4 AI analysts, each reasoning independently.
→
02 · Debate
They challenge and revise each other’s reads over two rounds.
→
03 · Evidence
Every claim is tied to a cited, linked source on The Wire.
→
04 · Synthesis
A moderator writes it into one read, disagreement and all.