MeshCore vs Meshtastic: Which LoRa Mesh Should You Run?

Meshtastic and MeshCore run on the same LoRa boards and do the same basic job, which is passing short encrypted text messages between radios with no cell service. The difference is how a message gets from you to the other end. Meshtastic lets every node rebroadcast every packet up to a hop limit, which is simple and works anywhere two nodes can hear each other. MeshCore gives each radio a fixed job (companion, repeater or room server), and only repeaters relay, so the air stays quieter once somebody has put a repeater up high. For a rural county with no mesh yet, Meshtastic is the easier start and has the larger user base. For a city or a region where a group has already placed MeshCore repeaters on hills and towers, MeshCore is the better experience. And yes, you can run both; you just need two boards, because a board runs one firmware at a time.

How each one moves a message

Meshtastic: managed flooding with a hop limit

Meshtastic's mesh algorithm page describes "managed flooding": every node rebroadcasts a packet it receives, up to a hop limit, but first it listens briefly to see whether another node has already rebroadcast the same packet, and nodes that heard the packet weakly (low signal-to-noise ratio) get to go first, since they are probably farther away (Meshtastic mesh algorithm). The hop limit defaults to 3 and cannot be set above 7 (Meshtastic LoRa config). Infrastructure roles exist: ROUTER and ROUTER_LATE always rebroadcast once even if they hear another node relay, and CLIENT_MUTE never relays (Meshtastic device roles). Since firmware 2.6, direct messages learn a next hop after the first exchange, so only the matching node relays later direct messages, with a fall back to flooding if the route breaks. Broadcasts on a channel still flood.

MeshCore: fixed roles and learned paths

MeshCore's FAQ is direct about the design: "No, MeshCore clients do not repeat." Only repeaters, and room servers with repeat turned on, relay packets (MeshCore FAQ). The first direct message to a contact goes out by flood through the repeaters. The destination sends back a delivery report listing every repeater the message passed through, and that path is stored in your contact list. Later messages carry the path in the packet, and a repeater only retransmits if its address and hop position match. If a repeater disappears, the message fails after three retries and the app resets the path and sends the last retry as a flood to find a new route. Group channels have no single destination, so they always flood, but repeater owners can cap flood traffic with a hop limit of their own. The README adds that companions do not repeat "to prevent adverse routing paths from being used" (MeshCore on GitHub).

What that means on the ground

In our use, a Meshtastic mesh of handhelds works the moment two of them are in range, with nothing to configure beyond the region. The cost shows up when a region gets busy: every node is a relay, so a popular channel can keep the airtime full, and the hop limit of 3 can leave a far node out. MeshCore is quieter and scales with repeaters, but a group of companions with no repeater between them is just point to point. Somebody has to put a repeater up.

The apps

Meshtastic has an Android app, an Apple app, a web client that runs in the browser, and a Python command line tool (Meshtastic software). The phone connects to the node over Bluetooth, or over Wi-Fi or USB on boards that support it, and a node pairs with one phone at a time.

MeshCore has two companion apps. The MeshCore app by Liam Cottle runs on Android, iOS and in a browser at app.meshcore.nz, and connects to a companion radio over Bluetooth or USB. MeshOS is listed on meshcore.co.uk as the official companion app, for iOS, Android, macOS, Windows, Linux and the web (meshcore.co.uk). Repeaters and room servers are configured over USB at config.meshcore.io or remotely from the app over the radio. The FAQ notes the T-Deck firmware is free to download, with an optional unlock code for deeper map zoom and remote server administration; messaging does not need it.

One MeshCore idea with no Meshtastic equivalent is the room server, a small bulletin board that stores posts and hands a returning user the last 32 unseen messages when they log in. If your family nodes are off for hours during an outage, a room server at the house lets them catch up on what they missed.

Hardware support

Both projects run on ESP32 and nRF52840 boards from Heltec, LILYGO, RAK and Seeed. Meshtastic's device list is longer, and includes watches, e-paper boards and Raspberry Pi targets (Meshtastic supported hardware). MeshCore's web flasher (flasher.meshcore.co.uk) lists the Heltec V3, V4, T114, Mesh Node T1 and Wireless Tracker; the LILYGO T-Deck, T-Deck Pro, T-Beam, T-Beam Supreme, T-Echo and T3-S3; the RAK WisBlock and WisMesh boards on the RAK4631; and the Seeed T1000-E, Wio Tracker L1 Pro, Wio Tracker L1 E-Ink and the XIAO boards, among others. The four below are all on Meshtastic's device list and run MeshCore, and cover the roles you would want. Each needs the 915 MHz version for the US; MeshCore's FAQ confirms the 915 MHz range for the USA. Our Meshtastic device guide and MeshCore device guide go board by board.

Heltec LoRa 32 V3

Cheapest Dual-Firmware Board

Heltec LoRa 32 V3

• ESP32-S3FN8, 8 MB flash
• SX1262, 21±1 dBm max
• 0.96 inch OLED, 128 by 64
• Two SH1.25-2 battery connectors with charging
• IPEX (U.FL) LoRa antenna connector

For a powered node at the house that you may reflash as you learn.

Check price on Amazon

Sold by Leapiot Devices (third-party seller)

The cheapest board that runs either firmware well. It is an ESP32-S3 with an SX1262, a 0.96 inch OLED and a 21 dBm radio, per Heltec (Heltec V3). On Meshtastic it is the classic starter. On MeshCore the flasher offers companion (Bluetooth or USB), repeater and room server images for it, and the FAQ uses the V3 as its Wi-Fi companion example. Being an ESP32 it eats batteries, so keep it on USB power. You add your own antenna, battery and case. Amazon's listing here is from Leapiot Devices, a third-party seller.

Heltec Mesh Node T114

Best Battery Board for Either

Heltec Mesh Node T114

• nRF52840 with SX1262, 21 dBm
• 1.14 inch color TFT (optional on Heltec's page)
• 23 µA Meshtastic low-power mode
• Solar connector, 5 to 6.5 V
• Kit adds battery, case and GPS module

For a handheld that lasts on either firmware.

Check price on Amazon

Sold by Leapiot Devices (third-party seller)

The T114 is the nRF52840 board we would pick if the node will run on a battery for either firmware. Heltec lists 23 µA in Meshtastic low-power mode, a 1.14 inch TFT and a solar connector (Heltec T114). MeshCore's flasher has companion, repeater and room server builds for it, and its FAQ names the T114 among the nRF boards that can take firmware updates over the air. The Amazon kit adds a battery, a case and a GPS module (Heltec's page lists the GNSS module and shell as options) and is sold by Leapiot Devices, a third-party seller. Heltec also reports that some units have trouble sending messages longer than about 50 characters on the Long-Fast preset.

RAK WisBlock Meshtastic Starter Kit

Best Repeater Base for Either

RAK WisBlock Meshtastic Starter Kit

• RAK4631 core: nRF52840 and SX1262
• 22 dBm LoRa output
• 2.0 µA sleep current
• RAK19007 base with 5 V solar input
• Pre-flashed with Meshtastic

For the hilltop node, whichever firmware your area runs.

Check price on Amazon

Sold by Rokland (third-party seller)

The RAK4631 core is on both lists and is named in MeshCore's own FAQ hardware list. RAK's datasheet gives 22 dBm output and 2.0 µA in sleep (RAK4631 datasheet), and the RAK19007 base in this kit has a 5 V solar input. RAK's kit page says it ships pre-flashed with Meshtastic; switching it to MeshCore repeater firmware goes through the MeshCore web flasher. Sold on Amazon by Rokland, a third-party seller.

SenseCAP Card Tracker T1000-E

Pocket Companion for Either

SenseCAP Card Tracker T1000-E

• nRF52840 with LR1110 LoRa
• MediaTek AG3335 GNSS
• 700 mAh battery
• IP65 rated
• Built-in buzzer

For the pocket, on either network.

Check price on Amazon

Sold by Seeed Studio Official

The sealed pocket node, with an nRF52840, an LR1110 radio, a GNSS chip, a 700 mAh battery and an IP65 rating, per Seeed (Seeed T1000-E). It is a Meshtastic tracker out of the box, and MeshCore's flasher offers companion, repeater and room server images for it. Seeed lists no external antenna connector and the device is card-sized, so it is a companion, not a hilltop radio. Sold on Amazon by Seeed's official store.

Rural county or city with repeaters

Running both at once

One person can run both networks, and that is what we do. The rule is one firmware per board. A T114 flashed with MeshCore companion firmware and a T1000-E on Meshtastic can both sit in the same bag, each paired to its own app on the same phone. What you cannot do is bridge them: a Meshtastic node will not hear a MeshCore packet or the reverse, even on the same frequency. Flashing back and forth is possible (both projects publish web flashers), but on nRF52 boards MeshCore's flasher recommends installing an updated bootloader for reliable Bluetooth updates, so treat a board as committed once it has a job.

Questions that come up

Is one of them more secure?

Both encrypt. Meshtastic lists encrypted communication as a core feature, and MeshCore's site describes AES-128 end-to-end encryption. We are not in a position to grade the implementations against each other, and neither project claims to be a replacement for a vetted secure messenger.

Do I need a license for either?

No. Both use the 902 to 928 MHz ISM band in the US. Meshtastic's region table lists US as not requiring a license, and MeshCore's FAQ names the 915 MHz range for the USA. Licensed voice is a different tool; see our GMRS vs FRS explainer.

Which has more users near me?

Usually Meshtastic, since it has been around longer, but that is our impression rather than a count. Check the public maps for each project before you buy, and ask your local group which repeaters are live.

Can a MeshCore repeater run on solar?

Yes, and nRF52840 boards like the RAK4631 are the right choice for it; MeshCore's README lists low power consumption for battery and solar nodes as a goal. The repeater needs its frequency set over USB the first time, and the default admin password should be changed.

Which one should a beginner start with?

Meshtastic, unless a local MeshCore group already has repeaters up. It has more hardware, more guides and the larger map, and a board you buy for it will run MeshCore later if you change your mind.

Where we land

Start with Meshtastic if you are building a mesh from nothing in a rural county; move to or add MeshCore when repeaters appear on your horizon. Buy an nRF52840 board either way. More radios and mesh guides are in our off-grid comms section.