frpvsRemoteTerm for MeshCore
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| frp | RemoteTerm for MeshCore | |
|---|---|---|
| Score | 85/100 | 45/100 |
| Rank in category | #1 of 25 in Proxy | #4 of 4 in Amateur Radio |
| GitHub stars | 110 279 | 338 |
| Stars, last 30 days | +668 | +1 |
| Stable releases, 12 months | 10 | 10 |
| Latest release | v0.71.1 · 14 Oct 2026 | 3.17.1 · 26 Jul 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | No | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Python |
Which one should you pick?
frp scores 85/100 against 45/100 for RemoteTerm for MeshCore, so it is the safer default.
If you want the quickest setup, frp is easier to run; RemoteTerm for MeshCore needs more configuration.
frp is growing faster right now (+668 stars in 30 days).
frp details →RemoteTerm for MeshCore details →
Swap a project
Keep frp, compare it with
Keep RemoteTerm for MeshCore, compare it with