# apitable vs RemoteTerm for MeshCore

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | apitable | RemoteTerm for MeshCore |
|---|---|---|
| Score | 65/100 ✓ | 45/100 |
| Rank in category | #4 of 17 in Low Code | #4 of 4 in Amateur Radio |
| GitHub stars | 15 654 ✓ | 337 |
| Stars, last 30 days | +35 ✓ | +0 |
| Stable releases, 12 months | 0 | 10 ✓ |
| Latest release | — | 3.17.1 · 26 Jul 2026 |
| Setup | Moderate ✓ | Advanced |
| Official Docker image | Yes | Yes |
| License | AGPL-3.0 | MIT |
| Main language | Typescript | Python |

## Which one should you pick?

apitable scores 65/100 against 45/100 for RemoteTerm for MeshCore, so it is the safer default.

RemoteTerm for MeshCore ships more often: 10 stable releases in the past year, against 0 for apitable.

If you want the quickest setup, apitable is easier to run; RemoteTerm for MeshCore needs more configuration.

apitable is growing faster right now (+35 stars in 30 days).

## Details

- [apitable](https://selfhost.directory/project/apitable) (markdown: https://selfhost.directory/project/apitable.md)
- [RemoteTerm for MeshCore](https://selfhost.directory/project/remote-terminal-for-meshcore) (markdown: https://selfhost.directory/project/remote-terminal-for-meshcore.md)

---
Source: https://selfhost.directory/compare/apitable-vs-remote-terminal-for-meshcore