CinephagevsRadarr
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Cinephage | Radarr | |
|---|---|---|
| Score | 57/100 | 78/100 |
| Rank in category | #40 of 141 in Media Management | #3 of 46 in Download Management |
| GitHub stars | 918 | 14 793 |
| Stars, last 30 days | +64 | +234 |
| Stable releases, 12 months | 23 | 23 |
| Latest release | v0.18.1 · 3 Nov 2026 | v7.0.3.10918 · 16 Nov 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | GPL-3.0 |
| Main language | Typescript | C# |
Which one should you pick?
Radarr scores 78/100 against 57/100 for Cinephage, so it is the safer default.
If you want the quickest setup, Radarr is easier to run; Cinephage needs more configuration.
Radarr is growing faster right now (+234 stars in 30 days).
Key differences
- Language: Cinephage is written mainly in Typescript, Radarr in C#.
- Platforms only Radarr lists: Docker, FreeBSD, macOS, QNAP and 2 more.
- Features only Cinephage lists: Automated monitoring tasks, Built-in Cloudflare bypass, Cardigann-compatible tracker definitions, Content discovery and requests and 11 more.
- Features only Radarr lists: Automatic library import, Automatic Quality Upgrades, Custom Formats, Customizable quality profiles and 10 more.
Cinephage details →Radarr details →