Meshtastic vs LoRaWAN: what is the difference, and which fits your project?
Meshtastic and MeshCore relay text between LoRa radios with no infrastructure; LoRaWAN carries sensor data through gateways. How they differ and which fits.
Photo: Egor Myznik / Unsplash
After reading this article you will be able to:
- Explain how Meshtastic's managed flooding differs from LoRaWAN's gateways and network server
- Place MeshCore between the two and describe the legal limits that apply to all of them
- Choose a LoRa mesh or LoRaWAN for messaging, telemetry or a fleet of sensors
On this page
Meshtastic and LoRaWAN use the same LoRa radio and the same unlicensed bands, and that is where the similarity ends. Meshtastic is an open-source project that builds an off-grid mesh from inexpensive radios: each node rebroadcasts what it hears, so people can exchange text messages and positions with no towers, servers or subscriptions. LoRaWAN is a network protocol in which sensors send data through gateways to a network server and on to an application. One is built for people talking to people; the other for devices reporting to software.
The short answer. Use Meshtastic, or the newer MeshCore, when a group needs to message each other where there is no cellular coverage (hiking, events, sailing, emergency preparedness, a neighborhood network) and nobody wants to run infrastructure. Use LoRaWAN when you have sensors that must deliver readings to a database or dashboard, many devices, batteries that must last years, and security keys that someone manages. A LoRa mesh can carry a few sensor readings, and LoRaWAN can carry a short command, but each is awkward at the other’s job.
| Meshtastic | MeshCore | LoRaWAN | |
|---|---|---|---|
| Built for | Text and position between people | Text with fixed repeaters | Sensor data to applications |
| Who relays | Any node, by default | Repeaters only | Gateways, over IP |
| Routing | Managed flooding | Flood once, then learned paths | Star of stars, network server |
| Infrastructure | None required | Repeaters on high sites | Gateways and a network server |
| Governed by | Open-source project | Open-source library (MIT) | LoRa Alliance specifications |
How does Meshtastic work?
A Meshtastic node is a small board with a LoRa radio and a microcontroller. The project’s hardware list includes boards from RAK, LILYGO, Heltec and Seeed Studio, mostly built around ESP32 or nRF52840 chips with an SX1262 radio. Most people pair a node with a phone app and type messages there; some nodes have their own screen and keyboard.
Routing is managed flooding. Every node that receives a packet may rebroadcast it, but it waits a short, signal-dependent time first and stays silent if it hears a neighbor do it, so distant nodes tend to relay and nearby ones hold back. A hop limit stops packets from spreading forever: the default is 3 and the maximum 7. Since firmware 2.6, direct messages learn a next-hop relay after the first exchange and fall back to flooding if that relay disappears.
Channels are encrypted with a pre-shared key using AES, and the default channel uses a published key, so anyone can read it. Private groups set their own key, and direct messages use a key derived between the two nodes. The project states plainly that there is no forward secrecy and that packet headers stay readable so nodes can relay them.
Meshtastic is not limited to chat. A telemetry module reports battery, channel usage and readings from common I2C environmental sensors, every 30 minutes by default, and a node with internet access can bridge the mesh to an MQTT broker through the MQTT integration.
How is LoRaWAN different?
LoRaWAN does not relay between devices at all. The LoRa Alliance describes a star-of-stars topology: every gateway in range forwards a device’s uplink over IP to a network server, which removes duplicates, manages data rates and passes the payload to an application server. Devices do not need to hear each other, and adding coverage means adding gateways.
The design priorities follow from the job. A LoRaWAN Class A sensor wakes, sends a few bytes, listens briefly for a reply and goes back to sleep, which is how a soil probe or meter lasts years on a battery. Security is built in: per-device keys, end-to-end payload encryption toward the application server, and frame counters, all defined in the LoRaWAN specification. Certified devices from different makers work on the same network. The LoRaWAN guide covers the details.
What LoRaWAN lacks is a way for devices to talk to each other without the network, and a comfortable path for messages flowing toward devices. Downlinks are scarce, and nothing works without at least one gateway with a backhaul and a server behind it.
Where does MeshCore fit?
MeshCore is a newer open-source project described as a lightweight C++ library for multi-hop packet routing over LoRa and other packet radios, released under the MIT license. Its firmware comes in three roles: companion radios that connect to a chat app, repeaters that extend coverage, and room servers that hold shared posts.
The routing differs from Meshtastic’s. According to the MeshCore FAQ, the first message to a new destination is flooded, the reply records which repeaters it crossed, and later messages carry that path so only the listed repeaters retransmit. Client devices never repeat. Group channels have no single destination and are still flooded. The result sits between the two models in this guide: still a mesh with no servers, but with fixed infrastructure nodes, which suits a community that can put repeaters on rooftops or hills. Meshtastic and MeshCore nodes do not interoperate, and neither can join a LoRaWAN network.
What legal limits apply to all of them?
Every LoRa transmitter in an unlicensed band follows the same rules, whatever protocol it runs. In Europe, ERC Recommendation 70-03 allows up to 500 mW e.r.p. with a duty cycle of at most 10 percent in the 869.4 to 869.65 MHz band, and only 1 percent in 868.0 to 868.6 MHz. Meshtastic’s EU_868 setting uses the 869.4 to 869.65 MHz band and enforces the 10 percent limit, pausing a node that reaches it. The same page documents an option to override the duty cycle and warns that it may break the rules.
A few other points from the Meshtastic documentation matter in practice. A node will not transmit until its region is set. The power limits in the firmware are ceilings, not national allowances, so check your own band plan. Amateur radio band settings require a license, and an amateur license forbids encryption. Nodes hear each other only when they use the same modem preset, so a mixed group has to agree on one.
For a busy mesh, the duty cycle is the real capacity limit. Every relayed packet costs airtime on every node that relays it, which is why both mesh projects work to reduce rebroadcasts.
When should you choose each?
Choose Meshtastic when:
- People need text and location sharing without cellular coverage.
- You want to start with two radios and no infrastructure, and grow organically.
- A few sensor readings on the side, such as a weather station on the mesh, are enough.
Choose MeshCore when:
- A community can install and maintain repeaters at good sites.
- You expect enough traffic that flooding every message would waste airtime.
Choose LoRaWAN when:
- Devices are sensors whose data must reach an application reliably.
- You need years of battery life, managed keys and certified hardware from several vendors.
- You are deploying tens or thousands of devices, on your own network or an operator’s. The LoRaWAN vs NB-IoT guide helps if cellular is also an option.
Where to go next
- LoRa vs LoRaWAN separates the radio layer from the protocols built on it.
- LoRaWAN explained covers gateways, device classes and security.
- LoRaWAN vs NB-IoT compares LoRaWAN with operator cellular IoT.
- IoT connectivity overview places these options among Wi-Fi, BLE, Zigbee, Thread and cellular.
Topics: Meshtastic, MeshCore, LoRaWAN, LoRa, mesh, comparison