a-trainvssimon
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| a-train | simon | |
|---|---|---|
| Score | 28/100 | 47/100 |
| Rank in category | #113 of 118 in Media Server | #71 of 105 in Monitoring & observability |
| GitHub stars | 17 | 162 |
| Stars, last 30 days | +0 | +1 |
| Stable releases, 12 months | 0 | 5 |
| Latest release | — | 0.3.7 · 18 Oct 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | — | MIT |
| Main language | Rust | Rust |
Which one should you pick?
simon scores 47/100 against 28/100 for a-train, so it is the safer default.
simon ships more often: 5 stable releases in the past year, against 0 for a-train.
If you want the quickest setup, simon is easier to run; a-train needs more configuration.
simon is growing faster right now (+1 stars in 30 days).
a-train is archived, so it won't get fixes. Prefer the other one for anything long-lived.
Key differences
- Platforms only simon lists: Linux.
- Features only a-train lists: Autoscan trigger integration, Google Drive Shared Drive monitoring, Multiple Shared Drive support, Rust binary installation and 1 more.
- Features only simon lists: Alerting with multiple notification channels, Cross-Platform Support, Password Authentication, Real-time system monitoring and 2 more.
a-train details →simon details →
Swap a project
Keep a-train, compare it with
Keep simon, compare it with