Offband MeshCore

Offband MeshCore is an open-source client for MeshCore LoRa mesh radios. Connect a compatible radio and send messages across a LoRa mesh, with no cell service, no internet, no accounts, and no servers in between.

It's built for off-grid and resilient communication: hiking, overlanding, events, emergency preparedness, or anywhere the grid doesn't reach.

Connect your radio
- Bluetooth (BLE), USB serial, or TCP/IP
- Works with MeshCore-compatible LoRa devices from RAK, Heltec, LilyGO, Seeed, and others

Messaging
- Direct (private) messages to your contacts
- Named group channels
- @-mention autocomplete and emoji in the composer
- View the hop-by-hop path a message took across the mesh

Map and network
- See contacts and nodes on a map, with positions from GPS or set manually
- Trace message and repeater routes on the map
- Line-of-sight and terrain analysis between points
- Download map regions for offline use

Radio and repeaters
- Manage and configure repeater nodes
- RF stats (RSSI, SNR, packet counts)
- Battery, sensor, and environmental telemetry
- Raw command-line access for advanced control

Other
- Share channels via QR code
- Available in 18 languages

Privacy by design
Offband has no accounts, no backend, and no analytics or telemetry. Your messages, contacts, and channels stay on your device and travel over your own radio, not through us. It's open source under the MIT license.

Requires a MeshCore radio
Offband is a client for MeshCore hardware, so you'll need a MeshCore-compatible LoRa radio to use it.

Offband is an independent open-source project. It's a fork of meshcore-open by zjs81, and a client for the MeshCore ecosystem created by Scott Powell, all under the MIT license.

Recent changes:
Offband Meshcore 1.4.0
A follow-up to the 1.3.0 launch. New button and buzzer settings for headless devices, a one-tap Send Again on channel messages, and more capability detail in Device Info. Fixes: the block list is scoped per radio again, per-radio caches are cleared on reconnect so nothing lingers from another radio, translation-model downloads retry on transient errors, and routed replies use the correct path width.