Mesh networking that's yours
High-performance Reticulum (RNS),
built to run on any device.
Built for the performance, stability, and energy efficiency every Reticulum node needs, from a $5 microcontroller to a cloud server cluster. One engine and one API, the same on embedded, desktop, mobile, games, and the web.
Runs onOur standards
What you can count on
License
MIT / Apache 2.0
Dual-licensed and permissive. No copyleft or commercial restrictions.
Safety
Enforced, then audited
In the engine, panics, unwraps, and unjustified unsafe never compile. What can't be forbidden is audited: dependency unsafe with cargo-geiger, undefined behavior under Miri, advisories with cargo-deny.
Correctness
Diff-tested against RNS
Every change is checked against the reference, then put through unit, property, fuzz, and mutation tests, with Kani proofs where they matter.
Performance
Measured, not just claimed
Performance is tracked in the open, measured by a harness you can run yourself.
See the benchmarks →
What we're building toward
Reticulum is the foundational communication infrastructure of a bright future we can have, as long as we all build it. This is the Personal team's effort to put RNS into the hands of more builders, to help realize that future.
Interfaces
Where the mesh meets the world
Prns keeps the RNS-compatible interfaces builders already know, then expands the map with native links for new devices and networks.
Prns interfaces are hot-swappable: add, remove, or change an interface without a node restart.
Radios
Proximity links for devices and boards
Bluetooth LE Auto-interface, ESP-NOW, and LoRa bring nearby devices, board fleets, and long-range RF links into one Reticulum mesh.
LAN
Auto-discovered local-link peers
Wi-Fi Auto-interface uses multicast, mDNS, and gateway rendezvous to find nearby nodes and fold a local network into the mesh.
Wires + packet radio
Cables, TNCs, and radio modems
USB Auto-interface, serial framing, KISS, AX.25, and RNode bridge small devices and packet-radio hardware into the same mesh.
Routed IP
Internet, WAN, and backbone links
TCP client/server, UDP, WebSocket, and Backbone let distant peers participate in the mesh across private WANs, VPNs, public Internet relays, and browser integrations.
Routes in
What are you here to do?
Choose the path that matches how Prns fits into your work: hardware you flash, infrastructure you run, or software you build.
Flash a Hopspot
Pick a supported board, flash it straight from your browser, and have a dedicated mesh device in minutes.
Run a daemon
Install a fast Reticulum daemon for desktops, LXMF apps, backbone VPSs, etc.
Use the browser node playground
Try the TypeScript API with the shared Rust engine in WebAssembly, connect through Auto Wi-Fi or USB Auto, and watch live node activity locally.
Build on Reticulum
Use the engine and bindings to add mesh networking to apps, tools, services, or games.