HealthchecksvsRemoteTerm for MeshCore
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Healthchecks | RemoteTerm for MeshCore | |
|---|---|---|
| Score | 73/100 | 45/100 |
| Rank in category | #2 of 12 in Uptime Monitoring | #4 of 4 in Amateur Radio |
| GitHub stars | 10 468 | 337 |
| Stars, last 30 days | +106 | +0 |
| Stable releases, 12 months | 12 | 10 |
| Latest release | v5.0.3 · 27 Oct 2026 | 3.17.1 · 26 Jul 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | BSD-3-Clause | MIT |
| Main language | Python | Python |
Which one should you pick?
Healthchecks scores 73/100 against 45/100 for RemoteTerm for MeshCore, so it is the safer default.
Healthchecks ships more often: 12 stable releases in the past year, against 10 for RemoteTerm for MeshCore.
If you want the quickest setup, Healthchecks is easier to run; RemoteTerm for MeshCore needs more configuration.
Healthchecks is growing faster right now (+106 stars in 30 days).
Healthchecks details →RemoteTerm for MeshCore details →
Swap a project
Keep Healthchecks, compare it with
Keep RemoteTerm for MeshCore, compare it with