Dell backs Aitan with $41m as autonomous defence software targets allied markets

Aitan, formerly known as eyesAtop, has closed a $41 million financing round co-led by Deep33 and Dell Technologies Capital, bringing total capital secured by the privately held defence technology company to $54 million as it expands from Israel toward allied markets in the United States, Europe and Asia. Other participants include Gokul Rajaram, Benjamin Ling through Bling Capital and Kevin Weil through Scribble Ventures. The company is emerging from stealth around a strategy it describes as robotic sovereignty, providing software, hardware and integration capabilities that allow governments to operate and maintain heterogeneous unmanned systems under their own control. Aitan says its technology has accumulated more than 500,000 operational hours across Israeli defence deployments, although that figure is company-reported and has not been independently broken down by platform, mission or individual system.

The September 2 financing is commercially notable because Aitan is not presenting itself primarily as another drone manufacturer. Its technology is designed to coordinate different unmanned platforms through command-and-control, edge artificial intelligence and autonomy software, allowing existing systems from multiple suppliers to operate through a common architecture. The company has also disclosed a joint contract to develop a command-and-control platform for the next generation of Israel Defense Forces attack drones and additional design contracts around robotic systems, though financial values, delivery quantities and programme timelines were not disclosed.

Why is Aitan selling robotic sovereignty rather than simply manufacturing another military drone?

The distinction sits at the centre of Aitan’s commercial strategy. Defence ministries can already buy unmanned aircraft, ground robots and other autonomous platforms from numerous manufacturers. The harder problem is often making systems from different suppliers communicate, coordinate and remain upgradeable without depending permanently on one foreign vendor.

Aitan is positioning its technology as the layer that sits across those platforms. Its software and edge-computing architecture are intended to coordinate autonomous systems, provide command-and-control and allow military customers to operate, maintain and update the broader robotic force using infrastructure they control.

This can change procurement economics. A defence customer buying a proprietary unmanned system may become dependent on the original supplier for software updates, integration and future expansion. A more vendor-neutral orchestration layer can potentially let the military add new platforms without rebuilding its entire control architecture.

The idea is analogous to enterprise technology platforms that connect hardware from several manufacturers, but the defence environment introduces much stricter requirements around communications resilience, security, latency, reliability and national control.

That is why sovereignty has become an increasingly important selling point. Governments investing heavily in autonomous defence may want the underlying systems to keep functioning even if cross-border supply chains, political relationships or external communications are disrupted.

How meaningful are Aitan’s claimed 500,000 operational hours for a company emerging from stealth?

Aitan says its technology has accumulated more than 500,000 operational hours across deployments with the Israel Defense Forces and Israeli national-security organizations. Local reporting has described the figure as operational or flight hours generated through systems used since the escalation of conflict beginning in October 2023.

That level of field exposure can be commercially important because autonomous systems often behave differently in real operating environments than in controlled demonstrations. Communications interference, terrain, weather, hardware failures and rapidly changing operational requirements can reveal weaknesses that simulations do not reproduce.

At the same time, the number needs qualification. Aitan has not publicly disclosed how those 500,000 hours are distributed across individual platforms, how many systems generated them or what proportion represents fully autonomous operation rather than broader system usage.

The figure therefore supports the argument that the technology has been used extensively, but it should not be treated as a standardized reliability benchmark.

For prospective international customers, the more important evidence may come from whether Aitan can replicate deployment outside Israel. An architecture shaped around one military’s equipment, doctrine and communications environment still has to integrate with entirely different platforms and procurement systems in Europe, the United States or Asia.

Why does Dell Technologies Capital’s participation matter to Aitan’s international expansion?

Dell Technologies Capital gives the financing a strategic technology angle beyond conventional defence venture capital. Modern unmanned systems depend increasingly on edge computing because data, sensor processing and artificial intelligence decisions may need to occur close to the platform rather than being sent continuously to a distant cloud environment.

Aitan explicitly describes edge AI as one of its core technologies. That makes relationships around computing hardware, networking and enterprise-grade infrastructure potentially relevant as the company scales its architecture. Dell Technologies Capital has not announced a separate commercial supply agreement alongside the investment, so the funding should not be interpreted as evidence that Dell Technologies will automatically become an Aitan hardware provider.

The investor mix also signals the industry’s convergence. Defence technology is drawing capital from investors traditionally associated with enterprise software, semiconductors and computing infrastructure because autonomous military systems increasingly resemble distributed computing environments attached to physical machines.

For Aitan, that can help as it expands in the United States, where defence procurement requires commercial networks, local hiring and regulatory expertise in addition to technology.

Axios reported that Aitan intends to grow its U.S. team and pursue customers across Europe and Asia, while the company says the new capital will fund product development, international expansion and broader hiring.

What do Aitan’s disclosed defence contracts prove and what remains financially unknown?

Aitan says it recently secured a joint contract to develop the command-and-control platform for the next generation of Israel Defense Forces attack drones as well as design contracts involving other robotic systems. That indicates the company has moved beyond internally funded technology development and into formal defence programmes.

The missing numbers are equally important. Aitan has not disclosed contract values, revenue, backlog, delivery schedules or the proportion of its business represented by government customers.

The company’s valuation in the $41 million financing was also not disclosed. Investors therefore know the amount of capital secured and total funding to date, but not what percentage of the company was sold or what enterprise value the funding implies.

This limits conventional financial analysis. A $41 million round can be transformative for a company with modest historical revenue or relatively small for a business already holding large defence contracts. Without revenue or valuation data, the strategic interpretation is stronger than the financial one.

The next meaningful disclosure would be an international contract with a named customer, defined scope and preferably a transaction value. That would show whether technology proven within Israel can become a repeatable export product rather than remaining heavily concentrated around one domestic defence ecosystem.

Can Aitan scale autonomy across different allied militaries without becoming another bespoke contractor?

This may be the most important commercial question. Defence customers use different drones, radios, sensors, command systems and security standards, creating a temptation for technology suppliers to customize every deployment heavily.

Customization can win early contracts but limits software economics. A company becomes much more scalable if the same underlying platform can support new customers through configuration and integration rather than complete redevelopment.

Aitan’s vendor-neutral positioning suggests management is trying to build the second model. Its architecture is intended to connect disparate systems so nations can operate robotic forces without depending on one specific hardware supplier.

International expansion will test that claim. If Aitan can integrate several manufacturers across different militaries while preserving a common software platform, recurring software, maintenance and upgrade revenue could become increasingly important.

If every defence ministry requires a largely unique system, growth may look more like traditional systems integration, where revenue expands but engineering headcount and project complexity grow at almost the same rate.

The $41 million financing gives Aitan enough additional capital to discover which model it actually has.

Why is defence autonomy attracting large technology investors despite procurement risk?

Military organizations globally are increasing interest in unmanned and autonomous systems partly because they can extend surveillance, logistics and operational reach while reducing direct human exposure to dangerous environments. The strategic competition is therefore shifting from buying individual drones toward controlling networks of robotic systems.

This creates an opportunity for software companies that can coordinate existing platforms rather than manufacturing every airframe or vehicle themselves. The potentially attractive part of the economics is that software can be upgraded faster than military hardware, allowing capabilities to evolve without replacing the entire physical fleet.

The downside is procurement. Defence sales cycles can be lengthy, geopolitical restrictions can limit export markets, and budgets remain exposed to government priorities. Products also need to work under conditions far more demanding than conventional enterprise software.

Aitan’s extensive field-use claim gives it an unusually strong starting reference, but that same history does not guarantee foreign procurement success. Allied governments may require domestic manufacturing, local partners, technology transfer or sovereign hosting arrangements before adopting the platform.

Those requirements are precisely why Aitan’s sovereignty pitch may resonate. The company is effectively arguing that autonomy can be exported without forcing countries to outsource permanent control of their robotic fleets.

The next phase will show whether that concept can become a scalable business category or remains primarily a compelling description of custom defence integration.