Europe Is Rearming. The Question Is Whether It’s Buying the Right Thing.

NATO budgets are surging. Hardware contracts are being signed. But the real capability gap in European defense isn’t measured in platforms — it’s measured in decision speed under adversarial conditions. The knowledge to close it already exists – it was forged in Ukraine.

Something significant is happening in European defense right now, and it’s easy to misread if you’re only watching the headline numbers.

NATO members are hitting 2% of GDP in defense spending. ReArm Europe has unlocked over €800 billion. Germany is deploying its own AI-powered targeting network, Uranos KI, this year. The UK’s Project ASGARD — a digital targeting web that compresses decision-making from hours to seconds — is slated for completion by 2027. By any measure, Europe is taking its security seriously in a way it hasn’t in decades.

And yet, the most important shift in defense right now is not about budget sizes or platform counts. It’s about what kind of capability those budgets are actually buying — and whether the procurement logic underpinning them has fully caught up with what modern threat environments demand.

The doctrine has changed. Ukraine and Russia have both adapted to the new reality. Europe largely hasn’t.

Alberts Spila, co-founder at DK NEJET  /  CSO & Head of Norway Division

The Corvette Problem

Here is a concrete way to think about what’s at stake. Billion-dollar contracts for corvettes and artillery systems are still being signed across Europe. These are serious, capable platforms. But a coordinated swarm of drones costing $20,000–30,000 can blind a corvette worth several hundred million dollars and take it out of the fight for an extended period. The asymmetry is not hypothetical — it has been repeatedly demonstrated under real operational conditions.

This is not an argument against investing in major platforms. It is an argument that platforms alone are insufficient — and that the software layer capable of coordinating multiple assets, adapting under pressure, and compressing decision cycles to machine speed is now as strategically important as the hardware it operates alongside.

The shift has already happened on the battlefield. In contested EW environments, the engagements that determine outcomes are not won by the side with the superior single asset. They are won by the side whose systems can continue to function, adapt, and coordinate when communications are degraded, GPS is unreliable, and the adversary is actively working to sever command links. That is a software architecture problem — and it is one that Europe’s current procurement pipeline is only beginning to address.

Decision Speed Is Now a Procurement Category

The EU’s AGILE program, proposed in March 2026, is one of the clearest institutional signals that Europe understands what needs to change. It’s a fast-track funding instrument designed to move defense technologies — AI-driven autonomous systems, electronic warfare tools, multi-domain coordination platforms — from development to deployment within one to three years, with funding decisions in months rather than years.

The structurally significant thing about AGILE is not just the fact that they are allocating €115 million to it. It’s more that it’s explicitly designed to attract software-native companies that do not fit the traditional consortium procurement model. They accept single-company applications, up to 100% cost coverage, and retroactive eligibility is built in. This is European defense procurement consciously redesigning itself around a different kind of supplier.

The urgency behind that redesign is not abstract:

• EU Defense Commissioner Andrius Kubilius has estimated that, in a broader conflict scenario, the EU would need 3 million drones annually just to defend Lithuania alone.
• NATO’s Hedgehog exercise showed that targeting chains, which once took hours, can now run in minutes (granted, only when the software layer connecting sensors, assets, and decision-makers is built for that speed from the ground up.)

The platforms exist. The coordination architecture is the gap.

The Software Layer Is Not Optional

Operating in a genuinely contested electronic warfare environment means your software cannot assume reliable GPS, stable communications, or a clean sensor feed. The adversary is actively trying to degrade exactly those conditions. A system designed for clean environments will fail when it matters most. The only architectures that hold up under EW pressure are those that were designed and tested specifically for adversarial degradation, and that kind of design knowledge only comes from real operational conditions.

This is why the question of where defense software gets built, and under what conditions it gets tested, is not a secondary procurement consideration. It is the primary one. A system that has never operated in a real EW environment carries unknown failure modes. A system that has been iterated through thousands of real engagements, with direct feedback from operators in the field, carries a very different kind of reliability — one that no amount of laboratory testing can fully replicate.

Ukrainian Experience as a Global Innovation Engine

Ukraine has been the most demanding and most rapidly evolving electronic warfare environment on the planet for the past three years. Every week produces new jamming techniques, new signal spoofing approaches, and new adversarial adaptations to autonomous systems. The engineers and operators working in that environment are not iterating against theoretical threat models. They are responding to a live adversary that updates its tactics faster than any NATO exercise cycle.

The knowledge accumulated through that process — through thousands of real missions, real EW encounters, real failure modes discovered and resolved under operational pressure — is now among the most strategically valuable technical assets in the world. It represents a compression of years of R&D into lived operational reality. And critically, it is transferable. The systems built on that foundation, and the doctrinal understanding that comes with them, can be integrated into allied frameworks, adapted to different operational contexts, and deployed across NATO-aligned defense architectures.

Ukrainian innovation is already moving in this direction. Defense technology developed and refined in Ukrainian conditions is being adopted by allied nations, assessed by multiple ministries of defense, and informing how European militaries are thinking about autonomous operations doctrine. This is not a future aspiration. It is happening now, at the pace that the threat environment demands.

Ukrainian operational experience isn’t just credibility. It is the fastest R&D cycle in defense technology, and transferring that knowledge to allies is precisely what European security requires right now.

The Sovereign Capability Question

European governments are starting to take seriously the fact that investors also need to understand clearly: a defense capability built on someone else’s software, updated on someone else’s timeline, and maintained under someone else’s contract is not a sovereign capability, rather it is a dependency. In national security terms, a dependency is a vulnerability — and in an environment where the software layer is increasingly decisive, that vulnerability compounds.

The European defense industrial base for software-native, autonomous systems remains fragile. Intra-European procurement for this category of capability is thin. The structural question of how the broader ecosystem sustains itself and whether Europe ends up with genuine sovereign capability or a managed dependency on a handful of non-European platforms is real and unresolved.

The fastest and most credible path to closing that gap runs through the operational knowledge base that the Ukrainian defense tech ecosystem has built over three years at real cost and in real conditions. Integrating that knowledge into European frameworks is not just a strategic opportunity. For several NATO members, it is becoming an urgent operational requirement.

Where the Investment Logic Points

For investors, the structural picture is clearer than it has been at any point in recent European defense history. Governments have publicly committed to closing a capability gap they have defined in software terms. Procurement instruments have been redesigned to favor fast, deployment-ready technology from non-traditional suppliers. The geopolitical driver is structural, not cyclical.

The category of company best positioned to capture this is not the one with the deepest hardware manufacturing base. It is the one with combat-tested software architecture, a direct operational feedback loop, and the ability to deploy across multiple NATO-aligned jurisdictions under a coherent European doctrine — while carrying the kind of real-world reliability that only comes from having built and iterated in the most demanding environment available.

Europe has the political will, the institutional frameworks, and now the funding to close the capability gap that matters. The knowledge to close the right one — measured in decision speed, EW resilience, and coordinated autonomous capability — already exists. It was built under the most demanding conditions imaginable, by people who had no choice but to get it right. The question now is whether Europe moves fast enough to put it to work.

This editorial draws on publicly available defense policy documents, procurement announcements, and operational reporting from 2025–2026. The author holds expertise in autonomous systems architecture and software-defined defense strategy.