Overview
Meshtastic
Meshtastic is an established open-source LoRa mesh networking project focused on creating a decentralized communication platform that works without relying on internet or cellular infrastructure. It enables text messaging, location sharing, and telemetry over mesh networks.
MeshCore
MeshCore is a lightweight, portable C++ library for multi-hop packet routing in embedded projects using LoRa and other packet radios. It aims to provide a balanced approach to mesh networking with a focus on simplicity and scalability for custom embedded solutions.
See how these technologies work in practice
Interactive Routing VisualizationFeature Comparison
| Feature | Meshtastic | MeshCore |
|---|---|---|
| License | Open Source | Open Source (MIT License) |
| Architecture | Focused on complete mesh networking solution | Lightweight library for packet routing |
| Target Use | General-purpose mesh communication | Custom embedded solutions |
| Routing Method | Flood-based broadcasting with hop limits | Selective forwarding with priority-based routing |
| Power Consumption | Optimized for low power | Designed for low power consumption |
| Firmware Types | Unified firmware | Four distinct firmware types |
| Network Structure | Channel-based with encryption | Route-based with encryption |
| Premium Features | Fully open-source | Some premium features in T-Deck firmware and mobile apps |
| Congestion Control | Role-based scaling and hop limits | Priority-based transmission and airtime budgeting |
Key Differences
Routing Architecture
Meshtastic
Uses a hybrid approach with three layers: Flooding Router (base), Next Hop Router (for acknowledgments), and Reliable Router (for messages requiring guaranteed delivery). Messages propagate through the network with high redundancy but potentially higher congestion.
MeshCore
Implements three distinct routing modes: Flood Routing (with priority), Direct Routing (path-specific), and Zero-Hop Routing (local broadcast). Focuses on selective forwarding to reduce network load.
Routing Mechanisms Compared
Meshtastic Flooding Approach
Messages flood through all available paths to reach the destination, maximizing delivery probability but creating potential congestion
MeshCore Selective Routing
Messages travel along specific routes, optimizing bandwidth but requiring path establishment
Packet Forwarding
Meshtastic
When a radio receives a packet, it checks if it has seen the packet before. If not, it will rebroadcast it. Each rebroadcast decreases the hop limit by one, and packets with a hop limit of zero are not rebroadcast.
MeshCore
Uses a more selective approach where repeaters don't forward every packet they receive, but only those that need to be routed to specific destinations. This aims for a more efficient use of bandwidth.
Network Structure
Meshtastic
Uses channels with shared encryption keys. All nodes in a radio mesh retransmit messages regardless of channel settings.
MeshCore
Uses routes for message delivery with public key encryption. Offers room servers that function like BBS systems for persistent message storage.
Congestion Management
Meshtastic
Scales message intervals based on network size, with special handling for router/repeater nodes and trackers/sensors. Uses message deduplication and hop limits to control congestion.
MeshCore
Employs an airtime budget system (limiting nodes to ~33% of available airtime), combined with priority-based transmission and randomized delays to prevent collision storms.
Client Architecture
Meshtastic
Uses a unified firmware approach across different hardware platforms.
MeshCore
Offers four distinct firmware types:
- BLE Companion (connects over Bluetooth)
- USB Serial Companion (connects over USB)
- Repeater (extends network range)
- Room Server (stores message history)
Disaster Scenario Performance
In a large-scale disaster scenario with many users (tens of thousands) across a wide area (hundreds of km²):
Meshtastic Strengths
- Immediate message propagation without requiring path establishment
- Higher probability of message delivery through redundant paths
- Better for the initial emergency phase when reliable communication is critical
Meshtastic Challenges
- Risk of broadcast storms and significant congestion with many users
- Limited ability to prioritize critical messages during high traffic
- Potential for significant packet loss as network scales
MeshCore Strengths
- More efficient bandwidth usage through selective routing
- Priority system helps ensure critical messages get through
- Room servers provide persistent messaging points for affected communities
- Better performance over sustained usage periods
MeshCore Challenges
- Initial path discovery requires time to establish efficient routes
- Less redundancy could result in some message delivery failures
- Requires more strategic node placement for optimal performance
Use Case Suitability
Meshtastic is better for:
- Users wanting a fully open-source solution
- Larger mesh networks with many nodes
- Users who want an established platform with extensive documentation
- Applications requiring extensive telemetry and sensor integration
- Scenarios requiring immediate message propagation without path establishment
- Emergency situations where message redundancy is more important than network efficiency
MeshCore is better for:
- Custom embedded solutions requiring lightweight implementation
- Networks needing more selective message routing for bandwidth efficiency
- Use cases benefiting from the room server concept for persistent message storage
- Applications where T-Deck hardware integration is important
- Dense node deployments where network congestion is a concern
- Long-term communication scenarios requiring sustainable bandwidth usage
Conclusion
Both Meshtastic and MeshCore provide off-grid mesh communication solutions using LoRa technology, but they take different approaches. Meshtastic offers a more established ecosystem with full open-source implementation and better immediate delivery through aggressive flooding, while MeshCore provides a lighter-weight alternative with more efficient routing and some unique features like room servers for persistent storage.
For disaster scenarios, Meshtastic may perform better in the immediate aftermath when redundancy is critical, while MeshCore could provide more sustainable communication over time as the network stabilizes. The ideal solution might combine elements of both approaches or deploy them in complementary roles based on the specific requirements of the deployment area and expected user density.
Latest Version Comparison
Meshtastic
VS
MeshCore
Disaster Scenario Analysis
How would each platform perform in a large-scale disaster with 50,000 people trying to communicate over 1,000 nodes?