A
immich
92.4
119,439 stars · AGPL-3.0
Self-Hosted
uptime-kuma leads by 4.8 · narrow
A
92.4
119,439 stars · AGPL-3.0
B · leads
97.2
94,538 stars · MIT
immich versus uptime-kuma is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. immich is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 92.4 for immich and 97.2 for uptime-kuma.
immich has 119,439 GitHub stars to uptime-kuma's 94,538, a gap of 24,901 (1.26×). Forks are 7,638 for immich and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 98 versus 100.
Push history: immich was last pushed on 17 November 2026 (0 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 725 for immich (0.006 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
immich is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. uptime-kuma is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 52 for immich and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both immich (119,439 stars) and uptime-kuma (94,538 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: immich is open source, uptime-kuma is open source.
The lead is split. immich is furthest ahead on adoption (100 to 98), while uptime-kuma is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
uptime-kuma finishes ahead at 97.2 against immich at 92.4, a 4.8 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | immich | uptime-kuma |
|---|---|---|
| GitHub stars | 119,439 | 94,538 |
| Forks | 7,638 | 8,860 |
| Open issues | 725 | 852 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 98 | 100 |
| Issue health | 84 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.4 | 97.2 |
High performance self-hosted photo and video management solution.
A fancy self-hosted monitoring tool
immich has more GitHub stars: 119,439 versus 94,538 for uptime-kuma. The gap is 24,901 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both immich and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
immich is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. uptime-kuma is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
uptime-kuma scores 97.2 and immich scores 92.4. This page calls that a narrow lead for uptime-kuma.