HN Debrief

Lithuanian startup launches open-source network to detect Shahed-type drones

  • Defense
  • Hardware
  • Open Source
  • AI
  • Infrastructure

The article is about a Lithuanian startup building a distributed drone warning network from donated Android phones. The idea is simple: use phone microphones and location data to spot the distinctive engine noise of Shahed-type one-way attack drones, then aggregate many reports into an open detection layer. That makes it cheap, fast to deploy, and easy for non-specialists to join.

If you work on low-cost air defense or critical infrastructure protection, treat phone-based audio sensing as a niche layer, not the backbone. The useful question is how cheaply you can fuse audio with radar and optical systems before attackers adapt altitude, route, and volume.

Discussion mood

Interested but skeptical. People liked the low-cost, open, civilian-friendly idea, yet most doubted that ground-based phone microphones will stay useful against higher-flying Shahed variants and kept steering the conversation toward radar, multimodal sensing, and interception economics.

Key insights

  1. 01

    Higher altitude flips the sensor choice

    As Shaheds climb, the problem stops looking like acoustic detection and starts looking like straightforward radar coverage. Flying high makes the drones easier to see from farther away. It mainly helps them against short-range guns and battery-limited interceptors. If radar coverage is dense enough, the old low-altitude trick of hiding below the radar horizon no longer buys much.

    Do not evaluate an audio network in isolation from the attack profile. If the threat is shifting upward, spend on radar density and interceptor geometry first, then decide whether audio still fills a real gap.

      Attribution:
    • dghlsakjg #1
    • anovikov #1 #2
  2. 02

    Interceptor economics depend on the defended asset

    Comparing a $10k drone to a $100k kill mechanism misses the actual decision. Defenders are trading against the value of what would be hit, which can make an expensive shot perfectly rational. The problem is scale. Repeated mass attacks can still exhaust the defender unless the response becomes cheap, reusable, and operationally sustainable, which is why prop-plane interceptions and low-cost airborne hunters got so much attention.

    Model defense costs at the campaign level, not the per-shot level. If you are designing counters, prioritize reuse rate, sortie cost, and magazine depth over elegant but expendable intercepts.

      Attribution:
    • energy123 #1
    • af78 #1
    • rdtsc #1
    • dghlsakjg #1
  3. 03

    Phones are a deployment hack, not an ideal sensor

    Repurposed Android phones make sense because they are already everywhere and require almost no technical skill to field. That is a distribution advantage, not a sensing advantage. Engineers in the comments were blunt that if you actually want reliable acoustic performance, a dedicated node with controlled microphones, placement, and firmware is the better instrument.

    Separate adoption strategy from sensor strategy. Use phones when participation speed matters more than data quality, then migrate hotspots to purpose-built hardware once you know where coverage is worth paying for.

      Attribution:
    • lnsru #1
    • rdtsc #1
    • dzhiurgis #1
  4. 04

    Low-frequency pressure sensing might beat phone mics

    One of the more technical ideas was to listen for the deep pressure signature of propeller drones with differential pressure sensors rather than ordinary microphones. The claim was not that these sensors are generally more sensitive, but that they can work better in the very low-frequency range where conventional audio chains and calibration often get awkward. Another commenter backed part of that framing by explaining why pressure sensors can behave better near DC and very low frequencies, and a linked hobbyist build showed a similar setup exists in practice.

    If you pursue acoustic detection, test sensor classes before assuming a phone mic is good enough. Very low-frequency signatures may justify a custom front end even when the rest of the stack stays cheap.

      Attribution:
    • MiracleRabbit #1
    • amluto #1
    • dzhiurgis #1
  5. 05

    Open reporting lives or dies on aggregation

    The spam concern is obvious in any open sensor network. The practical answer offered here was not strong identity or perfect trust, but statistical filtering from enough independent participants. That only works once the network is dense enough that truthful reports dominate and outliers can be discarded.

    For open sensing projects, trust emerges from redundancy, not from one clean signal. Plan for quorum rules, cross-sensor correlation, and graceful degradation before inviting the public in.

      Attribution:
    • embedding-shape #1
    • tpolm #1

Against the grain

  1. 01

    Audio and vision still matter below radar’s comfort zone

    The strongest pushback to the radar-first view was that other drone classes are already exploiting places radar handles poorly, especially very small low-altitude systems. That does not change the article's focus on Shaheds, but it does undercut any neat claim that radar is the universal answer. Optical and acoustic sensing will stay in the stack because some threats are only visible at the last moment and need layered coverage.

    Avoid building around a single sensing doctrine. Even if radar is the main answer for Shaheds, leave room in your architecture for optical and acoustic feeds aimed at smaller and lower threats.

      Attribution:
    • energy123 #1
    • dghlsakjg #1
    • MobiusHorizons #1
  2. 02

    Open-source radar projects may be junk

    A commenter challenged the idea that open-source radar is an easy upgrade path by calling out one cited phased-array GitHub project as likely fake, commercial camouflage, or worse. The specifics were not verified, but the broader warning is sound: defense-flavored open hardware attracts vaporware and dubious provenance much faster than ordinary maker projects.

    Vet claimed radar alternatives aggressively before treating them as buildable options. In this area, repository polish is weak evidence compared with traceable hardware, believable test data, and provenance.

      Attribution:
    • kamranjon #1
    • kklisura #1

In plain english

DC
Direct current, used here to mean signals at or near zero frequency rather than ordinary audio frequencies.
ESP32
A cheap, widely used microcontroller chip with built-in Wi‑Fi and Bluetooth, often used in embedded and Internet of Things devices.
radar horizon
The distance limit at which radar can detect low-flying objects because the Earth's curvature blocks line of sight.
Shahed
A family of Iranian-designed one-way attack drones, often used for long-range strikes on infrastructure and cities.

Reference links

Radar and defense systems

Sensor and detection experiments

Questioned or dubious radar vendors

Politics and side debates