Home The Playbook Directory
Learn
Settings Guide Field Guides & Resources Certifications
Get
Meshtastic Meshcore Reticulum Nodes About Contact
MeshCore cyberdeck terminal — AI-generated concept render
DIY Build Guides — Live LoRa Edition

Build a Cyberdeck
Mesh Terminal

AI-generated concept render. Build guides below are for real hardware.

A desk terminal that actually talks to the network. Heltec LoRa32 V4 display node, mechanical keyboard, 915 MHz antenna, acrylic base with LED underglow. Three protocols. One hardware platform. Choose your stack.

Build cost ~$87–169
Radio 915 MHz LoRa
Skill Intermediate
Soldering Light
Last updated April 2026

Why this matters now

Something has shifted in how people think about communication infrastructure. It happened gradually — a pandemic that made everyone suddenly aware of how dependent they were on systems they didn't control, then a few years of platform collapses and acquisition drama, and then a quiet resurgence of interest in what it would look like to build the network yourself. The r/cyberdeck community, the Meshtastic Discord, the Reticulum matrix rooms — all of them have been growing. The question being asked isn't hypothetical anymore: what does local, decentralized, owned infrastructure actually feel like to use?

These builds are a partial answer. A LoRa mesh node at desk height inside a stucco house won't reach downtown. But that's not really the point of building one. The point is that it's yours, it runs when the internet doesn't, it talks to other nodes in your neighborhood without touching a server you don't control, and it feels — in a way that a phone app never quite does — like actual infrastructure. Something with weight to it. Something you made decisions about.

The cyberdeck form factor adds something that a bare development board zip-tied to a shelf doesn't: presence. A mechanical keyboard, an OLED map, a glowing acrylic base — it signals that this is a thing you inhabit, not an experiment you're tolerating. That's not purely aesthetic. When a piece of infrastructure looks and feels intentional, you're more likely to leave it running, more likely to maintain it, more likely to actually use it. The mesh grows when nodes stay on.

All three builds here run on the same $18 board. The hardware is a solved problem. What differs is the network philosophy behind each protocol — and which one matches how you think about communication, routing, and the people you're trying to reach.

Choose your protocol

Reticulum / NomadNet

NomadNet

Cyberdeck Terminal

Flashed with RNode firmware, the Heltec becomes a live Reticulum interface device. The OLED draws an animated peer map. rnsd on your host machine sees it as a radio modem. A Python bridge feeds real peer count and RSSI to the display. This is infrastructure for people who have already set up Reticulum.

Build Cost~$160
ProtocolReticulum
FirmwareRNode
DisplayCustom sketch
Read the build guide
MeshCore

MeshCore

Cyberdeck Terminal

Flash via the official web flasher at flasher.meshcore.co.uk. Select BLE Companion, pair with the MeshCore phone app over Bluetooth. The OLED shows your pairing PIN, connection status, and radio state natively. A secondary MCU drives the LED strip from MeshCore's serial debug output — no firmware modifications required.

Build Cost~$160–250
ProtocolMeshCore
FirmwareWeb flasher
DisplayNative OLED
Read the build guide
Meshtastic

Meshtastic

Cyberdeck Terminal

Flash the native heltec-v4 target from flasher.meshtastic.org. The OLED shows channel name, node count, hop limit, and message previews automatically. Configure with the Python CLI or the phone app. Set ROUTER role for a fixed desk node with a real antenna. A secondary MCU triggers LED pulses on mesh activity.

Build Cost~$160–250
ProtocolMeshtastic
FirmwareWeb flasher
DisplayNative OLED
Read the build guide
Hardware note

All three builds use identical hardware — Heltec LoRa32 V4, 3mm clear acrylic base, WS2812B LED strip, M3 brass standoffs, TKL mechanical keyboard, and a 915 MHz whip antenna. The only variable is the firmware you flash and the secondary MCU sketch. If you've already completed one build, switching protocols means reflashing — nothing else changes. STL files and SVG assets at nodestar.net/builds.

Quick comparison

Feature NomadNet
Reticulum
MeshCore Meshtastic
Native OLED (no custom sketch)
Flashing method CLI (rnodeconf) Web flasher Web flasher
Phone app pairing BLE BLE
Host daemon required rnsd Optional Optional
Structured / routed messages Flood
Store-and-forward Via NomadNet ✓ Room Server ✓ Native
LED underglow method Host bridge + GPIO Secondary MCU Secondary MCU
Python API / library rns meshcore_py meshtastic
Build complexity Intermediate Intermediate Intermediate