CrossWatchvsMediary Scout
Two self-hosted Media Management projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| CrossWatch | Mediary Scout | |
|---|---|---|
| Score | 55/100 | 65/100 |
| Rank in category | #44 of 141 in Media Management | #11 of 141 in Media Management |
| GitHub stars | 1 020 | 1 841 |
| Stars, last 30 days | +58 | +243 |
| Stable releases, 12 months | 57 | 13 |
| Latest release | v0.14.8 · 22 Nov 2026 | v2026.11.16 · 16 Nov 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | No |
| License | AGPL-3.0 | 0BSD |
| Main language | Python | Typescript |
Which one should you pick?
Mediary Scout scores 65/100 against 55/100 for CrossWatch, so it is the safer default.
CrossWatch ships more often: 57 stable releases in the past year, against 13 for Mediary Scout.
Mediary Scout is growing faster right now (+243 stars in 30 days).
Key differences
- License: CrossWatch is AGPL-3.0, Mediary Scout is 0BSD.
- Language: CrossWatch is written mainly in Python, Mediary Scout in Typescript.
- Only CrossWatch ships an official Docker image.
- Platforms only CrossWatch lists: Docker.
- Platforms only Mediary Scout lists: macOS, Windows.
- Features only CrossWatch lists: Analyzer and debugging tools, Anime ID mapping, CLI-only mode, Custom mappings and 11 more.
- Features only Mediary Scout lists: Agent-driven media acquisition, Automated quality selection, Desktop applications, Direct cloud-to-cloud transfer and 11 more.
CrossWatch details →Mediary Scout details →All Media Management projects →