Every autonomous deployment creates a practical question about trust. An operator needs to know what a system can do, how reliably it will perform and how it will behave alongside other technologies. In shared airspace, that question also extends to identifying and responding to drones whose presence creates a security risk.

Andrew White, Partner at Mathys & Squire, offers a timely starting point in 27% increase in anti-drone technology patents last year. The firm’s research reports 126 patent applications worldwide in the year ending 31 March 2025, compared with 99 in the previous period. White connects this activity with drones becoming a mainstream security challenge and organisations seeking reliable countermeasures for sensitive sites and infrastructure.

The figures describe patent applications within the firm’s research. They provide a signal of inventive activity; commercial readiness requires separate evidence. For founders, investors and infrastructure operators, the strategic question is how those inventions become dependable systems that customers can deploy repeatedly.

Several voices from the Robotics, Drones & Autonomous Systems ecosystem help explore this question. Their contributions connect airspace operations, integration, learning, operational reliability and investment. The IP implications developed below are our editorial interpretation of their published work.

Adam Bry and the growing role of drones in infrastructure

In his TED talk The invisible infrastructure in the sky, Skydio’s Adam Bry describes autonomous drones supporting emergency response, infrastructure inspection and the electricity grid. His examples place flying robots within recurring operational tasks, where their usefulness depends on the information and capabilities they deliver to people on the ground.

This creates an important connection to White’s analysis. As useful drone operations become embedded in infrastructure, operators need ways to accommodate authorised activity and manage potential threats. The commercial setting includes multiple aircraft, service providers, site owners and operational responsibilities.

For IP strategy, that setting makes the interfaces between systems significant. A company may contribute a distinctive sensing capability, a software component or a method of integrating information into an operator’s workflow. Understanding which contribution customers depend on helps determine where protection and contractual permissions can support the business.

A useful management question follows: which part of the customer’s recurring operation becomes better because this company participates? Answering it connects the invention with a purchasing decision. It also helps identify dependencies that could constrain deployment, including access to other suppliers’ technology and permission to use operational information.

Florian Seibel and the commercial significance of integration

Florian Seibel provides a concrete perspective on multi-system integration. In Quantum Systems’ announcement of MOSAIC UXS, he emphasises open SDK and API architecture, third-party integration and the prevention of vendor lock-in. The platform is presented as a way to coordinate systems across air, land and sea and consolidate information from different sources.

For the wider autonomy ecosystem, this illustrates why integration is itself a strategic capability. Customers often need new technology to work with equipment and processes they already use. The supplier that makes these connections dependable can become important to the customer’s future expansion.

Our IP interpretation concerns the relationship between interoperability and control. Interfaces can be made accessible while particular implementations, engineering methods and commercially sensitive knowledge remain protected. The relevant choices depend on what partners need to connect their products and what the company needs to retain as its competitive contribution.

Counter-drone procurement brings these questions into focus because individual capabilities must fit a larger operational environment. Agreements should make clear who may reuse an integration, maintain it and develop subsequent improvements. These questions become particularly consequential when the same integration is expected to serve additional sites or customers.

The broader lesson is that an IP position should account for the relationships through which a technology reaches deployment. Technical compatibility and commercial permission both matter to repeatable growth.

Jim Fan and the value distributed across learning systems

Research co-authored by Linxi “Jim” Fan offers a comparison from humanoid robotics. NVIDIA’s GR00T N1 paper describes a foundation model developed using several sources of training material, including real and simulated robot trajectories, human video and synthetic data. It illustrates how embodied intelligence can draw on a combination of models, training processes and experience.

This is relevant to the wider IP discussion because a learning system’s commercial capability can be distributed across several assets. The visible machine may depend on software, model access, simulation tools and information generated during operation. Each introduces its own questions about ownership, permitted use and dependence on third parties.

For companies developing autonomous sensing or decision-support capabilities, an early review can follow the path from development inputs to customer deployment. Can the company use its chosen components commercially? What permissions govern information gathered at a customer site? Can experience from one installation support improvements offered to other customers?

These are questions to assess for each business, including the applicable contractual and confidentiality restrictions. They do not imply that operational data automatically belongs to the supplier or that a single patent covers the resulting system.

White’s patent signal therefore opens a wider inventory exercise: identify the technical inventions and the complementary resources required to turn them into a usable product.

Rodney Brooks and the cost of dependable operation

Rodney Brooks brings operational discipline into the conversation. In his Predictions Scorecard for January 2026, he discusses the human assistance and support that autonomous services can require. His assessment highlights how these requirements affect the economics of scaling.

For an infrastructure customer, reliability includes the work needed to keep a system useful over time. Installation, maintenance, operator attention and recovery from interruptions all influence the purchasing decision. A convincing demonstration provides only part of the evidence needed to assess those demands.

Our IP inference is that commercially valuable technical improvements can emerge from deployment itself. An engineering team may discover how to simplify calibration, reduce maintenance effort or improve performance under changing conditions. Where such work produces protectable inventions, it can strengthen the company’s position around capabilities that customers encounter every day.

Capturing these developments requires communication between field teams, product management and IP specialists. Teams also need to distinguish what can be disclosed publicly from knowledge whose value depends on confidentiality.

For counter-drone suppliers, this connects protection with the customer’s actual operating burden. The strategic value of an invention becomes clearer when the company can explain the contribution it makes to dependable, economical operation.

Fady Saad and the evidence investors need

Fady Saad, founder and general partner of Cybernetix Ventures, develops the investment perspective in The venture capital and investment view from inside robotics’ defining decade. His discussion emphasises deployment cycles, integrated hardware and software, clear customer problems and evidence of repeat purchasing. These considerations connect technical capability with a credible commercial trajectory.

That perspective gives the IP discussion a practical financing context. An investor needs to understand whether the company can reproduce the value demonstrated in an initial deployment and retain enough of that value as sales grow.

A pilot agreement can have a substantial influence on this prospect. It may determine the treatment of existing technology, customer-specific developments, subsequent improvements and access to information. Clarity about these matters helps a company explain which capabilities it can carry into its next project.

This is an editorial implication, without presuming anything about Saad’s portfolio companies or their contracts. For an emerging supplier, the useful objective is to align the rights supporting the product with the expansion described in its business plan.

The same discipline applies to the market highlighted by White. Growing inventive activity can attract attention; repeatable customer value and a credible ability to retain it help support an investment decision.

Bringing the ecosystem back to the IP decision

Together, these perspectives place counter-drone innovation within a broader management challenge. Bry connects autonomous aircraft with essential services. Seibel makes integration a strategic issue. Fan’s research illustrates the resources supporting learning systems. Brooks focuses attention on operational demands, while Saad connects deployment evidence with investment.

For a leadership team, a practical review can begin with five questions:

  • Which technical contribution makes our solution valuable in the customer’s operating environment?
  • Which rights and permissions support that contribution?
  • Which integrations and third-party dependencies affect expansion?
  • How will deployment improvements be captured and used across future projects?
  • What evidence connects our IP position with repeat purchasing and sustainable economics?

These questions extend the discussion in our Robotics & Autonomous Systems Industry Focus, which examines IP across the technologies, information and relationships supporting autonomous systems.

Andrew White’s analysis provides the entry point: rising counter-drone patent activity reflects an increasingly consequential field of innovation. The ecosystem perspective develops its commercial meaning. Founders, investors and operators need an IP strategy that supports the journey from a technical contribution to dependable deployment, and from that deployment to a business capable of scaling.