MeshCore and Meshtastic Compared
MeshCore and Meshtastic are both open-source firmware projects that enable mesh networking over LoRa radio hardware. They share the same goal of enabling off-grid communication, but they take different technical approaches. This page provides a factual comparison to help you make an informed decision.
Side-by-Side Comparison
| Feature | MeshCore | Meshtastic |
|---|---|---|
| Routing protocol | Managed flood | Naive flood (with some optimizations) |
| Node types | Client, standalone, repeater, room server | Client, router, repeater |
| Room servers | Yes — dedicated group chat hubs that store and forward messages | No — group messages rely on all nodes in range |
| Max hops | Configurable, typically 3-5 | Configurable, default 3 |
| Encryption | AES-256-CTR for direct messages | AES-256-CTR with PSK for channels |
| Message persistence | Room servers store messages for offline users | No server-side persistence |
| Companion app | MeshCore App (Android, iOS) | Meshtastic App (Android, iOS, web) |
| Web flasher | flasher.meshcore.co.uk | flasher.meshtastic.org |
| Hardware support | ESP32-based LoRa devices (Heltec, LilyGo, RAK, SenseCAP) | ESP32 and nRF52-based LoRa devices (broader hardware range) |
| Firmware variants | Evo, Weebl, Aurora, ZephCore | Single firmware with configuration options |
| Community size | Smaller, growing, concentrated in Europe | Larger, established, global |
| Project maturity | Newer project, rapid development | More established, stable release cycle |
| License | Open source | Open source (GPL) |
| Telemetry modules | Limited | Extensive (environment, power, GPS, air quality) |
| MQTT gateway | Community-built integrations | Built-in MQTT support |
Routing: Managed Flood vs Naive Flood
This is the most significant technical difference between the two projects.
Meshtastic: Naive Flood
In Meshtastic, when a device sends a message, every device that receives it rebroadcasts it (up to the hop limit). This is simple and reliable for small networks, but it scales poorly. In areas with many nodes, the same message is retransmitted many times by many devices, consuming bandwidth and increasing the chance of packet collisions.
MeshCore: Managed Flood
MeshCore uses a more selective approach. Nodes make decisions about whether reforwarding a message is useful, reducing redundant transmissions. This means the network uses less airtime for the same number of delivered messages, which is especially beneficial in dense networks.
In practice: MeshCore’s routing tends to perform better in areas with established repeater infrastructure. Meshtastic’s approach works well for ad-hoc groups where every device needs to relay.
Room Servers
Room servers are a MeshCore feature with no direct equivalent in Meshtastic.
A room server is a dedicated node that acts as a group chat hub. It stores messages and forwards them to participants, even if they were offline when the message was sent. This enables asynchronous group communication: you can go offline, come back hours later, and receive all the messages you missed.
In Meshtastic, group communication happens through broadcast channels. Messages are sent to all devices in range, but if a device is offline or out of range when the message is sent, that message is lost.
Room servers add infrastructure cost (a device dedicated to this role), but they significantly improve the group communication experience.
Can I Run Both?
You can own devices running both firmwares, but they operate on separate networks. A MeshCore device and a Meshtastic device cannot exchange messages, even if they are using the same hardware model and frequency.
Some operators run both networks in parallel in the same area, serving different use cases. This requires separate devices for each network.
Making Your Decision
The best choice depends on your local context. If there is an active MeshCore community in your area with repeater infrastructure, MeshCore provides a strong experience. If your area has an established Meshtastic network, joining that network gives you immediate connectivity.
If you are starting from scratch with no existing network nearby, both are viable options. Consider which project’s technical approach and community best match your goals.
Visit our community directory to see what is active in your area, or check the coverage map to see which network has nodes near you.