MeshCore-Self-Hosted
Self-hosted MeshCore web application with automatic updates.
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
78/100 Good
- Maintained
- 100last commit 7 days ago
- Popular
- 724,110 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 83no serious findings, 2 minor, CI, tests
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 20 days ago
- GitHub stars
- 4,110
- Open issues
- 926
- Last commit
- 2026-11-14
- Latest release
- companion-v1.18.0
- License
- MIT
- Activity
- declining
Checked today - source: GitHub (meshcore-dev/meshcore)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Save region changes before you finish After you create or change regions in the MeshCore CLI, run `region save` so the new settings are written to persistent storage. If you skip it, MeshCore may forget the changes on restart and use the old region setup. source
- Start packet logs for troubleshooting Run `log start` in the CLI if you want MeshCore to save packet activity to a file. Without this, you may not have a log to review when connections or messages stop working. source
- Bluetooth firmware requirement Your MeshCore device must be flashed with BLE companion firmware to use Bluetooth. source
- HTTPS required for Bluetooth Bluetooth requires HTTPS — place a reverse proxy such as Cloudflare Tunnel or Nginx Proxy Manager in front of this container. source
Fetched 47 days ago - each note links to its source
Variants
Alternatives (1)
- Meshtastic - Meshtastic is a project that enables you to use inexpensive LoRa radios as a long range off-grid communication platform in areas without ex…
Checked 54 days ago - source: AlternativeTo
Common questions
How do updates work for the self-hosted MeshCore web app?
The container downloads the latest MeshCore web release on startup. It then checks for updates daily.
How can I capture packet logs when troubleshooting MeshCore?
Run log start in the MeshCore CLI to save packet activity to a file. Without this, there may be no log to review when connections or messages stop working.
Will region changes survive a restart?
Only if you run region save after creating or changing regions in the CLI. If you skip it, MeshCore may forget the changes and use the old region setup on restart.
Answers sourced from github.com, github.com, github.com
Community
- [Support] MeshCore Self-Hosted - Self-hosted MeshCore Web ... - Unraid (forum)
- Mesh VPN - WireGuard admin : r/selfhosted - Reddit (reddit)
Collected 49 days ago - public community threads