automatic-ripping-machinevsAutoPlexx
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| automatic-ripping-machine | AutoPlexx | |
|---|---|---|
| Score | 66/100 | 45/100 |
| Rank in category | #11 of 141 in Media Management | #88 of 119 in Media Server |
| GitHub stars | 5 439 | 124 |
| Stars, last 30 days | +148 | +2 |
| Stable releases, 12 months | 16 | 4 |
| Latest release | 2.24.4 · 3 Oct 2026 | v2.1.0 · 7 Aug 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Python | Typescript |
Which one should you pick?
automatic-ripping-machine scores 66/100 against 45/100 for AutoPlexx, so it is the safer default.
automatic-ripping-machine ships more often: 16 stable releases in the past year, against 4 for AutoPlexx.
If you want the quickest setup, automatic-ripping-machine is easier to run; AutoPlexx needs more configuration.
automatic-ripping-machine is growing faster right now (+148 stars in 30 days).
Key differences
- Language: automatic-ripping-machine is written mainly in Python, AutoPlexx in Typescript.
- Features only automatic-ripping-machine lists: Asynchronous batched transcoding, Automatic disc insertion detection, Automatic transcoding queue after rip, Blu-ray, DVD and CD ripping and 9 more.
- Features only AutoPlexx lists: Auto-discovering dashboard, Automated container updates, Built-in stream analytics, Comprehensive monitoring stack and 9 more.
automatic-ripping-machine details →AutoPlexx details →