MeshRoute is an open LoRa mesh protocol and firmware project built around one conviction: radio airtime is scarce, so a mesh should route deliberately.
Why MeshRoute exists
Flood-based meshes are simple and robust at small scale, but every repeated transmission consumes shared spectrum. As a network becomes denser, that cost grows precisely when regulatory duty-cycle limits and collision risk matter most. MeshRoute explores a different trade-off: learn useful paths, adapt to observed link conditions, and spend airtime carefully—even when that can mean accepting more latency.
What makes it different
- Deliberate, link-quality-aware routing instead of network-wide message flooding.
- Encrypted teams with their own identity space and direct or channel communication.
- Mobile identities that can move between fixed home nodes while remaining reachable.
- Layered networks connected by gateways, so growth does not require one giant flood domain.
- A deterministic simulator and native test suite used to make protocol changes measurable.
Current stage
MeshRoute is a working protocol and firmware project approaching its first public release. Core behavior is implemented and the current focus is validation, fixing edge cases found by tests and real hardware, and completing the companion application. It is still pre-release software and should not yet be treated as a safety-critical emergency system.
Who is building it
MeshRoute is designed and implemented by Stanisław Kozicki, a software developer with more than 25 years of experience. Automated tools support implementation, analysis, and iteration; protocol design and engineering decisions remain human-reviewed.
The source, protocol documentation, simulator, and development history are available on GitHub.