Build Guidebeginner

MeshCore — Lightweight LoRa Mesh Protocol

A rapidly growing open-source LoRa mesh networking protocol with hybrid routing, room servers, and encrypted messaging — a lightweight alternative to Meshtastic with 2,200+ GitHub stars.

Boards:ESP32-S3ESP32nRF52840
Firmware:MeshcoreArduinoPlatformIO
Use Cases:Mesh NetworkingLoRa & WANPortable DeviceGPS Tracking

Overview

MeshCore is a rapidly growing open-source mesh networking protocol (2,200+ stars, 600+ forks) that provides an alternative to Meshtastic with a fundamentally different architecture. It uses hybrid routing — combining flooding and directed routing — to efficiently relay messages across multi-hop LoRa networks. The protocol separates infrastructure (repeaters, room servers) from client devices, so client nodes never waste battery repeating packets.

Key Features

  • Hybrid Routing: Combines flood and directed routing for efficient multi-hop messaging
  • Room Servers: Group messaging via "rooms" hosted on dedicated relay nodes — like IRC channels over LoRa
  • Client Separation: Client devices never act as repeaters, preserving battery life on portable nodes
  • Encrypted Messaging: End-to-end encrypted direct and group messages
  • Companion Apps: iOS app and WebUI for managing nodes from a phone or browser
  • Home Assistant Integration: Bridge mesh messages to your smart home
  • Wide Board Support: Native firmware for T-Beam, T-Echo, T3 S3, T-Deck, T-LoRa Pager, and many more

Getting Started

Flash MeshCore firmware via the web flasher — select your board, click install. The T-Deck runs the "Aurora" client firmware with full keyboard and display support. T-Beam and T-Echo nodes can serve as repeaters or room servers for the mesh infrastructure.

Why This Project

MeshCore is the fastest-growing Meshtastic alternative, with a lean codebase and innovative architecture that separates client and infrastructure roles. The room server concept enables persistent group channels that survive even when all clients go offline — messages are cached and delivered when clients reconnect.

Resources