Counter-UAS & loitering munitions
Layered defence against the drone threat
What it is
Counter-UAS (C-UAS) systems detect, track and defeat hostile unmanned aircraft, and loitering munitions provide the affordable precision effectors of the same fight. Together they form the layered answer to the defining air threat of the decade: cheap drones in quantity.
How it is employed
C-UAS is employed in layers: detection radar tuned to small, slow, low-flying targets, electronic and kinetic defeat options matched to the threat, and loitering munitions holding launch sites and operators at risk. The economics matter as much as the kill chain: the defence must cost less per engagement than the attack.
Why it matters now
Every recent conflict in and around the region has demonstrated mass drone attack against bases, cities and infrastructure, and shown high-end interceptors being exhausted against low-cost threats. Buyers worldwide need a defensive layer priced for the threat, without a foreign veto on when it can be used.
Procurement & integration
C-UAS procurement starts with the sites and assets to be defended, then builds the sensor-effector mix around them. Unstrat represents the detection, defeat and effector chain through one channel: classification and end-user certification confirmed before representation, integration and training sustained in-region.
Capability
- Layered detection: radar, RF sensors and optical trackers with AI friend-or-foe classification
- Net-capture interceptor: 30 m net throw, 5 km operating radius, ~30 min endurance
- Swarm-capable counter-drone interceptors at up to 150 km/h
- Kinetic FPV interceptor: fire-and-forget defeat of low-RCS drones at 350+ km/h, out to 5 km
- Indoor loitering munition for urban and interior tasking, man-in-the-loop, lethal and non-lethal payloads
- Man-portable drone-detection manpack for real-time detect and track
The Unstrat difference
01Independent, non-aligned origin, with no political exposure to any major-power ecosystem.
02One accountable team from first briefing through delivery and in-region sustainment.
03Layered detection: radar, RF sensors and optical trackers with AI threat classification.
Sourcing routes compared
| Consideration | Major-power prime | Independent principal via Unstrat |
|---|---|---|
| Cost per engagement | High-end interceptors against low-cost drones | Layered defeat options priced for the mass threat |
| Release authority | Employment constrained by foreign end-use conditions | Employed under the buyer's rules of engagement |
| Political conditions | Disclosure rules, re-export restrictions and upgrade approvals held by a foreign government | Independent, non-aligned origin, accountable to the buyer's flag |
| Accountability | Multiple contractors and a foreign prime's release schedule | One accountable team from first briefing through delivery and in-region sustainment |
Comparison is qualitative. Detailed specifications are shared under briefing once the export-control position for your market is confirmed.
Related capabilities
View all →
Counter-UAS & loitering munitions: questions
What are Counter-UAS & loitering munitions?
Counter-UAS & loitering munitions are Unstrat's Sky (Air Domain) capability: Counter-UAS and loitering-munition systems that detect, track and defeat hostile unmanned aircraft, paired with detection radar tuned to small, slow, low-flying targets. The layered, affordable answer to mass drone attack that recent conflicts demand.
How do Counter-UAS & loitering munitions work?
Counter-UAS & loitering munitions deliver their effect through layered detection: radar, RF sensors and optical trackers with AI friend-or-foe classification, Net-capture interceptor: 30 m net throw, 5 km operating radius, ~30 min endurance and Swarm-capable counter-drone interceptors at up to 150 km/h, capabilities matched to the requirement and confirmed under briefing rather than published.
Who makes Counter-UAS & loitering munitions?
Counter-UAS & loitering munitions are built by The Unmanned Systems Developer, whose focus is counter-uas, loitering munitions & unmanned aircraft. Unstrat represents The Unmanned Systems Developer to government and enterprise buyers worldwide as an independent, non-aligned prime vendor.
Who uses Counter-UAS & loitering munitions?
Government and enterprise buyers acquire Counter-UAS & loitering munitions to address counter-terrorism, hostile drone attacks, attacks on critical infrastructure, prison security, vip & event protection, port security and airport security across the air domain, matched to the mission and accountable to them, not to a foreign vendor's government.
Why choose Counter-UAS & loitering munitions over a major-power alternative?
Counter-UAS & loitering munitions are sourced from an independent, non-aligned manufacturer, so they carry no major-power disclosure rules, upgrade-locks or political ramifications. Concretely: layered detection: radar, RF sensors and optical trackers with AI threat classification. The capability is accountable to you, not to a foreign vendor's government and its release schedule.
How are Counter-UAS & loitering munitions procured, and where can it be exported?
Detect, track and defeat hostile drones with a layered system priced for the mass threat, not a major-power missile economy. Every engagement begins with a briefing, and export eligibility is confirmed per market under briefing rather than published. Where controlled capabilities are involved, the classification and end-user-certificate chain is confirmed first. Counter-UAS & loitering munitions are then sustained in-region by one accountable team from briefing through long-term operation.
Questions buyers ask
What is counter-UAS as a capability?
Counter-UAS systems detect, track and defeat hostile unmanned aircraft, with loitering munitions providing the affordable precision effectors of the same fight. Together they form the layered answer to the defining air threat of the decade: cheap drones in quantity. The economics matter as much as the kill chain, because the defence must cost less per engagement than the attack.
Why does counter-drone defence need to be layered?
Because no single sensor or effector covers the whole threat. C-UAS is employed in layers: detection radar tuned to small, slow, low-flying targets, electronic and kinetic defeat options matched to the threat, and loitering munitions holding launch sites and operators at risk. Each layer covers the gap the others leave.
Why is cost per engagement the key counter-UAS metric?
Because high-end interceptors get exhausted against low-cost drones, and every recent conflict around the region has shown mass drone attack doing exactly that. The layered independent route offers defeat options priced for the mass threat rather than exquisite interceptors against cheap targets. If the defence costs more than the attack, the arithmetic favours the attacker.
How does counter-UAS procurement start for a set of fixed sites?
It starts with the sites and assets to be defended, then builds the sensor-effector mix around them. We represent the detection, defeat and effector chain through one channel, with classification and end-user certification confirmed before representation. Coverage is designed against terrain and the expected threat axis, not sold from a brochure.
See: The counter-UAS procurement pathThe counter-UAS catalogue entry
Who holds release authority over a counter-UAS system?
On the independent route the system is employed under the buyer's rules of engagement, rather than constrained by foreign end-use conditions. That release authority is the row buyers often overlook until a crisis. It matters because the defensive layer you may most need is exactly the one a foreign veto can freeze.
How does counter-UAS relate to loitering munitions in doctrine?
They are two ends of the same fight: detection and defeat protect the site, while loitering munitions hold the launch sites and operators at risk. We reference loitering munitions as the affordable precision effectors of the counter-drone problem. Pairing them keeps the adversary's launch chain under pressure rather than only intercepting what he sends.
How does electronic defeat fit within a counter-UAS reference?
Electronic defeat is one of the matched defeat options in the layer, severing the command and navigation links hostile drones depend on. It sits inside the wider electronic-warfare portfolio alongside passive sensing and protected communications. That is why the counter-UAS, drone-detection-radar and electronic-warfare pages cross-reference one another.
Who is accountable across a counter-UAS sensor-effector mix?
The major-power route tends to spread the mix across multiple contractors and a foreign prime's release schedule. The independent route puts one accountable team on the detection, defeat and effector chain from first briefing through delivery and in-region sustainment. That matters because a layered defence has more moving parts to keep aligned.
Our air force is offered Turkish and American counter-drone suites. What is the doctrine case for the non-aligned route instead?
The doctrine case rests on two rows: employment under your own rules of engagement rather than foreign end-use conditions, and defeat options priced for the mass threat rather than exquisite interceptors against cheap drones. Independent, non-aligned origin means the layer is accountable to your flag and cannot be frozen by someone else's foreign policy. We confirm classification and the end-user-certificate chain before representing any of it.
See: The major-power route against the independent routeCounter-UAS against a named alternative
How should we structure a counter-UAS programme so training and integration are not an afterthought?
Build the programme from the sites outward, then represent the detection, defeat and effector chain through one channel so integration and training are part of the same engagement rather than bolt-ons. We sustain integration and training in-region for the life of the system. That keeps a single accountable team responsible from the coverage design to the crews who run it.
We defend bases against mass drone attack but cannot afford to burn interceptors. How does the capability answer that at programme level?
The answer is a layered mix where cheap threats meet cheap defeat: detection tuned to small, slow, low targets, electronic and kinetic options matched to the threat, and loitering munitions pressuring the launch side. The design goal is that the defence costs less per engagement than the attack. That is the arithmetic the capability page argues, and it is why the sensor-effector mix is built around your sites rather than sold as a fixed suite.
See: The economics of the counter-drone fightLoitering munitions as affordable effect
Where does counter-UAS sit in the solutions map, and what else does that group?
Counter-UAS is both a capability reference and part of the effectors-and-munitions solution, because defeating drones and holding launch sites at risk are two halves of arming a force without a foreign veto. Grouping them lets a buyer treat the drone problem as one sovereignty question. The related sensing layers, passive radar and drone-detection radar, feed the same picture.
Is the counter-UAS capability already fielded, or would a buyer be funding a demonstrator?
The capability page stays qualitative and points to the catalogue entry and the side-by-side comparison for the specifics a buyer can hold us to. We do not publish figures we cannot stand behind, and gaps are marked rather than filled. Detection range and saturation numbers belong in a scoped evaluation against your sites, not in a capability overview, so we say so plainly rather than invent them.
See: The counter-UAS catalogue entryCounter-UAS compared with a named system
How does counter-UAS relate to the detection and sensing layers we would reference separately?
Detection radar tuned to small, slow, low targets and passive sensing that emits nothing both feed the tracks that the counter-UAS defeat decision rests on. Counter-UAS is the layer that turns those tracks into an engagement under the buyer's rules of engagement. That is why the counter-UAS reference cross-links drone-detection radar, passive radar and electronic warfare rather than standing alone.
We fly our own ISR and delivery drones over the sites we are defending. How does the capability reference handle that at programme level?
It treats defeat as a layered decision made under positive control and the buyer's rules of engagement, with electronic and kinetic options matched to the threat rather than applied blindly. Coordinating friendly and hostile drones over one site is a spectrum-management and doctrine question, which is why counter-UAS is scoped alongside the electronic-warfare and ISR references. The specific deconfliction belongs in a scoped evaluation, not a capability overview, so we do not assert numbers we cannot stand behind.
See: Electronic warfare across the lanesISR as the find-and-fix layer