While Meshtastic is by far the most popular off-grid messaging solution relying on LoRa radios, MeshCore offers an alternative as a lightweight C++ library and firmware designed for multi-hop packet routing and made for developers who want to create resilient, decentralized communication networks that work without the internet.
The project’s GitHub repository provides some high-level differences compared to the Meshtastic and Reticulum projects:
MeshCore provides the ability to create wireless mesh networks, similar to Meshtastic and Reticulum but with a focus on lightweight multi-hop packet routing for embedded projects. Unlike Meshtastic, which is tailored for casual LoRa communication, or Reticulum, which offers advanced networking, MeshCore balances simplicity with scalability, making it ideal for custom embedded solutions., where devices (nodes) can communicate over long distances by relaying messages through intermediate nodes. This is especially useful in off-grid, emergency, or tactical situations where traditional communication infrastructure is unavailable.
MeshCore key features:
- Multi-hop packet routing – As a mesh network, devices can forward messages across multiple nodes, and MeshCore supports up to a configurable number of hops to balance network efficiency and prevent excessive traffic.
- Supports LoRa radios – Compatible with Heltec, RAKwireless, and (some) other LoRa-based hardware.
- Decentralized & resilient – No central server or internet required, and the mesh network is self-healing
- Low Power – Design for battery-powered or solar-powered devices.
- Simple to Deploy – Flash MeshCore Companion firmware to the device, and install the MeshCore app for Android or iOS, or use the web client. There’s also a JavaScript library and a Python client for developers.
Supported devices include LILYGO T-Deck Plus for standalone operation without a smartphone, Seeed Studio T1000-E, Heltek Lora32 V3, and others. You’ll find the full list of supported devices on the web flasher.
The video below shows how to get started with MeshCore, and the onboarding and messaging functionality is very similar to MeshTastic. It looks a bit simpler, and there’s no QR code, but instead, flood adverts are sent to add users. The video also demonstrates the use of MeshCore repeaters to further extend the network coverage.
MeshCore lacks features like real-time GPS tracking or sensor integration by default, but MeshCore premium features can be enabled on the T-Deck, T-Display Pro, and T5 ‘Ultra’ firmware, by purchasing an 8 GBP (about $11) license on the MeshCore store. Premium features include:
- Map zoom to higher detail levels
- MeshCore profiles:
- Remote repeater or room server admin CLI
- Telemetry support (and location sharing)
- Ripple profiles:
- Post office support. (msg store-n-forward, group chats, shared calendars, etc…)
- GPS location broadcast mode
- Pair tracker/sensor devices
MeshCore and Ripple are different profiles that can be enabled as needed. So while the MeshCore library/firmware is open-source under an MIT license, there must still be close-source binaries to handle the premium features. Another premium option will be the upcoming MeshCore ESP-NOW bridge licence. Those are designed to fund the development of the project. More details can be found on the project’s website.
Thanks to Marek for the tip.
Jean-Luc started CNX Software in 2010 as a part-time endeavor, before quitting his job as a software engineering manager, and starting to write daily news, and reviews full time later in 2011.
Support CNX Software! Donate via cryptocurrencies, become a Patron on Patreon, or purchase goods on Amazon or Aliexpress. We also use affiliate links in articles to earn commissions if you make a purchase after clicking on those links.
I’m an avid follower of CNX and I’m really happy meshcore gets covered here, thanks Jean-Luc !
Is it compatible with meshtastic, can one send messaged between the 2?
No
trouble is with other band. meshcore cant send message from 433MHz to 868MHz (reticulum can)
I think the problem is one-man show there – development requires time, and developer can’t catch meshtastic/reticulum teams that fast. But there is a benefit too – project was started later, having experience with lora limitations and is more scalable. Meshtastic have a problem with max-hops, on 7 it can choke band very fast, on 3 you can’t reach too far because someone can have little antenna in pocket not in mute, so it waste hop just on it. Greatest problems for now – it’s rare, in my city we have all time online 40 Meshtastic nodes and over 100 discovered, but only 2 Meshcore repeaters which even can’t see each other. Going with “pay to play” isn’t benefit for userbase growth too. I’ll pay when I can use it, but on start of building mesh I have one repeater, one companion and that’s it until I’ll see some coverage to reliably talk and share location with others.
I believe it’s not impossible to create 433/868 bridge, if there is already espnow/LORA bridge. In my understanding it needs 2 radios and code to share messages through uart or other interface – sounds easier than espnow bridge. (Or two esp-now bridges on different frequencies – so both will merge in one network giving espnow there as third band)
6 months ago we only had meshtastic in my city, now meshtastic has been wiped out and we only have meshcore, everybody has switched, I keep one lone meshtastic on for, well yes for what, have no contacts anymore on MT. That says that things can change fast.
Unfortunately it doesn’t seem to be possible to use 2.4GHz radios like the sx1280, only sub GHz radios seem to be supported for mesh… Else i would love to try it, would be great for the use in amusement parks, give the kids a terminal and know where they are, no crying over lost parents either. no big issue if such a terminal gets soaked in water 😉
MeshCore is a terrible thing movig towards closed source software. It have a bad licence (MIT that is not copyleft) and shows to the public how its possible to absuse partly open source code parts to combine them with closed source development and then start selling licences.
Do not use this partly closed source crap named MeshCore. The relevant part of the multi hop routing is already implemented in meshtastic.
There is no benefit in MeshCore for anything. All practical things you can already do with Meshtastic like for example scripting for remote management of your remote hardware that is far away and endless other things.
Nearly no one is using MeshCore. You wont have any mesh to connect to. If you start to setup something locally on your own from the beginning, then setup Meshtastic nodes. There wont be any people who try out this unknown closed source thing MeshCore. So when you setup something, it wont benefit others because happily nearly no one is using this because its just a unknown bad product.
If You have 20-50 nodes in town Your band is full 50-80%, This same in meshcore 11%.
Better way is reticulum not meshtastic
Maybe I missed it, but if it’s not there, they should put this type of information on their website or in the description on the GitHub repo.
They do explain it is lightweight, but numbers are always better, and I did not expect such a gap.
You are answering a complete diffetent topic. At first a tool have to be free as in freedom before considering to use it at first. When you use a tool for private encrypted communication, it have to be fully open source like Meshtastic is.
If you want to discuss your complete different topic, then do not put it as a answer to an other topic.
What you are talking about is the capability to send messages in general. You are talking about crouded places with many nodes. Yes, there LongFast is the wrong setting. You have to configure the correct spreading factor (SF) based on your area. Its just basic LoRa knowledge. When you change the SF and then rename the project and make parts closed source it does not make any logical sense. Just set the SF in Meshtastic to ShortSlow or ShortFast and then you have the same higher bandwith benefit but keep your software fully open source and reviewable.
CNXSoft reviewed Meshtastic on real hardware in a place with zero traffic. There you can even go with LongSlow that wont work properly on any places with few more nodes in range.
That’s terribly harsh. While you may not agree with some choices, the way you express it is IMHO way beyond polite discourse. Let’s please get back to civilised discussion.
Of course i am as harsh as possible against closed source software. Everyone on this planet should be as harsh as possible against closed source crap.
Openness is providing freedom, free access and transparency. The basic values of a free and democratic world.
Copyleft software licences is a insurance to keep those values up. MeshCore is a example on how bad things can get when those basic values are traded in for money-making.
so you think that everyone should work for free? and give away the product of their brains and knowledge? and who will feed and house such productive people?
Well no more meshtastic in my town, only meshcore, this happened in just 2-3 months. I do agree with closed source, but meshtastic was to unstable, and meshcore is just better in reality and it is alive, meshtastic was always dead feeling.
Meshtastic chases people who uses his registered trademark and/or logo without permission. Meshcore not, you are free to use Meshcore mark, logo and so on. So it’s enough to prefer Meshcore over Meshtastic.
You may have missed on important point here: MeshCore has important management features that cannot be accessed if not running T-Deck/LilyGo hardware. Having to remote manage a MeshCore node up a 50′ tower, without remote management (which comes by Ultra license) should be something people understand before choosing it over Meshtastic. I want to use MeshCore and do think it’s superior, but I don’t want or need their hardware.