Regulating a Dual-Use Counter-Drone System: AutoFly AI Robotics & Sky Control

How Grecta resolved the boundary between military exclusions and civil EU product safety law, converting complex multi-regime obligations into an actionable engineering backlog.

The Dual-Use Regulatory Perimeter

Sky Control is an AI-enabled counter-unmanned aircraft system (counter-UAS) built by Latvian manufacturer. Utilising sensor fusion, radio-frequency detection, an AI decision engine, and net-based interception, the system is positioned for both military defence and civil critical infrastructure like airports, prisons, and energy operators. This case study examines how a single hardware-and-AI product can sit on either side of the EU AI Act Article 2(3) military exclusion depending on how it is offered, documented, and contracted, and how to operationalise the resulting multi-regime obligations.

Download the full paper

Inside the Sky Control Engagement

Why dual-use hardware and AI require configuration-level scoping rather than generic compliance checklists.

The Boundary Problem: Military vs. Civil Scope

Under Article 2(3) of the EU AI Act, systems used exclusively for military, defence, or national security purposes are excluded. However, supplying the exact same counter-UAS to airports, prisons, or energy operators removes that exclusion. Grecta separated the intended purpose by customer segment so the right legal rules attach to each configuration.

The 5-Regime Intersecting Perimeter

Because the answer to the military exclusion controls every downstream rule, Grecta evaluated five connected regimes together: the EU AI Act (Annex I/III high-risk status), the Cyber Resilience Act (connected hardware/software), the Radio Equipment Directive (2014/53/EU), EU Dual-Use Export Controls (Regulation 2021/821), and customer-side NIS2 supply-chain evidence.

Custom Frameworks & Engineering Backlog

General compliance platforms do not model counter-UAS and dual-use regimes. Grecta translated every statutory gap into task-tracker work items with clear owners, evidence rules, and deadlines—while authoring custom machine-readable frameworks for the specialised regimes that reach the product.

💡 Key Takeaway: The regulatory perimeter of a dual-use product is not set by its technology alone—it is set by the intended purpose declared for each configuration and customer segment.

Establish where your product sits across the regimes that reach it.

Run a Compliance Pack Pilot for one product (€1,500 fixed, credited in full against your first year). You receive your formal classification and legal role, every applicable requirement with its deadline, the gap list and templates to close it, tasks exported into Jira or Linear, a buyer procurement answer pack, and your product's live verification page.

Start Your 2-Week Pilot