Critical Single-Source Dependencies in European Missile Defence Supply Chains
What Europe Still Depends on, Where the Real Chokepoints Sit, and What Public Evidence Can Actually Prove
The central problem is not whether European missile-defence programmes use some non-European inputs. That is already broadly understood. The analytical problem is narrower and more difficult: identifying which dependencies are truly critical, which are concentrated enough to qualify as single-source or near-single-source risks, and which can be demonstrated from public evidence rather than inferred from general industrial logic. In practice, this means moving below the level of prime contractors and complete weapon systems and examining the industrial layers that sustain missile-defence capability: semiconductor design toolchains, advanced electronics, photonics, specialty materials, propulsion-related inputs, and the lower-tier supplier base. The report starts from the premise that Europe has made real progress in system integration and programme-level sovereignty, but that important vulnerabilities remain upstream, especially where design authority, qualification constraints, export-control exposure, and sub-tier opacity intersect.
The report is structured around a strict evidentiary framework. It first defines four mandatory dependency categories: publicly evidenced single-source dependency, near-single-source dependency, structural extra-European dependency, and unresolved dependency. It then examines how current EU law and official policy documents recognise supply-chain vulnerability in defence, before turning to the semiconductor and design-toolchain layer, which appears to be the most clearly evidenced chokepoint. From there, the analysis moves through electronic components, RF and photonic subsystems, advanced materials, and hidden tier-2 and tier-3 exposures. A final section uses programme-level and institutional signals to identify where Europe itself perceives unresolved technology availability and industrial resilience problems, without confusing programme ambition with dependency resolution.