Free · open source · self-hosted

Your MeshCore radio, on every screen at home.

MeshHome keeps one connection to a MeshCore companion radio, saves every message it hears, and gives you a fast chat inbox in the browser on any phone, tablet or computer on your network.

  • Every message saved, even with no browser open
  • No cloud account
  • Raspberry Pi, Docker or Kubernetes
MeshHome in a desktop browser: the conversation list beside a direct message where a contact asks /weather and the home node replies with the temperature, humidity and wind.
MeshHome on a phone: the inbox with direct messages and channels.

Screenshots use sample conversations on MeshHome's built-in simulated radio.

What it does

Everything your radio hears, in one inbox.

MeshHome runs on a small server at home and stays connected to your radio around the clock. Open it from any browser on your network and pick up where you left off.

Channels and direct messages

Search, unread counts, favourites and drafts, with live updates in every open browser. Delivery states say what the radio actually confirmed.

See how messages travel

Signal (SNR and RSSI), hops, and every path a message took through the mesh, with repeaters named from your contacts.

Contacts and a live map

A contact list that follows the radio's adverts, and a map of every node that shares its position, filtered by type and when it was last heard.

Your radio's settings

Name and location, region presets, channels with QR codes and region scopes, routing and telemetry, checked against the firmware's limits before sending.

Manage your repeaters

Log in to repeaters and room servers for their status, command line and settings. Nothing is fetched until you ask, to save airtime.

A bot, with apps

Friends can message your node with /info or /ping. Add commands such as /weather from the app catalog. Apps are recipes, not code.

Install it like an app

With HTTPS on, add MeshHome to your phone's home screen or your computer's dock, with notifications sent by your own server.

An API for your scripts

API keys let other services read and send messages and follow events live. The API is documented.

Backups and easy updates

Encrypted backup and restore of the whole installation. On a Pi, a guided installer, HTTPS with Let's Encrypt, and one-click updates that roll back if anything fails.

Know your mesh

See who's out there, and how far your messages reach.

Every node your radio hears lands on the map at the position it advertises. Open any hop in a message's path to see which repeater carried it, how far away it is, and the town it's in.

  • Companions, repeaters, room servers and sensors
  • Filter by type and by when each node was last heard
  • OpenStreetMap by default, or your own tile server
MeshHome's node map: companions, repeaters, room servers and sensors as coloured markers on a street map, with the home node in the middle.
How it works

At home, away, or off-grid.

MeshHome stays at home next to your radio and collects messages around the clock. How you reach it depends on where you are.

A repeater on a hill sends messages by LoRa to the radio inside a house. The radio is connected to a Raspberry Pi running MeshHome and a Wi-Fi router. A person on the couch reads the inbox on their phone over Wi-Fi.
  1. 1
    Messages arrive by radioYour home radio hears channels and direct messages day and night, through nearby repeaters.
  2. 2
    MeshHome saves themEvery message goes into your archive, even when nobody has MeshHome open.
  3. 3
    Read and reply on Wi-FiOpen MeshHome on any phone, tablet or computer at home. No Bluetooth pairing, and no radio in your pocket.
A person in town on mobile data. Their phone connects through an encrypted VPN tunnel across the internet to the router at home and opens MeshHome. The radio at home sends their reply over LoRa.
  1. 1
    Connect to homeYour phone joins your home network through a VPN you run, such as WireGuard or Tailscale.
  2. 2
    Open MeshHome as usualEverything is there, just as at home. MeshHome itself stays closed to the internet.
  3. 3
    Your home radio sends itReplies go out over LoRa from the radio at home, wherever you are.

MeshHome doesn't include a VPN. Use the one you already have, or your router's.

A person outside sends /weather from a phone paired with a pocket LoRa radio. The message goes to a repeater on the roof of a house, then to the LoRa radio and Raspberry Pi inside, and MeshHome replies with the weather.
  1. 1
    Ask from your phoneSend /weather to your home node in the MeshCore app.
  2. 2
    Your pocket radio sends itThe phone passes the message to a small LoRa radio over Bluetooth.
  3. 3
    A repeater relays itA repeater up high passes it along, kilometres further.
  4. 4
    The home radio hears itThe radio at home receives it and hands it to MeshHome.
  5. 5
    MeshHome answersIt saves the message, and the bot replies by the same route. No internet or mobile signal needed.
Two ways to set it up

One box, or a radio wherever reception is best.

MeshHome talks to the radio with the MeshCore companion protocol over TCP. The radio can sit on the Raspberry Pi itself, or anywhere on your network.

All in one: a Raspberry Pi with a radio HAT

The LoRa radio plugs straight onto the Pi. One device, one power supply, and the installer sets up everything.

All-in-one Raspberry Pi The LoRa mesh reaches a radio HAT on the Raspberry Pi. ZephCore drives the HAT over SPI and serves the companion protocol on port 5000 on the Pi itself. MeshHome connects to it, stores messages in PostgreSQL, and serves browsers on the home network, optionally through nginx with HTTPS. LoRa mesh radios and repeaters RASPBERRY PI 4 OR 5 Radio HAT RAK6421 + RAK13300 LoRa SPI ZephCore radio service on port 5000 MeshHome inbox and API bot and apps message archive PostgreSQL your archive nginx HTTPS, optional LAN Your devices phone, tablet, PC

Good for

  • A first MeshHome, with one device to set up
  • A tidy box on a shelf, with the antenna by a window

You need

  • A Raspberry Pi 4 or 5 with 64-bit Raspberry Pi OS
  • A RAK6421 HAT with a RAK13300 LoRa module, and an antenna
  • The native installer, which sets up the HAT

Networked: a radio over TCP, MeshHome anywhere

A companion radio with Ethernet or Wi-Fi sits where reception is best, such as the attic or a mast on PoE. MeshHome runs on a Pi, a Debian machine, Docker or Kubernetes, and connects to it over the network.

Radio on the network, MeshHome on a server or container The LoRa mesh reaches a companion radio with Ethernet or Wi-Fi. MeshHome, running on a Raspberry Pi, Debian, Docker or Kubernetes, connects to the radio over TCP port 5000 on the home network, stores messages in PostgreSQL, and serves browsers on the home network. LoRa mesh radios and repeaters Companion radio ThinkNode M7, or RAK4631 + Ethernet PoE: mount it high TCP :5000 Ethernet or Wi-Fi MeshHome inbox, API, bot message archive connects to the radio PostgreSQL your archive RUNS ON PI · DEBIAN · DOCKER · K8S Your devices phone, tablet, PC

Good for

  • Putting the radio high up, on one PoE cable, while the server stays indoors
  • Running MeshHome next to your other services in Docker or Kubernetes

You need

  • A MeshCore companion radio with Ethernet or Wi-Fi firmware (supported radios)
  • A Pi, Debian machine, Docker host or Kubernetes cluster that can reach it
  • A firewall rule so only MeshHome can reach the radio's port
Install

Up and running in a few minutes.

After installing, open MeshHome in a browser and a short wizard sets up your account and radio. No radio yet? Choose the simulated radio to look around.

Raspberry Pi or Debian

Guided installer

Shows every change before making it, and can set up HTTPS and a radio HAT.

curl -fsSLo install.sh \
  https://github.com/roach0816/MeshHome/releases/latest/download/install.sh
sudo bash install.sh
Raspberry Pi guide
Docker Compose

One machine

The app and its database, from the repository.

git clone https://github.com/roach0816/MeshHome.git
cd MeshHome && cp .env.example .env
docker compose up -d --build
Container guide
Kubernetes

K3s with Fleet

Multi-arch images for amd64 and arm64, sized for Raspberry Pi nodes, with health probes and a GitOps deployment.

Kubernetes guide
Private by design

Your messages stay on your server.

No account, no cloud

MeshHome runs on your hardware. Messages, contacts and settings live in your own database, and the project never receives them.

No tracking

MeshHome sends no usage data anywhere. The few outside services it uses, such as update checks, are listed and can be turned off.

Encrypted backups

Backups are always encrypted with your passphrase. Passwords are stored only as hashes, and API keys only as fingerprints.

Read the privacy policy

Open source

Free, MIT licensed, and built in the open.

Read the code, follow releases, and tell us what works on your hardware.