Author: ghli@luotwo.com

  • AeroScope Alternatives in 2026: What the DJI-Only Gap Means for Buyers

    AeroScope Alternatives in 2026: What the DJI-Only Gap Means for Buyers

    DJI’s AeroScope is the most widely deployed drone detection system in the world, and in 2026 it is still the first product many buyers evaluate. This article is our working notes on how it works, what it covers, and what the alternatives look like — written for buyers comparing options, with every claim sourced.

    What AeroScope actually does

    AeroScope is a passive RF receiver. It listens to the communication link between a DJI drone and its remote controller and decodes it: position, altitude, speed, direction, serial number and take-off location, per DJI’s product page, with identification in as fast as two seconds. DJI claims monitoring of up to 50 km under ideal conditions; integrator deployments typically land between a 3-mile and 16-mile radius depending on antenna configuration. (Sources: dji.com/aeroscope; airsight.com deployment data — vendor-reported.)

    The limitation that decides everything

    AeroScope decodes the DJI protocol. That means it sees DJI drones — and nothing else. Critics including AeroDefense have made this point for years: DIY builds, other manufacturers, and modified aircraft are invisible to it. DJI’s counter-argument is market share; roughly nine in ten consumer drones are DJI, so covering DJI covers most of the hobby traffic. Both things are true, and which one matters depends on your threat model. A prison worried about contraband drops flown on a 500-euro home-built quad is not protected by a DJI-only sensor.

    How we evaluated alternatives

    Method, stated up front: we have not run a head-to-head field trial of every product named here. This comparison is built from published vendor material, regulatory filings and the evidence labels on our receiver comparison page — checked September 2026. Where a number is vendor-reported, treat it as a claim, not a measurement.

    The alternatives, by detection layer

    • Remote ID receivers — receive the standardised broadcast that most drones sold since 2024 must carry (US Part 89, EU direct remote ID). Brand-agnostic: a non-DJI drone that broadcasts is visible. Budget: roughly $129–2,500 per node.
    • RF spectrum sensors — detect any transmitting drone, including FPV builds and modified aircraft, across 2.4/5.8 GHz and beyond. The trade is cost ($3,500–15,000) and a higher false-alarm rate on shared bands.
    • Radar — sees aircraft that transmit nothing at all, at the highest cost and integration effort. Beyond our comparison scope; we refer to specialists.

    Where buyers go wrong

    Three failure patterns we keep seeing. First, buying for the drones that exist today and not for the one that shows up next month — a DJI-only sensor and a Remote ID receiver fail in opposite ways. Second, taking the 50 km figure as a deployment figure; ideal conditions do not survive a prison fence line. Third, skipping the walk-test: no coverage claim survives contact with your actual site.

    If your concern is…Best-fit layerWhy
    DJI hobby traffic near an airportDJI-protocol or RID receiverCheapest coverage of the dominant fleet
    Non-DJI and unknown dronesRID receiverStandardised broadcast, brand-agnostic
    FPV / modified / silent aircraftRF spectrum sensorDetects the transmission, not the paperwork
    Full perimeter, no assumptionsRID + RF combinedLayers cover each other’s blind spots

    Next step: the receiver comparison lists candidates with sources and dates, and the free screening tells you within one business day which layer your site actually needs.

    Content last reviewed: 2026-09-11. Sources: dji.com/aeroscope (vendor-reported); airsight.com; AeroDefense blog; COPTRZ market-share commentary.

  • Drone Detection for Prisons in the UK: A Complete, Honest Guide

    Drone Detection for Prisons in the UK: A Complete, Honest Guide

    Drones over UK prisons stopped being a curiosity years ago. This guide collects what is publicly known about the scale of the problem, what detection technology can and cannot do about it, and how we think a prison should approach its first deployment — with the honest caveats in place from the start.

    The scale, in numbers we can source

    The UK government has reported 1,712 drone incidents at prisons in a single year — a 43% rise on the previous period — covering sightings, disruptions and confirmed contraband attempts. (Source: GOV.UK prison drone statistics; vendor- and government-reported, checked September 2026.) Behind the number sits a simple economics problem: a drone can deliver contraband worth thousands of pounds in a thirty-second hover, and the alternative — corrupted staff or elaborate smuggling — costs more and carries more risk for the criminals.

    What detection can actually see

    A prison is a mixed-threat airspace, and that is the crux. Machines flown by organised groups are often home-built FPV quads: no Remote ID broadcast, no registration, nothing a standard receiver can hear. Consumer drones doing opportunistic flights — photography, curiosity — usually do broadcast. Our working numbers, all vendor-reported and documented on the receiver comparison: Remote ID receivers start around $129 per node; RF-spectrum sensors, which hear the FPV traffic, start around $3,500. Radar exists for full coverage and costs an order of magnitude more.

    How we evaluated approaches

    We have not installed detection at a prison ourselves — our role is selection advisory, and this guide is a synthesis of published incident data, vendor documentation and the survey discipline described in our site survey checklist. Everything we recommend below is buildable by an in-house team; the pilot criteria are the same ones we would accept in a procurement.

    A staged deployment that holds up

    • Phase 1 — baseline (weeks 1–4): one RID receiver on the main approach, logging 24/7. Cost: low. Purpose: learn what your airspace actually contains — most sites are surprised.
    • Phase 2 — RF layer (months 2–3): add RF-spectrum monitoring on the approach corridors if the baseline shows silent traffic or if the threat assessment says it will.
    • Phase 3 — response integration: alerts into the existing control room workflow, correlation across nodes, and a documented protocol for what happens on a confirmed detection.
    • Phase 4 — validation: an authorised walk-test with a known drone on a planned grid, detection logged against GPS truth, gaps on the map. No deployment is “done” without it.

    The failure modes to design out

    Detections without a response protocol become noise within weeks. Systems bought on coverage promises collapse at the first wall. Budgets that cover hardware but skip validation leave you unable to prove the system works on the day it matters. And a procurement that ignores the silent-FPV problem — because a datasheet said “drone detection” — is the most expensive failure of all, because it feels solved until the night it is not.

    Where to go next: our prison detection page carries the full scenario breakdown, the deployment guide covers siting and validation, and the free screening is the fastest way to test our judgement before any money moves.

    Content last reviewed: 2026-09-11. Sources: GOV.UK prison incident statistics (1,712 / +43%); vendor documentation, checked September 2026. Not legal advice.

  • RID vs RF vs Radar: Choosing Detection by Site Type, Not by Datasheet

    RID vs RF vs Radar: Choosing Detection by Site Type, Not by Datasheet

    “Which drone detection technology should I buy?” is the wrong first question. The right one is “what does my site need to see, and what can it afford to miss?” This article walks through that decision site-type by site-type, with budgets, evidence labels and the combinations that actually make sense. It goes deeper than our earlier primer on the three technologies — this one is for people close to a purchase.

    The three layers, one line each

    Remote ID (RID) receivers hear the standardised broadcast that most drones sold since 2024 must carry: identity, position, take-off point. RF spectrum sensors hear any transmitter — including FPV builds and modified aircraft that broadcast nothing. Radar sees airframes whether they transmit or not, at the highest cost. Prices we quote across the site, all vendor-reported: RID $129–2,500 per node, RF $3,500–15,000, radar from roughly $50,000 upward for a usable installation.

    How we structured this comparison

    Method: we match detection layers against site types using three inputs — the threat models that dominate each site category, the published capability and cost data on our receiver comparison, and the survey discipline in our checklist. We do not score radar (outside our advisory scope) beyond noting where it belongs. Treat every budget as vendor-reported; treat the mapping as our judgement, not physics.

    Site type by site type

    • Prisons and secure facilities — the confirmed threat is contraband drops, often flown on home-built quads. RID alone undercovers; the RF layer is not optional. Start RID (cheap baseline), add RF on approach corridors.
    • Airports and airspace — the fleet is mostly compliant consumer and commercial aircraft. RID receivers carry most of the load; RF and radar are regulator-grade additions. Your aviation authority will have opinions — involve them early.
    • Events and stadiums — short deployments, dense RF, heavy media drones that do broadcast. RID-first works; RF earns its cost only for A-list threat profiles. Renting beats buying for one-off events.
    • Critical infrastructure — mixed fleet, long perimeter, 24/7 operation. The RID + RF combination is the honest default; budget for two nodes minimum and a validation walk-test.
    • Law enforcement — you need identification for response, which makes RID’s decoded identity (serial, operator position) uniquely valuable; RF adds the silent-aircraft picture. Evidence handling rules push toward logged, timestamped data — both layers provide it.

    Where buyers go wrong

    The recurring failure is buying the impressive layer instead of the correct one: radar dreams on a RID budget, or an RF sensor deployed where every detection is a false alarm because the site’s own Wi-Fi drowns 2.4 GHz. The second failure is skipping phase zero — two weeks of baseline logging answers more questions than any datasheet.

    SiteStart withAdd ifSkip for now
    PrisonRID baseline + RFRadar at state levelRadar-only
    AirportRID receiver gridRF for known silent trafficDIY anything
    EventRID (rented)RF for A-list eventsPurchases
    InfrastructureRID + RF two-nodeCorrelation serviceSingle-layer promises
    Law enforcementRID for identificationRF vehicle unitFixed install before pilots

    Where to go next: run your site through the survey checklist, compare hardware on the receiver table, or hand the question to us with the free screening.

    Content last reviewed: 2026-09-11. Budgets are vendor-reported, checked September 2026. This is advisory content, not a quotation.

  • Is It Legal to Detect Drones Over Your Property? The 2026 Map

    Is It Legal to Detect Drones Over Your Property? The 2026 Map

    “Can I legally detect drones flying over my property?” We get this question weekly, and the short answer in the US, UK and EU is: receiving is fine, jamming is a crime, and the data you log has its own rules. This article maps the lines — it is not legal advice, and the regulations deserve a lawyer’s read before you act on them.

    Receiving is (mostly) legal

    Passive detection — listening to what a drone broadcasts or transmits — is generally lawful. Remote ID broadcasts are, by design, public signals: regulators built the system precisely so that third parties could receive them. A RID receiver or an RF sensor that only listens stays on the right side of interception law in the jurisdictions we advise on. Radar is different in kind: transmitting energy into the airspace can trigger aviation and planning rules that a receiver never touches, which is one more reason it sits outside our advisory scope.

    Jamming is a crime — full stop

    Everything that transmits to stop a drone — jammers, spoofers, force-landing devices — is illegal to operate for almost everyone in the US, UK and EU. In the United States the FCC treats jamming as a violation of the Communications Act with substantial penalties; in the UK the Wireless Telegraphy Act does the same work. Only a handful of government agencies hold exemptions. Buyers frequently ask us “and then it lands it, right?” — and the answer is that the kit which does that is not something a private site can legally switch on. (Sources: FCC jammer enforcement guidance; Ofcom/WTA framework.)

    The data you log is the quiet trap

    A detection log is not anonymous. A Remote ID record ties a serial number to a position and a timestamp; correlated over time, it traces an individual pilot’s home and habits. Under GDPR in the EU, and under comparable privacy expectations elsewhere, that makes detection logs personal data — with retention limits, access control and a lawful basis attached. We say this as advisers, not lawyers: the detection project that forgets data protection usually discovers it in the worst possible meeting. Our own handling is published on the privacy page.

    How we evaluated the rules

    Method: this summary rests on the published positions of the FCC, Ofcom and EU data-protection guidance, checked September 2026, plus the Regulatory texts themselves (14 CFR Part 89 for the US, the UK CAA framework for Britain). We are technologists, not a law firm — where your deployment touches aviation authority permissions, security-of-persons exemptions or employment law, get professional advice.

    ActionUSUK / EU
    Receiving broadcasts (RID/RF listening)Generally lawfulGenerally lawful
    Jamming / spoofing / force-landingIllegal (FCC)Illegal (Ofcom / WTA)
    Logging detection dataFine; mind data carePersonal data under GDPR
    Sharing logs publiclyCarefulLawful basis required

    Where to go next: the survey checklist includes the data-handling check most deployments skip, and the free screening is the place to surface compliance questions before they become procurement questions.

    Content last reviewed: 2026-09-11. Sources: FCC jammer guidance; Ofcom / Wireless Telegraphy Act framework; 14 CFR Part 89; GDPR guidance. Not legal advice.

  • US Army Buys the MOTH Tactical Spectrum Analyzer: 450 g, 5 MHz–6 GHz

    US Army Buys the MOTH Tactical Spectrum Analyzer: 450 g, 5 MHz–6 GHz

    The US Army has committed up to $99 million to a spectrum analyzer that weighs less than a water bottle. The contract went to Heaviside Industries Inc. of Marina del Rey, California, and covers procurement, deployment, upgrades and support for the company’s MOTH tactical spectrum analyzer. The award was published on the Army contract list on August 27, 2026, and runs through August 27, 2031.

    MOTH tactical spectrum analyzer front view showing real-time signal strength across 5.8 GHz, 2.4 GHz, 450 MHz, 148 MHz and L5 bands

    What the MOTH actually does

    The MOTH is a passive receiver. It does not transmit and it does not interfere with anything — it listens. Working from published vendor material, it monitors RF activity across roughly 5 MHz to 6 GHz and helps the operator decide whether something abnormal is on the air: the frequency, signal strength, direction and waveform character of each emitter. Drone control links, two-way radios, anything that transmits shows up.

    • Coverage: approx. 5 MHz – 6 GHz (vendor-reported)
    • Weight and size: 0.99 lb (≈450 g), 5.78 × 3.3 × 1.8 in (vendor-reported)
    • Carry: in hand, or strapped to a vest
    • Built in: GPS, vibration alerts, a direction-finding mode, real-time spectrum display
    • Interop: connects to ATAK, so RF observations land on the tactical map
    • Environment: IP67, −10 °C to +55 °C (vendor-reported)
    Rear view of the MOTH spectrum analyzer showing the battery module with LED indicators, USB-C port and dual antennas

    A note on evidence: we have not tested this unit. Every figure above is vendor-reported or taken from the contract announcement, checked September 2026.

    Is it just a ruggedized RTL-SDR?

    Fair question, and the honest answer is “partly”. Think of the MOTH as what the RTL-SDR ecosystem looks like after it grows up and joins the infantry. Both are wideband receivers that make the invisible spectrum visible. An RTL-SDR dongle is an exploration tool — cheap, ideal for learning radio, fine for scanning broadcast, airband, ham and digital signals. The MOTH packs wideband reception, a real-time spectrum display, signal analysis, direction finding, GPS and a tactical data interface into one sealed unit.

    The difference that matters is the last step. The MOTH is built so a non-specialist can read the result quickly: is this band abnormal, where is the emitter, does that waveform look like a drone link. An RTL-SDR gives you a waterfall and expects you to know what to do with it.

    Who carries one

    Not everybody. The MOTH will not be issued like a personal radio. It is a portable electronic-reconnaissance asset, used to find, identify and locate transmitters — an enemy drone link, a concealed radio. Expect it with scouts, special operations forces, electronic-warfare personnel and squad leaders first, not one per soldier.

    The price, and what is in the box

    The MOTH is also on the civilian market: Lumenier lists it at $4,950 (checked September 2026). The set includes the analyzer, two batteries, a USB-C charger, a vest-style pouch, a protective case and a pair of antennas — one for the low band, one for the high band.

    MOTH spectrum analyzer kit with antennas, battery modules and vest pouch packed in a protective case

    What this means if you are buying detection equipment

    We have not tested the MOTH and this article is contract reporting plus published specifications — nothing more. Still, the purchase confirms a pattern we keep explaining to clients: professional buyers treat RF-spectrum listening and Remote ID reception as two separate layers, and budget for them separately. A spectrum analyzer hears that something is transmitting; a Remote ID receiver tells you who it is. Most sites we advise end up needing both, in that order.

    If your concern is…RID receiverRF spectrum analyzer
    Drones that broadcast Remote IDSees them — ID and positionSees a signal, no identity
    FPV, modified or silent aircraftBlindDetects the transmission
    False alarmsLowHigher — 2.4/5.8 GHz bands are shared with Wi-Fi
    Typical budget$129–2,500$3,500–15,000

    If the MOTH contract says anything to a non-military buyer, it is this: passive RF listening has moved from a hobby project to standard procurement. The same two-layer logic applies at prison fences, airports and event perimeters — at civilian budgets.

    Go deeper: how RF-spectrum detection works, in plain terms → Spectrum detection explained. Shortlist hardware → receiver candidates, with sources and dates. Not sure which layer your site needs? Start with the free screening, answer within one business day.

    Content last reviewed: 2026-09-11. Sources: US Army contract announcement (August 27, 2026); Heaviside Industries and Lumenier public product material (vendor-reported).

  • Remote ID Receiver vs RF Detector vs Radar: Which Do You Actually Need?

    Remote ID Receiver vs RF Detector vs Radar: Which Do You Actually Need?

    Buying guide · Reviewed 2026-09 · Next review 2027-03

    Remote ID Receiver vs RF Detector vs Radar: Which Do You Actually Need?

    Three technologies, three different jobs. In the site requirements we have reviewed, most buyers sized the wrong layer first — usually the most expensive one.

    What each technology actually sees

    A Remote ID (RID) receiver listens to the radio broadcast that most drones sold since 2023 must transmit by law under FAA Part 89, EU Delegated Regulation 2019/945 and equivalent rules: a serial number, position, altitude, velocity — and, the part that matters to investigators, the location of the pilot at take-off. A receiver turns that broadcast into a logged, timestamped record. It hears nothing from an aircraft that does not broadcast.

    An RF-spectrum detector scans the airwaves themselves. It can spot the video downlink or control link of any transmitting drone — including FPV rigs and modified aircraft that stay silent on RID. The trade-off is identity. Depending on the protocol, it may decode the drone model; often it can only tell you that something transmitting is out there, in a band shared with Wi-Fi, Bluetooth and everything else in a busy RF environment. False alarms are the operational cost you accept for that wider view.

    Radar bounces a signal off the airframe. It measures position and movement precisely, works against aircraft with no emissions at all, and covers large areas from one installation. It cannot tell you who is flying, it is the most expensive option by a wide margin, and siting, processing and regulatory review make it a facility-scale project rather than a purchase.

    The question that decides everything

    Before comparing products, answer one question honestly: what does your site actually face? A correctional facility dealing with organised contraband drops faces compliant consumer drones flown at night from public land — RID sees those. A site concerned about a skilled FPV operator filming a fenced compound faces aircraft that may never broadcast — RID alone will not see those, and no honest vendor will tell you otherwise. Most sites we review face the first threat but budget as if they face the second, or the reverse.

    There is also a legal dimension that surprises buyers: counter-drone measures — jamming, spoofing, taking an aircraft down — are illegal for private operators in most jurisdictions, including around critical infrastructure in many cases. Detection is what you are buying. Everything on this site assumes that boundary.

    The honest comparison

    RID receiverRF detectorRadar
    SeesBroadcasting aircraft onlyAny RF-emitting droneAnything in coverage, regardless of emissions
    IdentifiesSerial, model, pilot take-off pointModel at best; often just presenceTrack only
    False alarmsLow — identity is verifiableHigher — 2.4/5.8 GHz bands are shared with Wi-FiLow to medium — birds, clutter
    Evidence valueStrong — logged ID plus pilot locationWeak unless the protocol decodesTrack data, no identity
    Budget$129–2,500 ◐ vendor-reported$3,500–15,000 ◐ vendor-reported$100K+ ◐ vendor-reported
    Legal statusPassive receive — permittedPassive receive — permittedPermitted; siting and aviation review may apply

    Budget rows are list-price ranges compiled from vendor publications, checked September 2026 — vendor-reported, not measured by us. Real quotes move around these numbers; demand written test conditions before comparing.

    Four questions that decide it

    1. Does your threat broadcast RID? Consumer and commercial aircraft from the major brands generally do, because the law requires it. Home-built FPV rigs generally do not. If you do not know, an RF-spectrum survey answers it faster than a datasheet.
    2. Do you need the pilot’s location, or just the alert? If evidence matters — prosecution, internal investigation, regulator follow-up — RID is the only low-cost layer that provides it.
    3. What is the perimeter? A single building may be covered by one portable receiver. Kilometres of fence line multiply nodes — and make radar’s per-site economics look different.
    4. What happens after detection? If the answer is “call security”, presence-only alerting may be enough. If the answer is “prosecute”, you need RID logs with timestamps.

    What RID cannot do

    Say it plainly: an RID receiver cannot see an aircraft that does not broadcast, and no detection technology can stop an aircraft in flight. Jamming and take-down measures are illegal for private operators in most jurisdictions our clients work in. Detection is about knowing what is overhead and being able to act on the ground — not about knocking anything out of the sky.

    Method and limitations

    Budget figures are vendor-reported list-price ranges checked September 2026. Our own field validation of detection distances is in progress; until we publish it as measured data, treat every range claim — ours included — as a claim. The comparison table above is regenerated whenever we re-check a figure, and the candidate version lives on the Receivers page with per-row sources.

    Still not sure which layer fits your site?

    Send us the requirement. We will tell you — free of charge, within one business day — which layer answers it, and which one you can skip.

  • Remote ID Receiver Buying Checklist

    Remote ID Receiver Buying Checklist

    Buying guide · Reviewed 2026-09 · Next review 2027-03

    Remote ID Receiver Buying Checklist

    Seven checks to run before money moves. Each one exists because a procurement somewhere failed without it.

    Run these checks in order

    1. Confirm your aircraft broadcast Remote ID

    Most consumer and commercial drones from the major brands sold since 2023 broadcast Remote ID, because the law requires it. Retrofit broadcast modules exist, but add cost, weight and a battery to manage — and some stripped-down FPV builds never transmit. If your threat model includes modified aircraft, no RID receiver will see them, and you should be planning an RF-spectrum layer instead of comparing RID units.

    2. Demand the test conditions behind every range figure

    “5 km range” means nothing without four facts: which aircraft was transmitting, which band (2.4 GHz BLE versus Wi-Fi NAN behave differently), what RF interference was present, and what decode success rate counted as “received”. Ask the vendor for those four items in writing. If the answer is a datasheet screenshot, treat the number as marketing.

    3. Get one real output sample before the demo

    A single anonymised JSON detection message tells you more than a brochure: the field names, the timestamp format, whether the pilot location is included, and how the unit handles multiple aircraft at once. Vendors who cannot produce one sample have a demo, not a product.

    4. Check what still works offline

    Local logging, local alerting, data export without a cloud account — these are the functions that keep working when the vendor’s platform does not. Cloud-only logging is a dependency you are agreeing to, and it outlives any subscription dispute.

    5. Verify the integration interface, not the integration promise

    “API available” and “webhooks supported” appear on every datasheet. Ask for the endpoint documentation and one example payload for the exact fields your control room consumes. Ten minutes with the real documentation prevents the most common post-purchase disappointment.

    6. Confirm which standards the unit decodes

    ASTM F3411 covers most Western-market aircraft. GB 42590 covers Chinese-market aircraft — including grey-import units common in some regions — and few Western receivers decode it. If your airspace includes such aircraft, multi-standard decoding is the specification that matters most.

    7. Agree the warranty path in writing

    Who pays return shipping, what the replacement turnaround is, and how long firmware updates continue. On imported hardware the answers vary from excellent to nothing — and the difference shows up exactly when you need support.

    Red flags we see in vendor quotes

    • Range claims with no aircraft, band, or decode success rate stated
    • “Detects all drones” — no such product exists; every technology has blind spots
    • Certificates listed for a product family, not the specific model quoted
    • Cloud features quoted as included, with no note about what happens if the subscription lapses

    Every specification on our candidate table carries an evidence label and a check date. Claims we could not verify are marked vendor-reported — the same scepticism you should apply to any datasheet, including ours.

    The three questions every evaluation visit should answer

    If a vendor demo is part of your evaluation, resist the temptation to watch the screen. Walk the perimeter instead, and check three things. First, where is the receiver relative to the flight path — was the demo flown on the vendor’s terms or yours? Second, what happens to the log when the demo ends — can you export it, or does the evidence leave with the salesperson? Third, which alerts arrived late — ask the unit itself, by checking timestamps against the flight you watched. A vendor comfortable with these questions has been tested before. One that steers you back to the datasheet has told you something too.

    Budget note: procurement files we review often compare an RID receiver’s purchase price against nothing. The fair comparison is against the cost of one incident without detection — a lost case, an unresolved complaint, a regulator asking what you knew. The right layer is the cheapest one that answers your threat; the wrong layer at any price is expensive.

    Want a second pair of eyes on a quote?

    Our $199 selection report applies this checklist — and the checks vendors hope you forget — to your specific shortlist, with sources and dates on every line.

  • Remote ID Receivers Compared: Evidence, Sources, Dates

    Remote ID Receivers Compared: Evidence, Sources, Dates

    Market review · Reviewed 2026-09 · Next review 2026-12

    Remote ID Receivers Compared: Evidence, Sources, Dates

    How we compiled the candidate table, what the September 2026 market looks like from the buyer’s side, and where every number on it came from.

    Our method, stated plainly

    We collect list prices and specifications from vendor publications and record the date we checked each value. Anything we have not measured ourselves is labelled vendor-reported. Claims from operator discussions enter as community evidence only when we consider the source credible — and even then we say so. When a vendor will not support a claim with test conditions, the claim stays in the table but the label tells you what it is worth.

    No referral arrangement existed with any manufacturer listed when this was compiled. When one exists, the disclosure appears on the comparison page before your details move anywhere.

    What the September 2026 market looks like

    Portable RID receivers. The specialist end is dominated by Dronetag’s RIDER ($1,099) and Scout (€2,499) — solid engineering, ASTM-focused, priced like the niche hardware it is. Both are vendor-reported figures; neither has been field-tested by us yet.

    Module and fixed-site options undercut the portables: DroneScout’s Bridge module sits at €129 for experimenters and its fixed receiver at €950 for small sites. The Polaris Hobit NT module reads GB 42590 alongside ASTM, ASD-STAN and DJI formats at $2,588 (MOQ 1) — the multi-standard option that matters when Chinese-market or grey-import aircraft are part of your threat picture.

    The RF-spectrum layer starts around $3,500 (Fanshuang handheld, list) and climbs toward $15,000 for multi-band fixed units. Its selling point is coverage of silent aircraft; its cost is false-alarm handling and weaker identity.

    Open-source builds — WarDragon and AryaOS on roughly $300–500 of SDR hardware — sit outside the commercial table but inside an honest comparison. They work. They also require Linux, SDR and decoding skills, and nobody answers a support line when decoding drops in a crowded RF environment. Right for technical teams; wrong for operations that need accountability.

    What we could not verify

    • Real-world decode success rates under RF congestion — no vendor publishes them with test conditions
    • Actual detection distances for the listed units in suburban terrain — our field programme is in progress
    • Firmware update commitments beyond what is written in current vendor documentation

    An honest gap in the table is worth more to a procurement file than a confident guess. That is why the gaps are listed.

    How to read the table like a procurement officer

    Three habits separate a useful comparison from marketing. First, read the evidence label before the number: a 5 km claim labelled vendor-reported has survived nothing, while a 2 km claim labelled measured comes with conditions you can repeat. Second, check the date — firmware moves decode capability between product generations, and a 2024 test of a 2026 firmware build is history, not evidence. Third, match the form factor to the mission before matching the price: a portable receiver for a vehicle patrol and a fixed node for a fence line are different tools that happen to share a category name.

    When a candidate matters to your decision, ask the supplier three things in writing: the exact firmware version the specification describes, the aircraft and conditions used for the range claim, and whether the warranty covers firmware-related faults. The answers — or the silence — belong in your procurement file next to our table.

    Turn the market overview into a shortlist for your site.

  • RID vs Spectrum: What Each Layer Actually Detects — and What Each Misses

    RID vs Spectrum: What Each Layer Actually Detects — and What Each Misses

    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.

    Which layer does your site actually need?