MeshContinuum (MECON) Private beta · Invitation only

MeshCore, without the boundaries of a single device.

Your mesh stays independent. MECON makes it more useful when connected.

Bring messages captured by your Companions and configured observer sources into one web Reader. Keep history, understand reception and manage supported devices while normal MeshCore radio operation remains independent of the Internet.

Status: Private beta · Invitation only · No opening date announced.

Explore the project Express beta interest

Expressing interest opens a public GitHub issue. It does not create an account or guarantee an invitation.

One Reader, more reception

See traffic captured by the sources available to your deployment. Keep one message with its reception evidence, even when several observers hear it.

Manage devices remotely

Check connectivity and health, configure supported devices and send through an authorized Companion gateway. Available actions depend on the device and accepted beta version.

Your infrastructure, your control

MECON is free and intended for open-source release, with hosted, local and hybrid deployment goals. mecon.cloud is one deployment, not a required service. Public self-hosting packages are still to come.

A look at the beta

MECON v0.193.0, private beta. Captured 2026-10-09 in the real application on a demo backend with synthetic devices, names and messages. Signed in, you see this installation's live traffic instead.

The Packets view for one channel message: its route through two repeater hops, the decrypted text, and three receptions by different gateways with their offsets, RSSI and SNR.
One Reader, more reception. One message, kept once, with every reception that heard it.
The Devices list: two Companions and a Repeater, each with its connection, firmware version, battery, uptime, when it was last heard and how many packets it reported.
Manage devices remotely. Connection and health for every device, from one list.
A Companion's Configure page: name and location, and its radio settings matched to the EU/UK (Narrow) community preset, each field marked with the transport that writes it.
Configure a supported device. Settings read from the device and written back over its connection; available actions depend on the device and firmware.
A channel conversation on a phone, with how many observers heard each message.
The same Reader on a phone.

How it fits together

MECON is an application layer around MeshCore. It does not replace MeshCore's packet formats, radio routing, node identities or normal Companion apps. Everything inside the dashed boundary is optional; the MeshCore radios keep talking to each other without it.

MeshContinuum architecture MeshCore radios (Companions, Repeaters, the RF network) connect to observers and MQTT brokers, which connect to the MeshContinuum backend, which serves the Reader web app. A dashed boundary encloses the observers, brokers, backend and Reader as optional; the MeshCore radios sit outside it and keep working peer to peer without any of it. MeshContinuum (optional) MeshCore Companions, Repeaters RF network Observers & MQTT brokers own · shared · public MeshContinuum backend stores · dedupes decrypts · routes one durable record Reader web app RF packets MQTT API keeps working, offline, on its own

Status and getting involved

First external testing is expected on mecon.cloud. Access remains invitation only and timing is not announced. Expressing interest does not create an account or guarantee an invitation.

The public repositories currently contain documentation and target contracts. Application and firmware source publication follows the staged roadmap. Documentation feedback and contract review are welcome now.