Reactive ResumevsRemoteTerm for MeshCore
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Reactive Resume | RemoteTerm for MeshCore | |
|---|---|---|
| Score | 87/100 | 45/100 |
| Rank in category | #1 of 46 in Document Management | #4 of 4 in Amateur Radio |
| GitHub stars | 45 067 | 338 |
| Stars, last 30 days | +1 666 | +1 |
| Stable releases, 12 months | 35 | 10 |
| Latest release | v6.0.8 · 29 Oct 2026 | 3.17.1 · 26 Jul 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Typescript | Python |
Which one should you pick?
Reactive Resume scores 87/100 against 45/100 for RemoteTerm for MeshCore, so it is the safer default.
Reactive Resume ships more often: 35 stable releases in the past year, against 10 for RemoteTerm for MeshCore.
If you want the quickest setup, Reactive Resume is easier to run; RemoteTerm for MeshCore needs more configuration.
Reactive Resume is growing faster right now (+1 666 stars in 30 days).
Reactive Resume details →RemoteTerm for MeshCore details →
Swap a project
Keep Reactive Resume, compare it with
Keep RemoteTerm for MeshCore, compare it with