a-trainvsMediary Scout
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| a-train | Mediary Scout | |
|---|---|---|
| Score | 28/100 | 65/100 |
| Rank in category | #113 of 118 in Media Server | #11 of 141 in Media Management |
| GitHub stars | 17 | 1 841 |
| Stars, last 30 days | +0 | +243 |
| Stable releases, 12 months | 0 | 13 |
| Latest release | — | v2026.11.16 · 16 Nov 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | No |
| License | — | 0BSD |
| Main language | Rust | Typescript |
Which one should you pick?
Mediary Scout scores 65/100 against 28/100 for a-train, so it is the safer default.
Mediary Scout ships more often: 13 stable releases in the past year, against 0 for a-train.
Mediary Scout is growing faster right now (+243 stars in 30 days).
a-train is archived, so it won't get fixes. Prefer the other one for anything long-lived.
Key differences
- Language: a-train is written mainly in Rust, Mediary Scout in Typescript.
- Only a-train ships an official Docker image.
- Platforms only a-train lists: Docker.
- Platforms only Mediary Scout lists: macOS, Windows.
- 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 Mediary Scout lists: Agent-driven media acquisition, Automated quality selection, Desktop applications, Direct cloud-to-cloud transfer and 11 more.
a-train details →Mediary Scout details →
Swap a project
Keep a-train, compare it with
Keep Mediary Scout, compare it with