a-trainvsautopulse
Two self-hosted Media Server projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| a-train | autopulse | |
|---|---|---|
| Score | 28/100 | 55/100 |
| Rank in category | #113 of 118 in Media Server | #46 of 118 in Media Server |
| GitHub stars | 17 | 556 |
| Stars, last 30 days | +0 | +3 |
| Stable releases, 12 months | 0 | 4 |
| Latest release | — | v2.0.0 · 5 Jun 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | — | MIT |
| Main language | Rust | Rust |
Which one should you pick?
autopulse scores 55/100 against 28/100 for a-train, so it is the safer default.
autopulse ships more often: 4 stable releases in the past year, against 0 for a-train.
autopulse is growing faster right now (+3 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 autopulse lists: Unraid.
- 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 autopulse lists: Basic Authentication, Configuration template API, Database-backed reliability, File existence and hash verification and 6 more.
a-train details →autopulse details →All Media Server projects →
Swap a project
Keep a-train, compare it with
Keep autopulse, compare it with