SOLUTIONS
Drone detection, matched to the mission.
Every system is priced on its product page. There is no quote gate and no discovery call required before a number is available. What differs by environment is which configuration fits, and that is what these pages set out.
Find the situation closest to yours
Drone activity presents differently depending on where you work. A corrections officer and an event security director are watching for different behavior, on different timelines, with different consequences when something is missed. Each page below covers the operational problem in that environment, what it costs when it goes unseen, what the system delivers against it, and how to specify a configuration.
Public Safety
Airspace awareness across a jurisdiction rather than one site, deployed by the team using it.
Corrections
Continuous monitoring over facilities and yards, where drone delivery is a persistent problem.
Event Security
Temporary coverage for venues and gatherings, deployed for the event and removed afterward.
Critical Infrastructure
Persistent awareness over plants, substations, and sites that need watching around the clock.
Detect it. Identify it. Locate it. Track it.
Whatever the environment, the instrument does the same four things. It demodulates supported drone communications rather than reporting that RF energy is present, which is the difference between an alert someone has to go and investigate and a record with an aircraft attached to it.
Coverage is not limited to Remote ID. WarDragon receives Remote ID broadcasts over Wi-Fi and Bluetooth, identifies DJI OcuSync activity, and on Elite kits covers FPV control and video links and open telemetry standards through a second software-defined radio. The demodulation library grows with each software release and reaches kits already in the field.
Detection distance comes from antenna selection, height, placement, line of sight, and the RF environment rather than from the processor inside the kit. Antennas are specified per site.
What is common to all four
Whatever the environment, the decision comes down to two questions: how the sensor is deployed, and how much it needs to work on at once.
Deployment is either Mobile, a hardened carry case a team sets up on arrival and removes afterward, or Drop-In, a metal enclosure with DIN-rail mounting that fits inside equipment housings already in the field — CCTV and LPR cabinets, pole boxes, rooftop enclosures, and surveillance trailers. Both run the same platform, so an organization can operate a mix without training staff on two systems.
Capacity is either Pro, running ARM processing, or Elite, which adds x86 processing and a second software-defined radio covering FPV control and video links and open telemetry standards. The second radio is fitted at manufacture and is not a later addition. Both tiers receive the same expanding library through software updates.
Your data, on your platform.
A detection system should report into what an organization already runs rather than into software bought from the vendor who sold the sensor. Detections publish as CoT, the format TAK and TAK-compatible systems already read. Where there is no existing system, routing options are configured as part of the deployment.
What it will not do
It does not jam, disable, take control of, or otherwise interfere with an aircraft. Detection is passive; the system only listens.
It does not detect an aircraft that transmits nothing at all. A fully autonomous flight with no control link is outside the reach of RF detection of any kind, ours included. Radar is the answer to that class of aircraft.
It does not determine intent, and it does not decide anything. Output is a detection record delivered to the systems you already run.
Passive RF detection and situational awareness only. Performance varies by RF environment, antenna placement, aircraft type, and deployment configuration.