Skip to main content

MeshCore Governance and Community

MeshCore is an open-source project with a distributed community and a governance structure that changed significantly in April 2026. Understanding the project landscape helps you navigate firmware choices and community resources.

The April 2026 governance split

In April 2026, the MeshCore project underwent a governance transition:

  • Core team repository: github.com/meshcore-dev/MeshCore — maintained by the core development team (Liam Cottle and collaborators). This is the canonical firmware for the full hardware range, the source for the official MeshCore app, and what regional networks (CascadiaMesh, WCMesh, RegionMesh, NoDakMesh) standardize on.
  • Andy Kirby’s fork (MeshOS): meshcore.co.uk — the original MeshCore founder’s fork, optimized for standalone keyboard devices (T-Deck, T-Deck Plus). Includes the MeshOS firmware and associated tooling.

Both projects share the same underlying protocol and are interoperable on the radio link. A node running MeshCore core team firmware and a node running MeshOS can communicate over the air. The split is about firmware features, hardware focus, and development direction — not protocol compatibility.

Which firmware should you use?

ScenarioRecommended firmware
Standard repeater or router node (Heltec, RAK4631, T-Echo, T-Beam)Core team (github.com/meshcore-dev/MeshCore)
T-Deck or T-Deck Plus standalone keyboard deviceMeshOS (meshcore.co.uk) for best feature set; core team firmware also works
Joining a regional network (CascadiaMesh, RegionMesh, etc.)Core team (regional networks standardize on this)
Ultra-low power ESP32 optimizationEasySkyMesh fork (community project, Heltec V4 family)

Community resources

ResourceURLFor
Core firmware sourcegithub.com/meshcore-dev/MeshCoreSource code, issues, releases
MeshCore web flashermeshcore.io/flasherFlash firmware without local tooling
Web configurationconfig.meshcore.devConfigure nodes via browser
MeshOS (Andy’s fork)meshcore.co.ukT-Deck standalone firmware
Python librarygithub.com/MeshCore-dev/MeshCore_pyPython API for automation
CascadiaMesh (PNW)cascadiamesh.orgPacific Northwest community
WCMesh (West Coast)wcmesh.comWest Coast network
RegionMesh (Central US)regionmesh.comCentral US communities
NoDakMesh (Northern Plains)nodakmesh.orgNorth Dakota & region

Contributing to MeshCore

The project welcomes contributions in several forms:

  • Bug reports: If your device behaves unexpectedly, open an issue on GitHub with firmware version, hardware, and steps to reproduce. Detailed bug reports are the most immediately useful contribution.
  • Hardware compatibility: Testing new devices and reporting what works (or doesn’t) helps the project support more hardware. Especially valuable for less-common boards.
  • Documentation: This wiki is the community’s primary documentation resource. See the Contributing section for how to improve it.
  • Code: Use the standard GitHub PR workflow. Open an issue first for significant changes to discuss the approach before writing code.