grimmoryvsRemoteTerm for MeshCore
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| grimmory | RemoteTerm for MeshCore | |
|---|---|---|
| Score | 69/100 | 45/100 |
| Rank in category | #2 of 12 in Book Management | #4 of 4 in Amateur Radio |
| GitHub stars | 4 626 | 338 |
| Stars, last 30 days | +201 | +1 |
| Stable releases, 12 months | 19 | 10 |
| Latest release | v3.5.0 · 21 Sept 2026 | 3.17.1 · 26 Jul 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | MIT |
| Main language | Java | Python |
Which one should you pick?
grimmory scores 69/100 against 45/100 for RemoteTerm for MeshCore, so it is the safer default.
grimmory ships more often: 19 stable releases in the past year, against 10 for RemoteTerm for MeshCore.
If you want the quickest setup, grimmory is easier to run; RemoteTerm for MeshCore needs more configuration.
grimmory is growing faster right now (+201 stars in 30 days).
grimmory details →RemoteTerm for MeshCore details →
Swap a project
Keep grimmory, compare it with
Keep RemoteTerm for MeshCore, compare it with