Contents

  1. 1AI News & ModelsWhich model, what changed, what it costs.
  2. 2Agents & AI CodingWhat works, what breaks, how to run them safely.
  3. 3Local AI LabPrivate AI on hardware you own.
  4. 4AI Security & SovereigntyKeep your data and your agents on a leash.
  5. 5Off-Grid AI & CommsMesh, radio, solar, and offline knowledge.
Subscribe to the Signal Report

Off-Grid AI & Comms

Meshtastic vs MeshCore: how they route, what they run on, how to choose

By TechnicalPrepper4 min read✓ Checked Nov 12, 2026

What each one is

Both projects send short messages over LoRa radio with no internet or cell service. Both are open source. They differ in how messages travel.

Meshtastic carries text messages and position reports across a mesh of nodes. Its firmware repo is GPL-3.0, with 8.6k stars and 2.9k forks as of Nov 12, 2026 (GitHub).

MeshCore is described in its README as a lightweight C++ library for multi-hop routing on LoRa and similar radios. It is MIT licensed, with 4.0k stars and 1.6k forks on the same date.

Stars are a rough signal of interest, not of users. Neither site gives a node or member count that we could find.

How routing differs

Meshtastic, per its routing docs:

  • Broadcasts use “managed flooding.” Nodes rebroadcast up to a hop limit, but skip it if they hear a neighbor already did.
  • Since version 2.6, direct messages start with flooding, then learn a next hop per hop. They fall back to flooding if that fails.
  • The hop limit defaults to 3 and cannot exceed 7, per the LoRa config page.

MeshCore, per its FAQ:

  • Companion (user) nodes do not repeat. Repeaters and room servers do.
  • Group channels always flood. A new direct message floods once, then the sender stores the path of repeaters and reuses it.
  • If a stored path breaks, the app retries, then floods on the last try by default.
  • The firmware caps routes at 64 hops, though the FAQ says real paths rarely get close.

The MeshCore FAQ says Meshtastic floods every message. Meshtastic’s docs describe next-hop routing for direct messages since 2.6. So that comparison may be dated. We could not tell how the two behave side by side, and we did not test either.

Hardware

Meshtastic’s device page lists boards from RAK, LILYGO, Heltec, Seeed, and others, on nRF52, ESP32, and RP2040 chips, plus Linux through meshtasticd. It recommends newer SX126x or LR11xx radios over older SX127x.

MeshCore’s site lists Heltec, Wio Tracker, ThinkNode, and WisMesh devices as companions, and SenseCAP Solar Node as a repeater. Its README sends you to the MeshCore Flasher for the full supported list.

Many boards overlap. Check each project’s list for the exact model before you buy.

Apps

  • Meshtastic: clients connect to a node over Bluetooth, Wi-Fi, Ethernet, or serial, per the overview page.
  • MeshCore: the site lists apps for Android, iOS, Windows, macOS, Linux, and the web. Some devices run standalone firmware with no phone.

Encryption, as documented

Meshtastic has a detailed encryption page. Channel messages use AES with a shared key. Direct messages use public-key exchange (X25519) with AES-256-CCM. Newer firmware (2.8 and up) adds options like signed broadcasts. The default public channel key is published, so that traffic is readable by anyone. The page lists limits too, including no forward secrecy, and says it is not equivalent to Signal or TLS 1.3.

MeshCore’s site says messages are end-to-end encrypted. The FAQ says adverts carry a public key and are signed. We found no page that states the algorithms, so we cannot compare strength.

How to choose

  • Choose Meshtastic if you want a long hardware list and detailed public docs, and your local group already uses it.
  • Choose MeshCore if you want chat with repeaters and learned routes, and your local group already uses it.
  • Either way, ask who is nearby. One lone node does nothing.

Range

Both projects speak of kilometers, but results swing with terrain, antenna, height, and settings. Meshtastic’s docs say slower presets reach farther and faster ones less far. We state no number. The only range that matters is the one you measure with your own nodes.

Radio rules

Meshtastic’s LoRa page says its power table shows firmware ceilings, not national limits, and advises you to check your national band plan. It also warns not to use amateur-radio regions without a license. In the US, the rule text for unlicensed devices is 47 CFR Part 15, and the FCC is the regulator. Readers elsewhere should look up their own regulator.

What to do next

  1. Ask on your local group’s channel which one is in use near you.
  2. Buy one companion node plus one repeater-capable node that both projects list.
  3. Set your radio region correctly before transmitting. Meshtastic’s node does not transmit until a region is set.

Sources

  1. Meshtastic: Overview, Meshtastic (checked Nov 12, 2026)
  2. Meshtastic: Mesh Broadcast Algorithm, Meshtastic (checked Nov 12, 2026)
  3. Meshtastic: Encryption, Meshtastic (checked Nov 12, 2026)
  4. Meshtastic: LoRa Config, Meshtastic (checked Nov 12, 2026)
  5. Meshtastic: Devices, Meshtastic (checked Nov 12, 2026)
  6. meshtastic/firmware repository, Meshtastic on GitHub (checked Nov 12, 2026)
  7. MeshCore repository (README), meshcore-dev on GitHub (checked Nov 12, 2026)
  8. MeshCore FAQ, meshcore-dev on GitHub (checked Nov 12, 2026)
  9. MeshCore, MeshCore (checked Nov 12, 2026)
  10. 47 CFR Part 15, Radio Frequency Devices, Cornell Legal Information Institute (eCFR text) (checked Nov 12, 2026)

Coming soon

The Signal Report

The 5-minute brief on AI and resilient tech. One story, three quick hits, one thing to try.

Launching soon. Signups are not open yet. Until then, follow new posts by RSS.

Keep going

Related