Awesome Resilient Communication [](https://awesome.re)

September 5, 2026 · View on GitHub

A curated list of open protocols, applications, hardware, and resources for communication during internet shutdowns, disasters, censorship, and off-grid operation.

Scope. This list is about resilient communication: technologies that keep people able to exchange messages, files, and situational information when normal infrastructure is unavailable, degraded, or hostile. Every software entry has a working open-source implementation; resilience must be part of the architecture, not a marketing claim.

Out of scope:

  • Cryptocurrency- and token-dependent projects, even connectivity-themed ones.
  • AI tools and agent frameworks.
  • Closed-source commercial products and conventional VPN services.
  • Encrypted messengers that depend on centralized infrastructure (Signal, WhatsApp and similar are excellent tools, but they stop working exactly when this list becomes relevant).
  • Military-only technology.

Please read CONTRIBUTING.md before submitting a project.

Entries marked Dormant still work but have seen no meaningful development for roughly 2 years; entries marked Experimental are promising but not yet mature enough to rely on; dead projects live in the Graveyard section at the bottom.

How to read this list. "Resilient" is not one property. These six often get conflated:

  • Confidentiality — outsiders cannot read your messages. (encryption)
  • Anonymity — outsiders cannot tell who is communicating. Encryption alone does not provide this.
  • Metadata resistance — outsiders cannot map who talks to whom, when, or how often. Rarer than anonymity; most "private" tools do not have it.
  • Censorship circumvention — communication works despite an adversary filtering a functioning internet. Decentralization alone does not provide this.
  • Infrastructure independence — communication works with no internet, cell service, or servers at all.
  • Disruption tolerance — communication survives intermittent, high-latency, or partitioned links by storing and forwarding.

No single tool covers all six — the Resilience at a Glance matrix below shows how representative tools spread their effort across them.

Inclusion is not a security endorsement. Assume a project has had no independent security audit unless the entry names one. If your safety depends on a tool, evaluate your own threat model first — EFF's Surveillance Self-Defense, listed under Guides and Threat Models below, is a good starting point — and prefer audited tools with documented limitations over impressive claims.

Contents

Resilience at a Glance

A few representative entries — deliberately not all of them — classified against the six properties above, to show how differently "resilient" tools spread their effort. The six properties cluster into two broad design goals. Tools built for hostile but functioning networks — confidentiality, anonymity, metadata resistance, censorship circumvention — assume the internet works and an adversary watches or filters it; Tor-based messengers live here. Tools built for broken, absent, or intermittent networks — infrastructure independence, disruption tolerance — assume connectivity itself has failed; mesh radio and store-and-forward systems live here. The two groups are not exclusive: Briar deliberately spans both, and Reticulum brings strong encryption to infrastructure-free links.

Read the matrix by failure mode, not as a ranking: internet fully down → infrastructure independence; internet up but filtered → censorship circumvention; connectivity intermittent → disruption tolerance. A ✗ usually means a system never set out to provide that property, and a ✓ marks a design goal, not a security guarantee — the audit caveat above applies to every cell. Rows run from hostile-network tools to broken-network tools.

SystemConfidentialityAnonymityMetadata resistanceCensorship circumventionInfrastructure independenceDisruption tolerance
PsiphonN/A✗✗✓✗N/A
Ricochet Refresh✓✓✓◐✗✗
Cwtch✓✓✓◐✗◐
Briar✓✓✓✓✓◐
Bitchat◐◐✗✗✓✓
qaul✓✗✗✗✓✓
Meshtastic◐✗✗✗✓◐
Reticulum / LXMF✓◐◐✗✓✓
NNCP✓✗◐✗✓✓
Syncthing✓✗✗✗◐◐
Winlink✗✗✗✗◐✓

✓ designed to provide it · ◐ partial, conditional, or configuration-dependent · ✗ generally not provided · N/A not meaningfully applicable

The conditional cells, from each project's own documentation. Psiphon is an encrypted proxy, not a messenger: traffic is protected to Psiphon's servers, not end-to-end, and its own FAQ sends users who need anonymity to Tor instead. Ricochet Refresh has no offline delivery by design — both parties must be online — and blocking resistance is only whatever the underlying Tor configuration provides; Cwtch delivers to offline recipients only through opt-in groups hosted on untrusted servers. Briar ships Tor bridge support enabled automatically by location, but local Bluetooth/Wi-Fi sync only reaches contacts within radio range, and delivery to offline contacts needs the optional Briar Mailbox on a spare device.

Bitchat encrypts private messages end-to-end (Noise protocol) but is young and unaudited, and its whitepaper states plainly that a nearby Bluetooth observer can track a device across time and place. Meshtastic channel encryption defaults to a well-known shared key, direct messages gained per-node public-key encryption only in firmware 2.5, and its store-and-forward module is optional and needs dedicated hardware. Reticulum packets carry no source address ("initiator anonymity"), but the project claims no resistance to radio-layer traffic analysis; store-and-forward comes from LXMF propagation nodes.

NNCP onion-encrypts relayed packets, though each hop sees its neighbors' node IDs; its documented censorship bypass works by avoiding the internet entirely, which this table counts under infrastructure independence. Syncthing works fully on an isolated LAN, but the default public discovery and relay operators can see which devices connect, and store-and-forward through an intermediate device requires the beta untrusted-device mode. Winlink is the deliberate opposite of private — amateur radio rules forbid encryption and require call signs — and its radio-only mode, which avoids internet gateways, is not the default.

Protocols and Networking Stacks

Protocols and building blocks for networks that tolerate disruption, partitioning, and hostile filtering.

Delay-Tolerant Networking

  • Bundle Protocol v7 - The IETF standard (RFC 9171) for store-carry-forward networking across links with extreme delays and frequent partitions, from CubeSats to disaster areas; the foundation of the implementations below.
  • DTN7 - Rust and Go implementations of Bundle Protocol v7 with pluggable routing (epidemic, spray-and-wait), aimed at research and field deployments.
  • IBR-DTN - Lightweight C++ bundle protocol implementation (RFC 5050) for embedded Linux and OpenWrt routers, widely cited in DTN research. Dormant
  • ION-DTN - NASA JPL's full DTN protocol suite (BPv7, LTP, CFDP), flown on space missions and usable for extreme-latency terrestrial links.
  • µD3TN - Lean Bundle Protocol v7 daemon in C for POSIX systems and microcontrollers, flight-tested on CubeSat missions.

Mesh Routing and Overlay Networks

  • B.A.T.M.A.N. Advanced - Layer-2 mesh routing in the Linux kernel and the backbone of many community wireless networks; provides no encryption of its own.
  • Babel - Loop-avoiding distance-vector routing protocol (RFC 8966) that behaves well on lossy wireless links; also implemented in FRRouting.
  • BMX7 - Mesh routing protocol with trust- and reputation-aware path selection (SEMTOR). Dormant
  • cjdns - Encrypted IPv6 overlay and mesh network with addresses derived from public keys; runs over the internet or directly over local links.
  • olsrd - Implementation of the OLSR link-state MANET routing protocol (RFC 3626), deployed in community networks for two decades.
  • Reticulum - Cryptography-first networking stack that runs over LoRa, packet radio, Wi-Fi, or IP, built for very low bandwidth and zero infrastructure, with the LXMF store-and-forward messaging layer on top. Released under a custom non-OSI license with field-of-use restrictions.
  • Yggdrasil - Encrypted IPv6 overlay with scalable spanning-tree routing that can also mesh over local peer discovery; self-described as experimental.

Amateur Radio Protocols

Transmitting requires an amateur radio license, and encryption is prohibited on amateur bands in most jurisdictions — these provide availability, not confidentiality.

  • APRS - Packet-radio protocol for positions, telemetry, and short messages over VHF, relayed node-to-node by digipeaters; works entirely off-grid, with optional internet gateways (APRS-IS).
  • AX.25 - The data-link protocol underlying most amateur packet radio, including APRS and Winlink RF links; implemented in the Linux kernel.
  • M17 - Fully open digital voice and data protocol for VHF/UHF radio, using the open Codec 2 vocoder as an alternative to proprietary digital voice systems.

Censorship-Resistant Transports

These evade filtering on a functioning internet connection — none of them work during a full shutdown.

  • Conjure - Refraction networking that lets cooperating ISPs redirect covertly tagged TLS flows to unused address space, defeating IP-based blocking; deployed in production via Psiphon.
  • Lyrebird - The Tor Project's pluggable-transport suite (obfs4, WebTunnel, ScrambleSuit) that disguises traffic against DPI classifiers and active probing.
  • meek - Domain-fronting transport that hides the true destination behind large CDNs; mostly defunct since major clouds disabled fronting. Dormant
  • Shadowsocks - Encrypted proxy protocol designed to look like random bytes, very widely deployed for over a decade; researchers have documented active-probing and entropy-based detection of it by the Great Firewall.
  • Snowflake - Routes censored users through ephemeral volunteer WebRTC proxies running in ordinary browsers, making IP blocking costly for the censor.
  • Xray-core - Modular proxy platform (VLESS, VMess, Trojan) that camouflages traffic as ordinary HTTPS; the most active branch of the V2Ray ecosystem.

Anonymity Networks

Anonymity and availability are different goals: all of these require a reachable internet.

  • I2P - Decentralized garlic-routing overlay for hidden services and peer-to-peer applications; recent academic work documents design weaknesses across its implementations.
  • Katzenpost - Mix network in the Loopix lineage providing metadata resistance without any token dependency; research-grade software with a small test network. Experimental
  • Tor - Onion-routing anonymity network, the base for onion services and the pluggable-transport ecosystem; repeatedly audited (most recently Cure53, 2023) with a publicly tracked vulnerability history.

Applications

End-user tools. Entries state what infrastructure each one actually needs.

Off-Grid and Local Messaging

  • Bitchat - Bluetooth LE mesh chat for iOS/macOS with no accounts or servers, widely adopted since its 2025 launch; its developer warns against relying on it for security, and researchers reported an impersonation flaw at launch.
  • Briar - Messenger that syncs over Tor when the internet works and over Bluetooth or Wi-Fi when it does not; relays only between mutual contacts, not strangers. Audited by Cure53 (2017).
  • Meshenger - Serverless voice and video calls over the local network, usable on community mesh networks with no internet at all.
  • qaul - Internet-independent mesh messenger using Bluetooth LE, Wi-Fi Direct, and LAN simultaneously, with store-and-forward delivery.

Anonymous and Metadata-Resistant Messaging

  • Cwtch - Metadata-resistant group messenger built on Tor onion services, with untrusted relay servers for offline delivery.
  • Ricochet-Refresh - Maintained fork of Ricochet in which every user is a Tor onion service, leaving no server-side metadata; the original was audited by NCC Group (2016), before the v3 onion migration.

Censorship Circumvention and Tool Distribution

  • F-Droid Nearby - Shares and installs Android apps device-to-device over local Wi-Fi and Bluetooth, letting circumvention tools spread during a total shutdown.
  • Paskoocheh - Farsi-language distribution channel for circumvention and privacy tools, reachable via web, app, email, and Telegram so that one blocked channel is not fatal.
  • Psiphon - Multi-transport circumvention client that automatically falls back across obfuscated protocols; open client and tunnel core, centrally operated network. Audited by iSEC Partners (2014), Cure53 (2017), and 7ASecurity (2021).
  • rdsys - The Tor Project's bridge-distribution backend, handing out bridge addresses through independent rate-limited channels to resist enumeration by censors.

Offline Data Sync and Content Distribution

  • Kiwix - Serves compressed offline copies of Wikipedia and other reference content from a laptop or Raspberry Pi hotspot; used by schools, libraries, and disaster responders worldwide.
  • NNCP - Encrypted store-and-forward file and mail exchange between trusted nodes over TCP, removable media, or one-way links; a modern UUCP successor built for air gaps and sneakernets.
  • Syncthing - Decentralized file synchronization that works fully on a LAN with no internet; relay and discovery servers are optional and self-hostable.

Local-First Publishing

  • Manyverse - Client for Secure Scuttlebutt, an offline-first gossip protocol that syncs social feeds over LAN or internet; content can be encrypted, but the social graph and metadata are public by design. Dormant
  • ShareBoxx - Rust reimplementation of the PirateBox concept: a standalone offline Wi-Fi box for anonymous local file sharing and chat. Experimental

Emergency Coordination

  • FreeTAKServer - Python server for the TAK (Team Awareness Kit) situational-awareness ecosystem used by civilian search-and-rescue and disaster-response teams.
  • OpenTAKServer - TAK server that runs on a Raspberry Pi on a LAN or local mesh; note that the official ATAK-CIV client is source-available under government terms, not OSI open source.
  • Sahana Eden - Humanitarian coordination platform (missing persons, shelters, inventory, volunteers) deployed since the 2010 Haiti earthquake.
  • Ushahidi - Crowdsourced crisis mapping that ingests reports via SMS, web, and email — useful where only degraded channels survive.

Amateur Radio Software

Same caveats as the protocols above: a license is required to transmit, and content is unencrypted.

  • Dire Wolf - Software TNC that turns any computer with a sound card into an AX.25 packet station, digipeater, or APRS gateway; the modem layer behind most open packet-radio tools.
  • fldigi - Multi-mode soundcard suite (PSK31, Olivia, RTTY, and many more) with companion forms and file-transfer tools, a staple of emergency nets for two decades.
  • FreeDATA - Open HF file and message transfer using Codec 2-based modems, built as the open alternative to the proprietary VARA modem.
  • FreeDV - Open digital voice for HF radio built on the Codec 2 low-bitrate speech codec.
  • JS8Call - Weak-signal HF keyboard chat derived from FT8, with store-and-forward relaying — intercontinental text messaging with no infrastructure at all.
  • Pat - Cross-platform Winlink email client written in Go, the standard open client for email-over-radio on Linux and macOS.
  • Xastir - Long-standing graphical APRS client for mapping, tracking, and messaging over RF.

Hardware and Firmware

Most LoRa projects below run on inexpensive ESP32/nRF52 developer boards (LilyGo, Heltec, RAK); these are commercial products whose designs are only partially open.

LoRa Mesh

  • MeshCore - Lightweight LoRa mesh firmware with hybrid flood and path-based routing, a lower-overhead alternative to Meshtastic.
  • Meshtastic - The most widely used open LoRa mesh firmware and companion apps for off-grid text and location sharing; channel encryption uses shared keys with a well-known default, and key-generation flaws have received CVEs (CVE-2025-52464).
  • RNode Firmware CE - Community-maintained firmware that turns common LoRa boards into open long-range radio modems, primarily as the physical layer for Reticulum.

Mesh Router Firmware

  • AREDN - OpenWrt-based firmware that turns commodity Wi-Fi hardware into high-throughput emergency data networks on amateur frequencies (license required).
  • Freifunk Gluon - Firmware build framework behind most German Freifunk communities' mesh nodes.
  • LibreMesh - OpenWrt meta-firmware that auto-configures multi-radio community mesh networks, deployed across Latin American community networks.
  • OpenWrt - The general-purpose open router firmware that AREDN, Gluon, and LibreMesh all build on.

Open Hardware

  • LibreRouter - Open-hardware multi-radio router purpose-built for community mesh networks, developed by AlterMundi; firmware ecosystem is active, hardware development is quiet.

Networks and Deployments

Living networks and documented real-world deployments.

Community Networks

  • Freifunk - German federation of hundreds of local community mesh initiatives; local segments keep working even when an uplink is lost.
  • Guifi.net - The largest community network in the world, with tens of thousands of nodes in Spain, run as a commons since 2004.
  • NYC Mesh - Volunteer rooftop mesh across New York City; its Red Hook lineage stayed connected through Hurricane Sandy in 2012.

Community Cellular and Rural Connectivity

  • Magma - Linux Foundation mobile-core platform for running LTE/5G networks on commodity hardware over unreliable backhaul.
  • Rhizomatica - Community-owned GSM networks in rural Mexico built on Osmocom software, operated by indigenous communities under their own spectrum concession.

Emergency Radio Networks

  • Winlink - Global volunteer-run email-over-radio network used in real disaster response; a fully open path exists via Pat and ARDOP, while the official client and the fastest modems (VARA, PACTOR) are proprietary.

Case Studies

  • Breaking Bridgefy, Again - USENIX Security 2022 paper showing the protest-marketed Bridgefy mesh app remained insecure even after adopting the Signal protocol library — a cautionary tale for any crisis-marketed messenger.
  • FireChat and the 2014 Hong Kong protests - Fact-check showing the widely reported "mesh app powered the protests" story had almost no evidence of actual offline mesh usage.
  • NetHope's Hurricane María response - After Puerto Rico's near-total telecom collapse in 2017, recovery came mostly from conventional NGO-restored Wi-Fi and satellite links — a sober benchmark for what actually gets deployed in a catastrophe.

Measurement and Monitoring

You cannot route around damage you cannot see: tools that document shutdowns and censorship.

  • Censored Planet - Remote measurement platform that detects censorship worldwide without needing volunteers inside the censored network.
  • IODA - Near-real-time detection of macroscopic internet outages and shutdowns from BGP, active probing, and darknet signals; the canonical reference for confirming shutdowns.
  • OONI Probe - Volunteer-run network tests documenting censorship since 2012, with open data from more than 200 countries.

Guides and Threat Models

  • EFF Surveillance Self-Defense - Practical security guides for protesters, journalists, and other at-risk users, maintained by the Electronic Frontier Foundation.
  • net4people/bbs - Multilingual discussion forum and reading list tracking censorship-circumvention research and deployment reports.
  • Security in a Box - Digital-security guides for human rights defenders, maintained by Front Line Defenders.

Organizations

Developer Resources

  • p2panda - Rust toolkit for building local-first, disruption-tolerant applications. Experimental
  • The ONE Simulator - The standard academic simulator for evaluating delay-tolerant and opportunistic routing protocols before deploying them.
  • Willow Protocol - Sync protocol and data model for offline-first applications with fine-grained capabilities, in the Earthstar lineage. Experimental

Graveyard

Projects that shaped resilient communication but are no longer maintained. Kept for the historical record. Domains of dead projects are sometimes squatted or hijacked — where that happened, links point to archived copies.

  • Byzantium Linux - Bootable live distribution that turned any laptop into a mesh node with zero configuration. Discontinued!
  • Commotion Wireless - State-Department-funded mesh firmware from the Arab Spring era; its Red Hook offshoot in Brooklyn survived Hurricane Sandy. Discontinued!
  • disaster.radio - Solar-powered LoRa mesh for post-disaster networking; its maintainers point to Meshtastic and Reticulum as successors. Discontinued!
  • FidoNet - The 1980s–90s global store-and-forward BBS network and a conceptual ancestor of DTN; still run by hobbyists at a tiny scale. Discontinued!
  • OpenCellular - Facebook's open cellular base-station platform; stewardship passed to the Telecom Infra Project and stalled. Discontinued!
  • PirateBox - Offline Wi-Fi box for anonymous local file sharing that seeded a whole genre; see ShareBoxx for a maintained successor. Discontinued!
  • Serval Project - Pioneering disaster mesh telephony for Android whose Rhizome store-and-forward design remains influential; unmaintained since about 2022. Discontinued!
  • TapDance - First ISP-deployed refraction-networking design, superseded by Conjure. Discontinued!
  • Taylor UUCP - The classic Unix store-and-forward transport that carried mail and Usenet over intermittent links; NNCP is its modern successor. Discontinued!
  • Village Telco - The Mesh Potato combined a mesh Wi-Fi node with an analog phone port for community telephony; hardware discontinued. Discontinued!

Deep dives into single technologies covered here only at the level of their resilience role:

Contributors

Thanks to all contributors. Contributions are welcome — see the contributing guide above.

This work is dedicated to the public domain under CC0 1.0.