Meshtastic vs MeshCore, Which is the better solution for the UK?

Off-grid mesh networking has had a quiet revolution over the last couple of years. LoRa radios, long the territory of hobbyists and amateur radio operators, have become genuinely accessible: affordable hardware, solid open-source firmware, and growing communities of people deploying nodes on rooftops, hills, and windowsills across the country.

The two dominant firmware platforms right now are Meshtastic and MeshCore. They run on the same hardware. They serve the same broad purpose. And they make almost entirely different decisions about how to get there. Understanding those decisions is how you pick the right one for your situation.

What they share

Both platforms use LoRa radio technology to send text messages and GPS coordinates between devices without any internet connection, cellular coverage, or infrastructure beyond the nodes themselves. Both are open source. Both run on the same affordable hardware: LILYGO T-Beam, Heltec LoRa 32, RAK WisBlock, and similar boards. If you already have LoRa hardware, you can flash either firmware onto it and switch between them as often as you like. The hardware does not care. It is just firmware.

Neither platform is compatible with the other. A Meshtastic node cannot talk to a MeshCore node. If you are building a network for a group, everyone needs to be on the same system.

The fundamental difference: how messages move

This is where the two platforms diverge entirely, and everything else, battery life, scalability, speed, infrastructure requirements, follows from this one design choice.

Meshtastic: managed flood routing

When a Meshtastic node sends a message, it broadcasts to every node in range. Those nodes check whether they have seen the message before and, if not, rebroadcast it to everyone they can reach. This continues until the message has hopped through the network or hit the hop limit (three hops by default, seven maximum).

The result is a network that is resilient, self-organising, and requires no pre-planned infrastructure. Every node is a potential relay. Add more people with devices and the network organically extends. This is exactly why Meshtastic works well for hiking groups, festivals, and any scenario where the network needs to form and reform around moving people.

The trade-off is radio congestion. In dense networks with many nodes, all that rebroadcasting adds up. Meshtastic has improved significantly here: version 2.6 introduced next-hop routing for direct messages, and version 2.7 disabled unnecessary telemetry broadcasts by default. But the underlying architecture is inherently chattier than MeshCore.

MeshCore: structured routing

MeshCore separates devices into distinct roles. Companions are personal devices, carried by users and paired to a smartphone. Repeaters are fixed infrastructure nodes, placed on rooftops and high ground to form the backbone of the network. The critical difference: companions do not relay traffic for other users. If a message is not meant for you, your companion ignores it.

When you send a message for the first time, MeshCore floods the network to find the recipient, learning the path as it goes. Every subsequent message to that contact travels the learned path directly through the relevant repeaters, with no unnecessary rebroadcasting. If a path breaks, MeshCore retries, then resets and re-learns. The network gets smarter the more you use it.

The result is dramatically less radio congestion, faster message delivery, longer battery life on companion devices, and a hop count of up to 64 rather than Meshtastic’s 7. The trade-off is that the network requires repeater infrastructure to function over distance. Two companions out of direct radio range cannot communicate without a repeater between them. Someone has to plan and deploy that infrastructure.

Feature comparison

Meshtastic: pros and cons

Pros

Hand someone a flashed device and it works. It joins whatever local mesh exists and starts relaying immediately. The community is the largest in the world for LoRa mesh: 40,000+ GitHub stars, an enormous subreddit, and years of community-maintained documentation covering every hardware combination and edge case. When something does not work, someone has probably already had the same problem and written about it. The telemetry and module ecosystem is deep: environmental sensors, range testing, MQTT bridging, ATAK integration for tactical use. Six years of development shows.

Cons

Dense networks get congested. The flood routing model means every node is contributing to channel utilisation regardless of whether their rebroadcast is useful. Delivery confirmation is historically ambiguous: a cloud icon with a checkmark does not guarantee the recipient actually received the message. The seven hop limit is a meaningful constraint for geographically spread deployments. And while version 2.6 and 2.7 have improved efficiency significantly, the fundamental architecture still generates more radio traffic than MeshCore.

MeshCore: pros and cons

Pros

The routing architecture is genuinely better for planned deployments. Less radio congestion, faster delivery, better battery life on personal devices, and 64 hops versus 7. Message delivery confirmation is explicit: the app shows transmission attempts and a clear success or failure result. Room servers provide store-and-forward messaging so members who are temporarily offline catch up when they reconnect. The network gets more efficient the more it is used. For city-scale or region-scale deployments with fixed repeater infrastructure, MeshCore scales in ways that Meshtastic cannot match.

Cons

It is younger. Launched in early 2025, the ecosystem around it is still catching up. Documentation is improving but thinner than Meshtastic’s. The iOS app works but lacks the configuration depth of the Meshtastic equivalent. Community support, while growing rapidly, is a fraction of Meshtastic’s. Most importantly for the UK specifically: the network is less established. MeshCore requires repeater infrastructure, and if nobody in your area has deployed any, two companions cannot communicate beyond direct radio range. You cannot join what does not exist yet.

The UK specifically

Meshtastic has a substantial and growing UK presence. Nodes are visible across England, Scotland, and Wales on the public mesh map. Communities have formed organically in cities and rural areas alike. If you are in a reasonably populated area, there is a reasonable chance there is already a Meshtastic mesh within range, or at least within a node or two. Joining it requires nothing more than flashing a device and setting your region to EU_868.

MeshCore has a notable connection to the UK: the official website is meshcore.co.uk, and the UK was among the first regions outside the US where nodes appeared when the public map launched in April 2025. Growth has been rapid, with 30,000 nodes worldwide by early 2026. But the infrastructure model means UK coverage is patchier and more dependent on deliberate deployment decisions than Meshtastic’s self-organising approach.

The UK’s geography is also relevant. Britain has a lot of elevated terrain, particularly in the north and west, that lends itself well to repeater placement. A well-sited MeshCore repeater on a hill in the Pennines or the Peak District could cover enormous ground. The urban density of England’s cities creates both an opportunity (many potential companion users) and a challenge (radio congestion in dense Meshtastic deployments is a real issue in places like Manchester and London, where MeshCore’s efficiency advantage becomes more meaningful).

The regulatory environment is also worth a mention. Both platforms operate on the 868MHz band in the UK under the EU_868 region setting, which is licence-exempt under Ofcom’s Short Range Devices regulations. Duty cycle limits of 1% apply, which constrains how often nodes can transmit. MeshCore’s lower per-device transmission overhead is a genuine advantage here: companions that do not relay traffic use less of their duty cycle allowance, leaving more capacity for actual messages.

Which one, then?

There is no universal answer, but there are clear patterns.

Choose Meshtastic if:

• You want to join an existing network with minimal friction
• You are deploying for a roaming group (hiking, cycling, events)
• You want the full telemetry and sensor module ecosystem
• Your group includes iPhone users who need a mature app
• You want extensive documentation and community support
• You are new to LoRa mesh and want a proven starting point

Choose MeshCore if:

• You are building planned infrastructure with fixed repeaters
• You are in a dense urban area where channel congestion is a concern
• You want explicit message delivery confirmation
• You are building for a city or region-scale network
• You want store-and-forward messaging via room servers
• You are willing to contribute to an early-stage ecosystem that is moving quickly

Consider running both if:

• You want Meshtastic for community compatibility and MeshCore for a private planned network
• You are evaluating which to commit to longer term
• The same hardware runs both, so the cost of experimenting is just your time

The honest assessment for the UK in 2026: if you want to plug in and participate in something that already exists, Meshtastic is the right choice. If you want to build something deliberate, efficient, and built to scale, MeshCore is the more interesting platform, and the UK’s geography makes it a compelling place to deploy repeater infrastructure.

The two protocols are not enemies. They are different tools. The community is better served by people understanding that than by treating it as a format war.

Meshtastic is a Swiss Army knife. MeshCore is a scalpel. Which one you need depends entirely on what you are cutting.