MeshCore versus Meshtastic: choose the network before the radio

MeshCore and Meshtastic both support text messaging over compatible LoRa radios without mobile data along the radio path, but they are different systems with different firmware, apps and protocols. They do not exchange messages directly just because the radios use the same band. For most beginners, the better choice is the system used by the people they actually want to contact.

This comparison is based on MeshCore’s official documentation and Meshtastic’s official getting-started guide, not comparative range, battery or reliability tests by CumbriaCQ.

The practical differences

Sources: MeshCore FAQ, including client and channel routing; Meshtastic device roles; Meshtastic MQTT configuration. Roles evolve: the Meshtastic documentation marks its old REPEATER role deprecated, so do not copy an old tutorial merely because it uses the word “repeater”.

Hardware overlap does not mean interoperability

Some board families appear in both projects, but the exact board revision, radio chip, frequency variant and firmware target matter. Check the MeshCore hardware/flasher routes and Meshtastic supported hardware instructions for your precise device. A similar enclosure or an “868 MHz” label is not enough.

Flashing a supported board from one system to the other replaces the software running on it. It does not translate the old network’s messages, migrate channel secrets automatically or leave an ordinary single-radio node simultaneously joined to both systems. Save settings you need securely and follow the board-specific installation procedure. Do not change a shared repeater without its operator’s approval.

A purpose-built bridge is an extra system with its own operator, power, privacy and possibly internet dependencies. Neither a public channel with the same name nor buying a second aerial creates such a bridge. Do not plan a household link around one unless its operator confirms exactly what it does and you test the intended route.

Apps, firmware and cost

Each system needs its own compatible client and firmware. MeshCore’s official site provides mobile, desktop and web entry points, while the FAQ distinguishes BLE, USB and standalone firmware. Its core messaging is available without buying optional advanced unlocks; that does not mean every app or standalone firmware component is open source. The FAQ specifically distinguishes the open firmware from the native mobile apps and T-Deck firmware.

Meshtastic’s setup guide walks through hardware, data cables, flashing and connecting a client. Follow the software route for your operating system rather than attempting to pair it with a MeshCore client. With either system, budget for a complete radio, antenna, enclosure, suitable power and the number of users — not just an advertised bare board. No prices or subscription promises are assumed here.

Privacy: public channels are still public

Encryption is not the same as secrecy from everyone. People who know a shared public channel’s key can participate in that channel; positions and identifiers may also be exposed by optional features. Use private communications only after understanding key sharing and who has access. Do not use either system to publish sensitive medical information or an unattended home’s precise location.

Meshtastic’s MQTT documentation says packets sent to a broker can be unencrypted when its encryption option is disabled, even if the radio channel uses a key; JSON output is unencrypted, and map reporting includes node information. Review uplinks, downlinks and location reporting rather than assuming a private radio channel stays private after an internet bridge.

Which should you choose?

• You want to join CumbriaCQ’s local mesh: choose MeshCore and follow the Cumbria setup and channels.
• Your friends already use Meshtastic: compatible Meshtastic equipment may be the sensible choice. The retirement of CumbriaCQ’s service does not invalidate their separate mesh.
• You want a self-contained family link: choose one system together, obtain an endpoint for each participant and test at the actual locations. A public community is helpful but not mandatory for a direct in-range pair.
• You want to contribute infrastructure: talk to local users first. Placement, compatible settings, permission to mount equipment and a maintainable power supply matter more than choosing the most aggressive forwarding role.

No universal range or emergency winner

Both depend on terrain, aerials, settings, interference, powered nodes and a recipient. A claimed long-distance contact under favourable conditions is not a household service guarantee. The local winter-power discussion illustrates why even solar infrastructure needs realistic planning.

UK licence exemption depends on compliant equipment and operation under Ofcom’s SRD rules, not the firmware name. Neither system guarantees contact with emergency services. Keep normal emergency contact routes and official warnings first, then practise your chosen mesh as an additional layer.

Make a decision you can test

Ask a prospective correspondent which system, radio profile and channel they use. Confirm your hardware supports it. Arrange a short two-way test, then repeat without your phone’s internet connection. For MeshCore, our first-message guide takes you through this. For an existing CumbriaCQ Meshtastic setup, read the retirement and migration page before changing anything.