Two-layer detection · Reviewed 2026-09 · Next review 2027-03
RID vs Spectrum: What Each Layer Actually Detects — and What Each Misses
Three real intrusion scenarios, run through both detection layers. The gaps are the point.
Scenario 1: A compliant drone over your site
A recent-model DJI or equivalent aircraft crosses your perimeter. The RID layer sees it from broadcast start: serial, model, position, altitude and the pilot’s take-off point, logged with timestamps. The RF layer also sees it — as one more transmitter in a busy band. RID alone is enough here, and it is the layer that produces usable evidence.
Scenario 2: A modified aircraft that broadcasts nothing
An FPV rig with the RID module stripped crosses low and fast. The RID layer hears nothing — there is nothing to hear. The RF layer catches the video downlink and raises the alert, possibly identifying the frequency band; identity evidence is thin to nonexistent. This is where the RF layer earns its cost — and where a buyer who only compared RID units discovers the gap after the incident.
Scenario 3: A busy RF environment
An industrial site next to a Wi-Fi dense zone. The RF layer fires constantly on shared-band noise — laptops, cameras, IoT. The RID layer stays quiet because most of those transmitters are not drones. Without the RID layer, the RF layer’s false-positive burden lands on your operators, and alert fatigue does the rest. Chained together, the RF alert is filtered by one question: is anything out there broadcasting an RID identity?
How the layers chain together
A practical deployment puts the RF layer on watch and the RID layer on identification: RF says something is flying, RID says whose it is and where it launched. Integration matters more than either unit’s datasheet — if the two layers do not deduplicate alerts in your control room, your operators will disable one of them within a month.
Budget split, honestly stated
- RID only — $129–2,500 ◐ vendor-reported: right when your threat is compliant aircraft and evidence matters
- RID + RF combination — $8,000–20,000 ◐ vendor-reported: right when non-broadcasting aircraft are a proven concern, not a hypothetical
- Enterprise multi-sensor — $50,000+ ◐ vendor-reported: radar and counter-UAS integration, a different procurement entirely
The open-source route, for completeness
WarDragon and AryaOS approximate the RF layer on $300–500 of SDR hardware, and DroneScout’s Bridge module does the same for RID. Respectable for labs and technical teams; impractical where someone must sign for the result and a support line must answer when decoding drops. We document these builds because understanding them makes you a better buyer of either layer.
Method and limitations
Layer capabilities and budget figures summarise vendor documentation and community reports reviewed September 2026 — vendor-reported, not measured by us. Our own two-layer field validation is in progress and will be published as measured data, including the failure cases. Jamming and take-down are outside this discussion entirely: they are illegal for private operators in most jurisdictions and we do not advise on them.
Integration questions that decide whether the combo works
Buying both layers does not automatically give you a combined system. Before the purchase order, put four questions to whoever will integrate them. Do the two layers share a time source, so alerts can be correlated after the fact? Does the RID layer receive the RF layer’s detections, or do operators read two screens? Is there one export that covers both, for evidence? And who maintains the feature library on the RF side — the buyer or the vendor — and for how long? Written answers to these four questions are worth more than a second demo.
We ask them during the $199 selection report whenever a combination is on the table, because a two-layer system that does not talk to itself is two half-systems with one invoice.