Counter-drone swarm systems
Layered swarm defence architecture
Overview
A layered counter-drone architecture built for the swarm threat: radar, RF and optical sensors fused with friend-foe discrimination, cueing multiple effectors from one command layer. Sits above the individual counter-UAS effectors and scales from a single site to national coverage.
Defence built for the swarm, not the single drone: layered sensors with friend-foe discrimination cueing multiple effectors from one command layer.
Capabilities
- Layered radar, RF and optical detection fused into one track picture
- Friend-foe discrimination across mixed friendly and hostile drone traffic
- Cues net-capture, kinetic and electronic effectors from one command layer
- Scales from single-site protection to national coverage
- Defends against saturating mass attack the affordable way: many low-cost effectors coordinated as one, not a scarce missile spent per drone
Specifications
| Type | Counter-drone swarm architecture |
| Sensors | Radar / RF / optical, fused |
| Discrimination | Friend-foe across mixed traffic |
| Origin | Independent / non-aligned |
In depth
The architecture above the interceptor
The product is defined as a counter-drone swarm architecture rather than a single interceptor. Its published sensor mix is radar, RF and optical detection fused into one track picture. The architecture also applies friend-foe discrimination across mixed friendly and hostile drone traffic. That distinction gives the command layer a specific task. It must combine different observations, identify which traffic is friendly or hostile, and present the resulting picture for action. The system therefore sits above individual effectors, where the problem is not simply whether one drone can be engaged, but how multiple tracks and responses are handled together.
One track picture
Radar, RF and optical inputs do not perform the same observation, so the record describes their fusion rather than selecting one as the sole source. Friend-foe discrimination is applied across the mixed traffic. The result is one track picture for the command layer instead of separate sensor views that an operator would have to reconcile manually. This is the part of the system that turns sensor plurality into a coordinated defence architecture. The catalogue does not publish a universal range, speed or endurance for this product. Its verified specification remains the sensor types, their fusion and the discrimination function.
Cueing several response types
The command layer cues net-capture, kinetic and electronic effectors. These are the response classes named in the product record. Net capture, kinetic defeat and electronic defeat are not presented as interchangeable, so the architecture can assign the available response to the track and the configured engagement plan. The value of the swarm system lies in coordinating those effectors from one layer rather than treating each as an isolated point solution. The statement is deliberately narrower than a performance promise. The record confirms cueing and coordination, not a universal result against every swarm composition or operating environment.
From one site to wider coverage
The catalogue states that the architecture scales from single-site protection to national coverage. That describes a coverage path, not a fixed claim that one installation protects an entire country. A single site can be the starting point, while additional defended locations can be brought into the same architecture as the requirement grows. The exposition identifies the system as layered and built for the swarm threat. The buyer's selected sensors, effectors, command arrangements and site requirements determine the actual configuration. Keeping that distinction visible prevents the word national from being mistaken for an unqualified range or capacity figure.
A vendor-neutral effector layer
The exposition describes the architecture as vendor-neutral at the effector level. That permits the sensor-effector mix to be matched to the sites and assets being defended instead of treating a fixed package as the only answer. It also gives the command layer a defined integration problem: the system must connect the selected sensors, effectors and operating picture into one architecture. The product detail does not name a particular external interface or existing national system, so those points remain matters for configuration. What is verified is the architectural role, the named sensor fusion and the ability to cue multiple effectors.
Governance and employment
The system is represented through one accountable channel, with classification and end-user certification confirmed before it is marketed. The exposition states that integration and sustainment are handled in-region and that employment follows the buyer's own rules of engagement. Those conditions describe how the architecture reaches an operator, not an additional sensor or effector feature. They matter because a swarm-defence command layer is tied to the authority that decides which response is permitted. The published origin is independent and non-aligned. No customer, deployment, certification or numeric performance claim is added beyond the catalogue and detail record.
Why Unstrat: the difference
Unstrat is the authorised global representative and distributor for this capability. It is already in service with a track record behind it, so you are buying something that has done the job elsewhere, not funding a first attempt. You are not the test bed.
Independent, non-aligned origin, with no political exposure to any major-power ecosystem.
One accountable team from first briefing through delivery and in-region sustainment.
Friend-foe discrimination: defends against the swarm without blinding your own fleet.
How it reaches you
Related capability
View all →
Procurement & sustainment
Classification and the end-user-certificate chain are confirmed before this capability is represented to your market.
Sourced from an independent manufacturer: no major-power disclosure rules or political conditions.
A single team responsible from first briefing through delivery: not a chain of foreign primes to integrate yourself.
Lifecycle support and operator training delivered in-region, building capability that outlasts the initial deployment.
Questions buyers ask
What is a counter-swarm system?
A counter-swarm system is the layer above individual counter-drone effectors: sensing fused into one track picture, discrimination between friendly and hostile aircraft, and the logic that decides which effector engages which track and in what order. Buying a single interceptor is not buying counter-swarm capability. Ours cues net-capture, kinetic and electronic effectors from one command layer and scales from a single site to national coverage.
See: Counter-drone swarm architectureCounter-UAS solution hub
How do you stop a drone swarm?
With numbers, not with one excellent machine. Once twenty targets arrive together, the constraint stops being sensor sensitivity and becomes how many cheap effectors you can put in the air per minute. Wideband jamming is the usual shortcut and it takes your own drones down with the attack. We coordinate many low-cost effectors as one, after discriminating friend from foe.
Best counter-drone swarm defence system
Judge it on the effector list the command layer can allocate to, not on the radar specification. Aselsan publishes threat evaluation and effector allocation algorithms in İHTAR, which is the right architecture, then gives it a jammer plus a gun or laser bought separately. Meteksan's KAPAN fuses radar and electro-optics into one picture and neutralises with an RF jammer. Ours allocates net, kinetic and electronic effectors per track from the same layer.
See: Architecture compared with Aselsan, Meteksan and Fortem
Counter-swarm system for a site that also flies its own drones
Choose an architecture that discriminates before it engages. İHTAR 100 meets swarms with omnidirectional jamming across control, data and GNSS bands, and that volume includes your aircraft. Our system performs friend-foe discrimination across mixed traffic and assigns an effector per track, so friendly ISR and logistics flights are not the cost of defending the site.
See: Friend-foe rows in the comparisonCoordinating many airframes as one
Counter-drone architecture that scales from one base to national coverage
Scaling is a command-layer property, not an effector property. Ours is designed to grow from single-site protection to national coverage with the same fusion and allocation logic underneath, so a second and third site extend the picture rather than starting a new integration. Aselsan states that multiple İHTAR systems can work jointly for area air defence, and Meteksan calls KAPAN scalable infrastructure; both are still built around one neutralisation mechanism.
Sensor fusion for counter-UAS: what should it actually deliver?
One track per object, classified, with enough confidence for a release decision. Our layer fuses radar, RF and optical detection into a single picture and drives classification from it. Where the sensor picture matters more than emissions, passive detection contributes persistence without advertising the defence, which is why the two lines are usually specified together.
See: Passive radar in the sensing mixPassive versus active radar
Alternative to Meteksan KAPAN for counter-swarm defence
KAPAN is a solid single-site suite: drone detection radar and electro-optics, detection of drones up to 2.5 km, AI-integrated classification and an RF jammer, mounted stationary or mobile. It is built around one defeat mechanism. Ours is a command layer above several effector types, designed to scale beyond the fence line, and supplied without a state shareholder in the chain.
Counter-swarm defence for a forward operating base that has to relocate
Mobility argues for putting sensors, command and effectors on the same move order. Our architecture scales down to a single site and travels with it, and the pod-deployed configuration exists precisely so the defeat layer arrives with the sensors rather than in a later phase. Fortem's man-portable SkyDome kit is the lighter counterpoint at 89 kg across two people, though it carries one interceptor.
See: Pod-deployed interceptors, EOIR and C2Deployment and relocation compared
Counter-drone command layer that cues effectors from more than one supplier
Most counter-drone programmes fail at the seams: radar from one supplier, jammer from another, C2 from a third and integration from a fourth. Ours is built as the layer that fuses the sensing and allocates the effectors, and it integrates with existing C2 and sensor systems. Fortem publishes an open API and names FAAD C2 compatibility, which is a stronger public claim than ours, so test integration during evaluation rather than accepting either statement on paper.
Twenty drones arrive at once from two axes. What does the system do in the first sixty seconds, and who decides?
Detection and fusion produce one track per airframe, classification separates friendly from hostile across the mixed picture, and the command layer allocates effectors track by track rather than blanketing the sector. Effectors available to it include net capture, kinetic interception and electronic defeat. Ask every vendor to demonstrate that sequence live against multiple simultaneous targets, because allocation logic is the part that brochures describe and few evaluations test.
Can a jammer-based counter-drone system defeat fibre-optic or inertially guided attack drones?
Not reliably, and no serious vendor claims it can. Jamming acts on the radio link and on satellite navigation, which is precisely what Aselsan's documents describe: control, telemetry, video and GNSS bands. A drone flying a pre-set inertial profile or trailing a fibre link presents nothing to deny, so the engagement has to be physical. Our architecture keeps kinetic and net effectors inside the same command layer for exactly that case.
See: Defeat mechanisms and their failure modesKinetic effectors in the counter-UAS line
How many simultaneous tracks does your command layer hold, and how do we compare that against other vendors?
We do not publish a simultaneous-track figure, and that is a fair thing to press us on before contract. For reference, Fortem publishes 50 configurable simultaneous tracks on its TrueView R30 radar, while Aselsan and Meteksan state multi-target tracking without a number. Ask all vendors for the figure against the specific radar quoted, and for the number of effectors that can be controlled concurrently, which matters more for saturation than the track count alone.
We already own a counter-drone suite from one supplier. Can a swarm command layer sit above it, or do we start again?
The layer is designed to sit above effectors rather than replace them, fusing radar, RF and optical inputs into one track picture and cueing what is available. What that means in your case depends on the interfaces the incumbent supplier exposes, and some sealed suites expose very little. Put integration against your existing sensors and C2 into the evaluation as a tested criterion rather than a paper claim, ours included.
See: Command and control across mixed platformsIntegration rows in the comparison
Is a counter-swarm architecture worth buying for a country that has never faced a swarm attack?
Every recent conflict in and around the region has shown mass drone attack against bases, cities and infrastructure, and high-end interceptors being exhausted against low-cost threats. The capability that takes longest to build is not the effector, it is the trained command layer and the doctrine around it. Buying the architecture first and adding effectors as the threat picture hardens is the cheaper sequence, and it is how our line is structured.
See: Counter-UAS solution hubOperator training and certification
Is the swarm architecture a fielded product or a research programme we would be funding?
It is delivered as a working command layer above the interceptor family: sensors, fusion and effector allocation as one supported system, scaled from single-site protection to national coverage and sustained in-region. The honest limits are published alongside it. We do not state a simultaneous-track count or an engagement cycle time, and those gaps are listed openly on the comparison page rather than papered over.
Counter-drone swarm systems: questions
What are Counter-drone swarm systems?
Counter-drone swarm systems are Unstrat's Sky (Air Domain) capability: A layered counter-drone architecture built for the swarm threat: radar, RF and optical sensors fused with friend-foe discrimination, cueing multiple effectors from one command layer. Sits above the individual counter-UAS effectors and scales from a single site to national coverage.
How do Counter-drone swarm systems work?
Counter-drone swarm systems deliver their effect through layered radar, RF and optical detection fused into one track picture, Friend-foe discrimination across mixed friendly and hostile drone traffic and Cues net-capture, kinetic and electronic effectors from one command layer, capabilities matched to the requirement and confirmed under briefing rather than published.
Who makes Counter-drone swarm systems?
Counter-drone swarm systems 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.
Why choose Counter-drone swarm systems over a major-power alternative?
Counter-drone swarm systems are sourced from an independent, non-aligned manufacturer, so they carry no major-power disclosure rules, upgrade-locks or political ramifications. Concretely: Friend-foe discrimination: defends against the swarm without blinding your own fleet. The capability is accountable to you, not to a foreign vendor's government and its release schedule.
How are Counter-drone swarm systems procured, and where can it be exported?
Defence built for the swarm, not the single drone: layered sensors with friend-foe discrimination cueing multiple effectors from one command layer. 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-drone swarm systems are then sustained in-region by one accountable team from briefing through long-term operation.