How systems actually scale

What three recent European drone deals reveal about the real bottleneck

Three announcements landed within ten days of each other this month. None of them were about buying more drones.

• On July 1, a major European aerospace group signed its first industrial partnership with Brave1, the Ukrainian government’s defense tech coordinator. 
• On July 3, the Dutch Ministry of Defence committed over €30 million to a UAV software developer, structured as a three-year architecture program rather than a hardware order. 
• On July 13, the Netherlands and Brave1 launched a joint €20 million grant fund, split 50/50 between the two governments.

If you read those articles individually, they look like routine funding news. Read together, they describe a shift in what European buyers think they’re actually purchasing.

What buyers are optimizing for now

Talk to procurement officers working these programs, and a pattern shows up fast.

They’re not asking “how many units.” They’re asking whether a unit can be added to an existing fleet without a separate integration project. The Dutch software deal exists because the Ministry decided the interoperability layer was the thing worth a three-year commitment, not the airframes that will eventually sit on top of it.

They’re funding joint task forces, not purchase orders. The aerospace partnership with Brave1 is built around working groups that run from early research through equipment already in service. That’s a different commercial relationship than a supplier contract. It assumes the technology will keep changing after delivery.

They’re distributing risk across countries, not concentrating it in one national champion. Brave International now runs parallel programs with the Netherlands, Norway, France, Germany, and Lithuania. Ukraine brings frontline data. Each partner brings a different piece of industrial or research capacity. No single country is being asked to build the whole stack alone.

Here’s the scale of that funding shift so far:

Three inputs, and hardware is the easy one

Ask any operator who has run a mixed fleet in the field for six months what actually breaks first, and the answer is rarely the airframe.

Scale requires three things moving together, not sequentially.

Hardware that can be built close to where it’s used. This is the part getting the most public attention right now, largely because of sourcing dependency. Chinese manufacturers still supply an estimated 80% of global drone component production, and Europe’s own reshoring targets call for 60% domestic sourcing by 2035. It’s the visible problem, which is exactly why it’s the one governments fund first.

That gap is worth seeing at scale:

The gap between those two bars is exactly what a components-only strategy can close and what it can’t touch.

Software that makes disparate hardware behave as one system. This is the part the Dutch deal is really about. A ministry can localize every component in its fleet and still end up with devices that can’t coordinate, can’t share a common mission picture, and can’t be upgraded without touching every unit individually. The funding didn’t go toward a factory. It went toward the layer that turns separate procurement decisions into one operational ecosystem.

Operators trained to run the system, not just the device. This is the part that gets skipped in press releases and shows up as a problem six months later, when the software works fine in testing and falls apart under real mission tempo because nobody built the training pipeline alongside it. Human-in-the-loop control needs to be a design principle from day one, not something bolted onto the interface after the fact.

Solve only the first of these and a country ends up with expensive, disconnected hardware built with local parts. That’s a real achievement. It’s also not scale.

Why the component story keeps eating the coverage

Sourcing is easy to measure and easy to write about. A percentage of domestic content is a clean headline. Interoperability architecture and training pipelines don’t compress into a single number, so they show up less often, even when they’re where the actual work is happening.

That’s a mistake worth correcting, because the governments and organizations treating this as one integrated problem are the ones producing news like the three deals above. The ones treating it as a components problem are still writing procurement specs.

The missing tier still applies here too

None of this replaces high-end interceptor systems, and it shouldn’t be read that way. Patriot batteries and similar systems remain essential against ballistic and strategic threats. What’s being built in these partnerships sits underneath that layer: an affordable, coordinated tier that absorbs cheaper uncrewed threats so the expensive stockpile isn’t spent on them. Complementary, not a substitute.

What to actually watch next

Component sourcing numbers will keep making headlines through 2026 as reshoring targets get revisited. The more useful signal is quieter: which governments are structuring deals as multi-year software and training commitments, the way the Dutch just did, versus which ones are still writing single-line hardware tenders. That’s the tell for who understands what scale actually requires.

DK NEJET is one of a small number of companies in this space built around that same three-part shape rather than around a single product line: autonomy and coordination software, combat-proven platforms, and trained operators, delivered as one thing instead of three separate line items. It’s not a unique position to hold anymore. Watching how quickly buyers like the Dutch Ministry started structuring deals this way suggests it’s becoming the baseline the market expects, not a differentiator any one company can claim for long.