selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

automatic-ripping-machinevsnomercy-media-server

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

automatic-ripping-machinenomercy-media-server
Score66/10027/100
Rank in category#11 of 141 in Media Management#116 of 119 in Media Server
GitHub stars5 43912
Stars, last 30 days+148+1
Stable releases, 12 months1690
Latest release2.24.4 · 3 Oct 2026v0.1.657 · 16 Nov 2026
SetupModerateModerate
Official Docker imageYesYes
LicenseMITOther
Main languagePythonC#

Which one should you pick?

automatic-ripping-machine scores 66/100 against 27/100 for nomercy-media-server, so it is the safer default.

nomercy-media-server ships more often: 90 stable releases in the past year, against 16 for automatic-ripping-machine.

automatic-ripping-machine is growing faster right now (+148 stars in 30 days).

Key differences

  • License: automatic-ripping-machine is MIT, nomercy-media-server is Other.
  • Language: automatic-ripping-machine is written mainly in Python, nomercy-media-server in C#.
  • Platforms only automatic-ripping-machine lists: Linux, Podman.
  • Platforms only nomercy-media-server lists: Build from Source, Linux (Binary), Linux (Native), macOS and 1 more.
  • 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 nomercy-media-server lists: Automatic Encoding, Custom Video Player, Hardware Transcoding (AMD), Hardware Transcoding (Intel Quick Sync) and 10 more.

Swap a project

Keep automatic-ripping-machine, compare it with
Keep nomercy-media-server, compare it with