Signals Inbox·July 17, 2026·Defense Tech
Is Helsing the new European Anduril?
Helsing is now Europe’s closest answer to Anduril, sharing 19 of 35 tracked capabilities, but Anduril still covers more weapon families and the two directly compete across only a quarter of the stack.
We track defense tech daily. Want the market signals in your inbox?
Send me the signals →Yes. Helsing is now Europe’s closest equivalent to Anduril. We mapped 35 defence capabilities across three observation dates, then separated broad similarity from actual procurement competition. Today, the companies share 19 capabilities, or 54.3% of the combined stack.
The resemblance runs much more strongly in one direction. Around 79.2% of Helsing’s current capabilities also exist at Anduril, while only 63.3% of Anduril’s stack appears at Helsing. Helsing has moved into territory Anduril already occupied far more often than the reverse.
Most of the convergence happened quickly. Their overlap jumped from 14.3% two years ago to 51.6% one year ago, then edged up to 54.3% today. Helsing is still catching up, but both companies are now adding capabilities that the other does not have.
The real competitive collision is much narrower than the headline overlap. Only 25.7% of the combined stack qualifies as direct competition, concentrated in mission software, electronic warfare, long-range strike drones and autonomous combat aircraft.
Anduril remains broader, especially in counter-UAS, strike weapons, fixed surveillance, deployable infrastructure and propulsion. Helsing’s edge is different: it fits more naturally into Europe’s existing aircraft, vehicles, primes and sovereign defence programmes.
Interested in defense tech?We can send you all the signals
Send me the signals → Delivered straight to your inboxQ1How much do Anduril and Helsing overlap today?
Anduril and Helsing currently overlap across 54.3% of the defence capabilities we tracked. At this point, the comparison rests on much more than a few similar products.
As our Anduril–Helsing Capability Convergence Map shows, they share 19 capabilities out of the 35 held by at least one of them. These include central parts of the autonomous-defence stack: battle management, sensor fusion, autonomous mission planning, swarm control, edge AI, electronic warfare, long-range strike drones, autonomous combat aircraft and underwater surveillance.
The software overlap is especially strong. Anduril uses Lattice to connect sensors, coordinate autonomous systems and support battlefield decisions. Helsing is moving into much the same territory through Altra and its other AI products.
A shared capability does not always mean interchangeable products, though. Helsing’s Lura acoustic model and Anduril’s undersea surveillance systems both sit in maritime intelligence, but they tackle the job differently.
Anduril also has 11 capabilities with no clear Helsing equivalent in our dataset. Helsing has five that remain unique. The convergence is real, but there is still plenty separating them.
Anduril–Helsing capability convergence map
| # | Capability | Anduril today | Helsing today | Shared two years ago | Shared one year ago | Shared today | First mover | Current overlap depth |
|---|---|---|---|---|---|---|---|---|
| 1 | Multi-domain sensor fusion and common operational picture | Yes | Yes | Unclear | Yes | Yes | Anduril | Direct product overlap |
| 2 | Battle management command and control | Yes | Yes | Unclear | Yes | Yes | Anduril | Direct product overlap |
| 3 | Autonomous mission planning and dynamic tasking | Yes | Yes | No | Yes | Yes | Anduril | Same product category |
| 4 | Collaborative autonomy and swarm control | Yes | Yes | No | Yes | Yes | Anduril | Same product category |
| 5 | Open third-party platform integration | Yes | Yes | Unclear | Yes | Yes | Anduril | Same broad capability |
| 6 | Resilient tactical networking and data mesh | Yes | Yes | No | Yes | Yes | Anduril | Same broad capability |
| 7 | Edge AI detection, classification and target recognition | Yes | Yes | No | Yes | Yes | Anduril | Same broad capability |
| 8 | Simulation and reinforcement-learning training for autonomy | Yes | Yes | No | Yes | Yes | Anduril | Adjacent |
| 9 | AI-based emitter classification and threat evaluation | Yes | Yes | Yes | Yes | Yes | Anduril | Same product category |
| 10 | Electronic support, direction finding and geolocation | Yes | Yes | Yes | Yes | Yes | Anduril | Same product category |
| 11 | Electronic attack and adaptive jamming | Yes | Yes | Yes | Yes | Yes | Anduril | Same product category |
| 12 | Autonomous electronic-attack combat aircraft | No | Yes | No | No | No | Helsing | Adjacent |
| 13 | Tactical VTOL ISR drone | Yes | No | No | No | No | Anduril | None |
| 14 | Man-portable loitering precision strike | Yes | No | No | No | No | Anduril | Adjacent |
| 15 | Long-range loitering strike drone | Yes | Yes | No | Yes | Yes | Anduril | Direct product overlap |
| 16 | Air-breathing cruise missile and stand-off strike | Yes | No | No | No | No | Anduril | Adjacent |
| 17 | Autonomous combat and collaborative combat aircraft | Yes | Yes | No | No | Yes | Anduril | Direct product overlap |
| 18 | AI integration into crewed fighter aircraft | No | Yes | No | No | No | Helsing | Adjacent |
| 19 | Counter-UAS detection and autonomous classification | Yes | No | No | No | No | Anduril | Adjacent |
| 20 | Kinetic drone-on-drone interception | Yes | No | No | No | No | Anduril | None |
| 21 | Reusable high-speed counter-air interceptor | Yes | No | No | No | No | Anduril | None |
| 22 | Electronic counter-UAS defeat | Yes | No | No | No | No | Anduril | Adjacent |
| 23 | Fixed-site border, base and infrastructure surveillance | Yes | No | No | No | No | Anduril | None |
| 24 | Artillery fire control and indirect-fires integration | Yes | Yes | No | No | Yes | Helsing | Same product category |
| 25 | Company-owned autonomous ground robotic platform | No | Yes | No | No | No | Helsing | Adjacent |
| 26 | AI integration with third-party ground vehicles | Yes | Yes | No | No | Yes | Same period | Same broad capability |
| 27 | Autonomous underwater vehicles | Yes | Yes | No | Yes | Yes | Anduril | Same product category |
| 28 | Persistent underwater surveillance and anti-submarine awareness | Yes | Yes | No | Yes | Yes | Anduril | Same product category |
| 29 | Large acoustic model for vessel and submarine classification | No | Yes | No | No | No | Helsing | Adjacent |
| 30 | Autonomous undersea effects and torpedo delivery | Yes | No | No | No | No | Anduril | Adjacent |
| 31 | Distributed undersea sensor constellations | Yes | Yes | No | Yes | Yes | Same period | Same product category |
| 32 | Tactical space-based reconnaissance and targeting | No | Yes | No | No | No | Helsing | Adjacent |
| 33 | Deployable edge command, compute and communications infrastructure | Yes | No | No | No | No | Anduril | None |
| 34 | Hyperscale and distributed defence manufacturing | Yes | Yes | No | Yes | Yes | Anduril | Same broad capability |
| 35 | Solid rocket motor design and production | Yes | No | No | No | No | Anduril | None |
Q2How much of Helsing’s business now looks like Anduril?
Almost four-fifths of Helsing’s current capability stack also exists at Anduril. That is why the “European Anduril” label has become so common.
Helsing has 24 evidenced capabilities today, and 19 are also present at Anduril. That gives Helsing a 79.2% resemblance to Anduril.
The reverse comparison is lower. Anduril has 30 capabilities, of which 19 also exist at Helsing, so Anduril resembles Helsing across 63.3% of its stack.
The asymmetry becomes obvious when you read the convergence map in both directions. Most of Helsing’s activities now sit inside categories Anduril already covers, while Anduril still operates in several areas Helsing has not entered publicly.
Those Anduril-only areas include dedicated counter-drone interceptors, tactical VTOL reconnaissance drones, cruise missiles, fixed surveillance towers, deployable command infrastructure and solid rocket motors.
Helsing already looks a lot like Anduril. Anduril still has the wider perimeter.
Q3Is Helsing basically a smaller Anduril?
Partly. Helsing is smaller by capability count, but the bigger difference is where each company has concentrated.
Helsing covers 24 capabilities, compared with 30 for Anduril. Its stack is therefore 80% as broad as Anduril’s. Two years ago, that figure was only 20%.
That is a huge shift. Helsing now operates in long-range strike, underwater autonomy, ground robotics and autonomous combat aircraft, on top of its original strengths in AI and electronic warfare.
Its portfolio still has a different shape.
Helsing covers every software and artificial-intelligence capability in our taxonomy. It also has all four electronic-warfare capabilities, compared with three for Anduril. Its strongest areas are software-defined operations, European platform integration, electronic warfare and a selected group of autonomous platforms.
Anduril has built more complete product families. It covers every counter-UAS capability we tracked, all three strike-system capabilities and several areas Helsing has not entered, including propulsion, expeditionary command infrastructure and fixed-site surveillance.
“A more focused Anduril” is closer to the data than simply “a smaller Anduril.”
We track defense tech daily. Want the market signals in your inbox?
Send me the signals →Q4Are Anduril and Helsing getting more similar?
Very clearly. Their capability overlap rose from 14.3% to 54.3% in two years.
The Anduril–Helsing Capability Convergence Map also shows when this stopped being a loose comparison. Two years ago, we found only three shared capabilities, all in electronic warfare.
One year ago, the number had jumped to 16. Helsing’s launch of Altra and HX-2 created new overlap in mission software, autonomy, strike systems and manufacturing. Its move into underwater systems then pulled the companies closer in the maritime domain.
Today, they share 19 capabilities. The latest additions came from autonomous combat aircraft, artillery integration and AI integration with ground vehicles.
The big leap happened between two years ago and one year ago. Since then, the overlap has kept rising, just much more slowly.
How the overlap changed over two years
| Observation date | Anduril capabilities | Helsing capabilities | Shared capabilities | Symmetric overlap |
|---|---|---|---|---|
| Two years ago | 20 | 4 | 3 | 14.3% |
| One year ago | 28 | 19 | 16 | 51.6% |
| Today | 30 | 24 | 19 | 54.3% |
Q5Is Anduril-Helsing convergence speeding up?
No. The companies are still moving closer, but the pace has slowed sharply over the last year.
The overlap score rose by 37.3 percentage points during the first year of the period. Over the latest 12 months, it gained only another 2.7 points.
Helsing still added five net capabilities during that time, including autonomous combat aircraft, ground robotics, tactical space reconnaissance and new land integrations.
Several additions did not create new overlap. Helsing’s autonomous electronic-attack aircraft, Gripen AI integration, RX-1 ground platform and KIRK space programme pushed it into areas where Anduril had no direct equivalent in our taxonomy.
Anduril kept adding capabilities too. Both portfolios are growing, and growth on both sides no longer guarantees a higher overlap score.
Q6Is Helsing becoming more like Anduril, or is Anduril moving toward Helsing?
Most of the convergence comes from Helsing moving into areas where Anduril already had products or programmes.
The first-mover column in our convergence map makes the direction fairly hard to miss. Anduril entered first in 16 of the 19 capabilities the companies now share. Helsing moved first in one, while two appeared at roughly the same time.
Mission software gives the clearest example. Anduril had already built Lattice around sensor fusion, command and control, mission planning, swarm coordination and third-party integration before Helsing introduced comparable Altra capabilities.
The same sequence appears in long-range strike drones, autonomous underwater vehicles, persistent undersea surveillance and autonomous combat aircraft. Anduril entered first, then Helsing followed with HX-2, SG-1, Lura and CA-1 Europa.
Artillery integration is the main exception. Helsing introduced Altra Indirect Fires before Anduril showed comparable fire-control integration through Lattice Mesh.
That does not mean Helsing copied Anduril. They are chasing many of the same military requirements. Still, the direction is hard to miss: Helsing enters Anduril’s earlier territory far more often than Anduril enters Helsing’s.
Interested in defense tech?We can send you all the signals
Send me the signals → Delivered straight to your inboxBoeing is turning a 500-pound JDAM into a cruise missile
Ursa Major is going public with $350M to scale hypersonics
The U.S. Army is testing 70,000-foot balloons over Poland
The Navy just revealed its longest-range air-to-air missile
Saildrone just fired two JAGM missiles from an autonomous vessel
Castelion raises $1B to mass-produce Blackbeard hypersonic missiles
The Navy is paying Raytheon $22.9B for more Tomahawks
Ukrainian drones wiped out a U.S. armored brigade in Germany
Q7What is making Anduril and Helsing more similar?
Helsing’s move from defence software into complete air, strike, land and maritime systems has driven most of the recent convergence.
Electronic warfare was the original meeting point. Both companies already worked on emitter classification, geolocation and adaptive jamming two years ago.
The next wave came from Altra and HX-2. Together, they moved Helsing into sensor fusion, battle management, mission planning, swarm control, edge AI, resilient networking and long-range loitering strike.
Underwater systems added another layer. SG-1 and Lura gave Helsing a position in autonomous underwater vehicles, persistent anti-submarine surveillance and distributed sensor constellations. Anduril had already entered these areas through Dive Technologies and later Seabed Sentry.
CA-1 Europa then created a much cleaner comparison in autonomous combat aircraft. Helsing’s artillery and ground-vehicle integrations added more overlap on land.
Capabilities driving the recent convergence
| Capability creating convergence | Became shared | Company entering later | What changed |
|---|---|---|---|
| Sensor fusion and common operational picture | Within the last two years | Helsing | Creates comparable battlefield software layers |
| Battle management command and control | Within the last two years | Helsing | Moves Helsing closer to Lattice’s sensor-to-effector role |
| Autonomous mission planning | Within the last two years | Helsing | Gives both companies customer-facing mission-autonomy software |
| Collaborative autonomy and swarm control | Within the last two years | Helsing | Supports coordinated autonomous mass rather than single systems |
| Long-range loitering strike drones | Within the last two years | Helsing | HX-2 creates clear product-level strike overlap |
| Autonomous underwater vehicles | Within the last two years | Helsing | Extends competition into undersea autonomous platforms |
| Persistent underwater surveillance | Within the last two years | Helsing | Gives both companies a long-duration anti-submarine proposition |
| Distributed undersea sensor constellations | Within the last two years | Both around the same period | Shows parallel movement toward autonomous maritime mass |
| Autonomous combat aircraft | Within the last year | Helsing | CA-1 Europa enters a strategic category already occupied by Fury |
| Artillery fire-control integration | Within the last year | Anduril | Rare example of Anduril entering Helsing’s earlier territory |
| Third-party autonomous ground integration | Within the last year | Both around the same period | Extends both software stacks into land warfare |
Q8Is Helsing actually catching up with Anduril?
Yes. Helsing has closed a large part of the capability gap over the last two years, even while Anduril kept expanding.
Two years ago, Anduril had 20 evidenced capabilities and Helsing had four. The gap was 16.
One year ago, it had fallen to nine. Today, Anduril has 30 capabilities and Helsing has 24, leaving a difference of six. Helsing has therefore closed 62.5% of the original gap.
Anduril was growing at the same time. It added capabilities in manufacturing, undersea warfare, artillery integration and ground autonomy.
Across the full period, Helsing added 20 capabilities and Anduril added seven. Helsing expanded inside its original areas and moved into new families such as maritime systems, ground robotics, manufacturing and space.
The remaining difference is bigger than six capabilities makes it sound. Anduril has 11 unique areas and Helsing has five, and several of Anduril’s are already full product families rather than small extensions.
Q9Do Anduril and Helsing actually compete with each other?
Yes, but much less directly than the 54.3% overlap figure suggests. Strict direct competition covers only 25.7% of the combined stack.
That stricter score only counts areas where both companies could realistically address the same customer need or show up in the same procurement process.
The group includes battle management software, mission autonomy, electronic warfare, long-range strike drones and autonomous combat aircraft.
A broader definition that includes partial competition raises the score to 48.6%. This catches areas where the companies solve a similar problem but use different product formats, architectures, maturity levels or routes to market.
Maritime systems show the difference well. Both offer autonomous underwater systems and persistent surveillance, but Anduril’s Dive platforms, Seabed Sentry and Copperhead do not map neatly onto Helsing’s SG-1 gliders and Lura acoustic model.
Manufacturing is another example. Anduril’s Arsenal and Helsing’s Resilience Factories express similar ambitions, but a defence ministry would not normally choose between them as competing products.
The two companies are converging faster as strategic models than as substitutes in an actual procurement.
We track defense tech daily. Want the market signals in your inbox?
Send me the signals →Q10Where do Anduril and Helsing compete most directly?
The clearest competition currently sits in mission software, electronic warfare and a small number of autonomous air and strike systems.
Mission software is the biggest direct battleground. Both companies cover all six software capabilities in our taxonomy. Four already qualify as direct competitive overlaps: sensor fusion, battle management, autonomous mission planning and collaborative autonomy.
Electronic warfare is just as real. Both classify emitters, locate threats and generate adaptive electromagnetic effects. Three of the four capabilities we tracked are shared and directly competitive.
The air and strike overlap is smaller but strategically important. HX-2 competes with Anduril’s long-range loitering weapons, while CA-1 Europa creates a clear comparison with Fury in autonomous combat aircraft.
Maritime overlap is wider than the direct competition score suggests. Both companies operate in three of the five maritime capabilities, but their systems still differ enough in architecture and operating concept to limit direct substitution.
Counter-UAS is where Anduril stands alone most clearly. It covers all four capabilities we tracked, while Helsing has no publicly evidenced dedicated counter-drone family.
Where Anduril and Helsing compete most directly
| Capability family | Shared capabilities | Family overlap | Direct competitive overlaps | Current interpretation |
|---|---|---|---|---|
| Mission software | 6 of 6 | 100% | 4 | Deepest and most systematic competitive overlap |
| Artificial intelligence | 2 of 2 | 100% | 0 | Shared enabling technologies, but not standalone procurement substitutes |
| Electronic warfare | 3 of 4 | 75% | 3 | Strong direct competition across core EW functions |
| Maritime systems | 3 of 5 | 60% | 0 | Broad strategic overlap with different architectures |
| Land systems | 2 of 4 | 50% | 0 | Growing integration overlap, still limited product substitution |
| Air systems | 1 of 3 | 33.3% | 1 | Narrow but strategically important collision in autonomous combat aircraft |
| Strike systems | 1 of 3 | 33.3% | 1 | Direct overlap in long-range loitering strike |
| Counter-UAS | 0 of 4 | 0% | 0 | Clear Anduril-only product family today |
| Infrastructure | 0 of 1 | 0% | 0 | Anduril-only deployable edge infrastructure |
| Propulsion | 0 of 1 | 0% | 0 | Anduril-only vertical integration |
| Space systems | 0 of 1 | 0% | 0 | Helsing-only disclosed space programme |
| Manufacturing | 1 of 1 | 100% | 0 | Shared industrial model, not direct product competition |
Q11Is the Anduril-Helsing overlap spread across the whole defence stack?
Across most of it, yes. The companies now overlap in mission software, artificial intelligence, electronic warfare, air systems, strike systems, land systems, maritime systems and manufacturing.
This is no longer a comparison built around one similar drone or one AI product. The overlap runs from battlefield software down to physical autonomous platforms and the factories meant to produce them.
Some families still contribute far more than others. Mission software accounts for six shared capabilities. Electronic warfare adds three, and maritime systems another three. Together, those areas represent 12 of the 19 shared capabilities.
The weighted overlap score reaches 57.9%, slightly above the unweighted 54.3%. Their shared capabilities tend to sit in important areas such as command software, autonomy and electronic warfare.
Once evidence quality is included, the score falls to 47.3%. Several capabilities exist at both companies, but the public proof is stronger on one side. One may have an operational deployment while the other has only announced or demonstrated a product.
So yes, the overlap is broad. The mature, head-to-head competition is still concentrated in fewer places.
Q12Where are Anduril and Helsing still clearly different?
They differ most in complete weapon families, European platform integration and the industrial layers each company wants to control.
Anduril’s biggest unique area is counter-UAS. It has dedicated products for detection, autonomous classification, drone-on-drone interception, reusable counter-air interception and electronic defeat. Helsing has relevant AI and electronic-warfare technology, but no comparable dedicated counter-drone family appears in the public evidence we reviewed.
Anduril also stands alone in tactical VTOL reconnaissance, man-portable loitering weapons, cruise missiles, fixed-site surveillance, undersea effects, deployable edge infrastructure and solid rocket motor production.
Some of these gaps may last. Anduril’s move into rocket motors and expeditionary command infrastructure shows a broader appetite for controlling hardware and industrial layers that Helsing has not publicly prioritised.
Helsing has fewer unique areas, but they say a lot about its European strategy.
Its AI has been integrated into a crewed Saab Gripen fighter. Lura gives Helsing a dedicated large acoustic model for classifying submarines and vessels. Helsing has also introduced an autonomous electronic-attack aircraft and moved into tactical space reconnaissance through its KIRK joint venture with OHB.
That fits Helsing’s close relationships with European defence primes and national platforms. It can add AI and autonomy to aircraft, artillery, ground vehicles and sensors that European militaries already use.
Anduril owns the broader set of unique capabilities. Helsing’s distinctive strengths are tied more closely to European integration and sovereign defence programmes.
Q13Is Helsing really the European Anduril?
Yes, with a fairly big caveat. Helsing is now Europe’s closest structural equivalent to Anduril, but it has not reproduced the whole Anduril model.
The comparison works because both companies want to own the AI and mission-software layer, build proprietary autonomous platforms, produce lower-cost systems at scale and connect their technology with third-party equipment.
The numbers in our capability convergence map back that up. The companies overlap across 54.3% of the tracked capability union. Almost 80% of Helsing’s current capabilities are also present at Anduril, and Helsing has closed 62.5% of the breadth gap that existed two years ago.
Anduril still has six more evidenced capabilities overall and 11 areas with no current Helsing equivalent. Its lead is especially clear in counter-UAS, strike weapons, deployable infrastructure, fixed surveillance and propulsion.
The broad similarity also overstates how often they truly compete. Strict competitive collision covers only 25.7% of the combined stack.
Helsing’s route is shaped by Europe’s existing defence industry. Its work with Saab, Airbus, ARX, OHB and other European players makes it more integration-heavy. Helsing can supply AI, autonomy and mission software while leaning on platforms and supply chains already embedded in European armed forces.
Our conclusion today is simple: Helsing is the European Anduril, but a more focused and more European one. Anduril remains broader and more vertically integrated. Helsing is catching up fast through a tighter portfolio and a stronger position inside Europe’s existing defence ecosystem.
We track defense tech daily. Want the market signals in your inbox?
Send me the signals →We tested the “European Anduril” label by breaking it into separate questions: portfolio breadth, shared capabilities, direct competition, the direction and speed of convergence, catch-up, and the parts of each company that still look different. We then compared the evidence across those dimensions before reaching the overall conclusion.
We built a fixed taxonomy of 35 defence capabilities covering mission software, artificial intelligence, electronic warfare, air and strike systems, counter-UAS, land systems, maritime systems, space, infrastructure, manufacturing and propulsion. Each capability represents a distinct military function or technology layer rather than an individual product, which prevents several versions of the same system from being counted separately.
We assessed both companies at three fixed observation dates: 17 July 2026, 17 July 2025 and 17 July 2024. A capability was included only when dated public evidence existed on or before the relevant date. Later announcements were not applied retrospectively.
We counted a capability only when it was supported by an identifiable product, programme, contract, deployment, acquisition or demonstrated integration. Broad ambitions, generic technology claims, undisclosed programmes and partnerships without a visible technical result were excluded. When the evidence remained uncertain, we marked the capability as unclear instead of filling the gap with an assumption.
We prioritised official product pages, government and military announcements, procurement documents and disclosures from programme partners. Reputable defence reporting was used when it added material detail unavailable from primary sources. We also recorded whether a capability was developed internally, acquired, jointly developed, enabled through a partner or integrated into a third-party platform.
The headline overlap score uses the Jaccard method: shared capabilities divided by all capabilities held by at least one of the two companies. We calculated directional resemblance, capability breadth, direct competitive collision, product-level overlap, strategic-importance-weighted overlap and evidence-adjusted overlap separately because they answer different questions.
A shared capability was not automatically treated as direct competition. We separated adjacent technologies, shared broad capabilities, shared product categories and direct product overlap. Direct competition was recorded only when the offerings could credibly address the same operational need or appear in the same procurement decision.
Strategic importance was scored from one to five based on how central each capability is to the companies’ broader defence platforms. Evidence quality was also scored from one to five, moving from announcement-stage evidence to contracts, operational deployments, combat use or several independent confirmations. These weighted results remain separate from the unweighted headline score.
The comparison tracks only publicly evidenced capabilities at each observation date. Classified possibilities, presumed internal projects and unverified claims were not used to complete either company’s portfolio.
Key Anduril sources include: Lattice mission autonomy, the Defense Innovation Unit’s Replicator software announcement, Fury, Anduril’s air-dominance and strike family, Roadrunner, Anduril’s maritime portfolio, Dive-XL, Copperhead, Seabed Sentry, Arsenal, and the Adranos acquisition.
Key Helsing and partner sources include: Altra, HX-2, SG-1 Fathom and Lura, CA-1 Europa, CA-1 Electronic Attack, Saab’s Gripen E flight-test announcement, RX-1, the ARX Robotics partnership, OHB’s KIRK joint-venture announcement, and Helsing’s Resilience Factories.
Building or investing in defense technology?We can send you all the signals
Send me the signals → Delivered straight to your inbox