Meshtastic vs Meshcore: which firmware to choose for your LoRa mesh network

Two firmwares, same radio

As explained in LoRa: what it is and how it works, LoRa radio is just the physical layer: the way bits become radio waves. Very different network protocols can be built on top of that radio. Meshtastic and Meshcore are the two most-used open-source firmwares today for turning a cheap LoRa device into a node of a decentralized mesh network, with no gateway and no central server.

They use the same radio, and often run on the exact same hardware, but they’re not compatible with each other: a Meshtastic node can’t exchange messages with a Meshcore one, because they speak different protocols. Choosing one or the other means choosing which network you join.

Meshtastic: the de facto standard

Meshtastic is the older, more mature of the two projects, with a large, active international community since 2020. Its core mechanism is flood routing: when a node transmits a message, every other node that receives it relays it further, up to a configurable hop limit. It’s a simple, robust mechanism that works well on smaller or lower-density networks.

Strengths:

• Official apps for Android, iOS, Windows, Linux, and web, plus a wide range of third-party integrations (MQTT, Home Assistant, Telegram/Discord bots).
• Extremely broad hardware support: practically every ESP32/nRF52 board with a LoRa module (Heltec, LilyGo, RAK, Station G1/G2, and many more) has an official or community-supported Meshtastic target.
• Per-channel encryption (a pre-shared AES256 key) and public-key-encrypted direct messages between individual nodes.

The main limitation comes precisely from flood routing: on very dense or large networks, every message relayed by many nodes eats into shared bandwidth and “airtime,” which on LoRa is a scarce, regulated resource (see the duty-cycle constraints covered in the intro article).

Meshcore: built to scale better

Meshcore is a newer project, explicitly designed to overcome the scalability limits of pure flood routing. Instead of relaying every packet on every node, it relies on route discovery and optimization: once an efficient path between two nodes is found, subsequent traffic tends to follow it instead of being re-broadcast across the whole network, reducing redundant traffic on denser networks.

Meshcore shares much of the hardware Meshtastic supports — boards like the Heltec V3, LilyGo T-Deck, and several RAK modules work with either firmware, depending on which image gets flashed — and offers dedicated multi-platform apps (Android, iOS, Windows, Linux, web). Security is also central here, with encryption designed around a model closer to point-to-point messaging between contacts.

Being younger, it has a smaller community than Meshtastic’s, with less established documentation and fewer ready-made third-party integrations, but it’s growing quickly among people running larger mesh networks who feel flood routing’s limits.

Which one to choose

• If you want the largest community, the richest documentation, and ready-made integrations (Home Assistant, MQTT, bots), Meshtastic remains the safer choice, especially to get started.
• If you’re building — or joining — a dense network with many nearby nodes, where flood routing starts saturating available bandwidth, it’s worth evaluating Meshcore for its more efficient routing approach.
• Keep in mind the choice isn’t locked to the hardware: many compatible boards can be reflashed with either firmware. It’s locked to the network you join — check which firmware the local community you want to join actually uses. In Italy, for example, Lora Italia’s Telegram group and node map make it immediately clear which firmware is in use, before deciding.

In the next article we’ll walk through how to actually join the Italian Lora Italia mesh network, with practical setup of your first node.