CinephagevsJellyfin
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Cinephage | Jellyfin | |
|---|---|---|
| Score | 58/100 | 88/100 |
| Rank in category | #34 of 141 in Media Management | #1 of 119 in Media Server |
| GitHub stars | 910 | 59 279 |
| Stars, last 30 days | +71 | +1 331 |
| Stable releases, 12 months | 23 | 14 |
| Latest release | v0.18.1 · 3 Nov 2026 | v12.4 · 26 Oct 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | GPL-2.0 |
| Main language | Typescript | C# |
Which one should you pick?
Jellyfin scores 88/100 against 58/100 for Cinephage, so it is the safer default.
Cinephage ships more often: 23 stable releases in the past year, against 14 for Jellyfin.
Jellyfin is growing faster right now (+1 331 stars in 30 days).
Key differences
- License: Cinephage is GPL-3.0, Jellyfin is GPL-2.0.
- Language: Cinephage is written mainly in Typescript, Jellyfin in C#.
- Platforms only Jellyfin lists: Windows.
- Features only Cinephage lists: Automated monitoring tasks, Built-in Cloudflare bypass, Cardigann-compatible tracker definitions, Content discovery and requests and 11 more.
- Features only Jellyfin lists: Live TV & DVR, Media Library Management, Multi-platform clients, No Tracking or Telemetry and 2 more.
Cinephage details →Jellyfin details →