Flood warnings that keep working when the internet doesn't.
Storm Shield is a local-first community sensor network. Sensor Nodes share readings peer to peer over a Reticulum mesh, so a surge seen upstream warns the towns downstream, and residents keep their warning and evacuation plan even after the internet goes down. No outside service holds the data.
It adds local ground truth next to official information; it never replaces it.
Storm Shield was built at SwampHacks 2026 as a flood warning dashboard, demonstrated on
a replay of the 26 August 2026 Bhote Koshi flood in Nepal: a Hub and a handful of Sensor
Nodes on a laptop, a projector showing the valley map, and phones receiving Community
Warnings over the mesh. That demo is tagged
v0-swamphacks and still
runs from that tag.
An open-source sensor network you run yourself, for a farm, remote land or a stretch of river or coast, where your sensors, cameras and data stay yours. The app is becoming modular: load a Region, place a few sensors on the map, and play an Event such as a flood wave or a storm surge. Fort Myers and Hurricane Ian are next after Nepal.
The full plan is in the roadmap.
| Part | What | Stack |
|---|---|---|
node/ |
The Node service: readings, signing, the Node registry, mesh transport | Python, Reticulum |
dashboard/ |
Map dashboard for the Hub, projector and phones | TypeScript, React, MapLibre |
regions/ |
One file per place: area, water, thresholds, shelters, alert sources | JSON |
pi/ |
Raspberry Pi hotspot setup for field demos | Shell |
- Try it: clone Stormshield and run
scripts/run-demo.sh - Pick up work: open issues, one issue per pull request
- Read first:
AGENTS.mdcovers the workflow and code rules for humans and agents alike