Off-grid comms for your crew—built for the LoRa hardware you may already own.
Four radios. Zero infrastructure. A complete network. MeshRoute is a working LoRa mesh protocol and firmware project that routes deliberately, supports encrypted teams, and keeps roaming members reachable as they move.
A mesh that treats airtime as precious
LoRa can travel remarkably far, but every node shares a small radio budget. Flood-based meshes are simple and robust at small scale; as density grows, repeated traffic consumes more airtime, increases contention, and pushes against duty-cycle limits. MeshRoute takes a different route: learn useful paths and send a message along a deliberate path instead of asking the whole network to repeat it.
That trade-off is intentional. Maintaining and repairing routes can add latency, but it gives the protocol a way to adapt to link quality, disappearing nodes, topology changes, and one-way radio links without spending airtime everywhere.
Designed around useful small teams
A network should not need city-wide adoption before it becomes useful. MeshRoute treats a team as an encrypted overlay with its own identities and communication. Members can talk directly or through team channels with no server, tower, or cellular service.
A team member can also roam. The member keeps a stable cryptographic identity while the network tracks which fixed home node can currently reach it. Move toward a better anchor and the attachment can change without turning the person carrying the radio into a new identity.
Built to grow without one giant flood domain
Local meshes can operate as separate layers with their own radio parameters and routing state. Gateways connect those layers and forward traffic along an explicit path. The objective is growth without forcing every local transmission across every participant.
Receipts, not just claims
MeshRoute is developed against deterministic radio simulations, a native test suite, and real test hardware. The scenarios exercise delivery, rerouting, asymmetric links, mobile registration, team separation, and cross-layer traffic. When a more realistic model exposes a failure, that result becomes a protocol or test problem to solve—not a number to hide.
Current status
The protocol and firmware are working and approaching their first public release. Hardware validation, edge-case fixes, release packaging, and the companion iPhone application are still in progress. MeshRoute is pre-release software, has only run on test hardware, and should not yet be treated as a safety-critical emergency system.
Follow the measurable path to release in Building MeshRoute in public, check the current project status, or learn more about MeshRoute.