SonDehub Geofence Guard (SGG)

Who it's for

Amateur radio operators and hobbyist weather-balloon trackers who host SondeHub receivers but use manual, fragile local software overrides today to mask their home addresses.

The problem

Legal and personal safety: raw receiver uploads inadvertently leak the operator's precise geographic location (and occasionally home IP address) to public global maps, creating high doxxing and physical security risks.

How to build it

A Docker-based proxy daemon with a local web dashboard that sits between the receiver software (e.g., auto_rx) and the public SondeHub API, allowing real-time geofence masking.

How it makes money

Hobbyist operators pay $15 one-time for a pre-configured Raspberry Pi SD card image, or $3/month for a hosted configuration-management bridge that simplifies multi-receiver setups.

Why it doesn't exist yet

Incumbent aggregator platforms prioritize maximum data coverage and precise crowd-sourced multilateration calculations, giving them no incentive to assist users in withholding high-accuracy raw telemetry. The indie gap is a local-first privacy gate that processes the stream at the edge before transit.

First users

Operators on hobbyist forums (SondeHub community, RTL-SDR subreddits, and amateur radio boards) who want to contribute data but refuse to leak their home coordinates to public maps.

Build size

1 person x 4 weeks. Includes a Go-based proxy daemon, a lightweight SQLite configuration storage, a Leaflet-based local web UI for geofence drawing, and auto-generated systemd units.

Biggest risk

The platform operators (SondeHub/SprocketFox) could update their APIs to require raw unredacted payloads, making user-side obfuscation cause submission rejection.

Conditions for a hit (all 3 required)

• A web-based interactive map UI that allows users to draw a precise polygon 'no-publish' geofence around their receiver coordinates.
• A real-time telemetry interceptor that strips metadata or shifts coordinates by a randomized offset for any receiver packets originating within the geofenced zone.
• A local diagnostic page showing a live counter of packets processed, packets masked, and an active log of outbound payload payloads.

How it's judged (in 6 months)

GitHub 300 stars or 5 independent community-forum mentions of 'Sondehub Geofence Guard' / 'SGG' as an operational mitigation on radio-tracking boards.(judgment date 2027-02-20)

AI self-confidence 75/100 — self-reported likelihood of meeting the criterion, not a business success rate