A · leads
immich
92.6
119,439 stars · AGPL-3.0
Self-Hosted
immich leads by 1.9 · narrow
A · leads
92.6
119,439 stars · AGPL-3.0
B
90.7
22,688 stars · Apache-2.0
immich versus neko 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; neko is written mainly in Go. The composite score is 92.6 for immich and 90.7 for neko.
immich has 119,439 GitHub stars to neko's 22,688, a gap of 96,751 (5.26×). Forks are 7,638 for immich and 1,662 for neko. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 83.
Push history: immich was last pushed on 17 November 2026 (0 days ago), and neko was last pushed on 16 November 2026 (1 day ago). Open issues stand at 725 for immich (0.006 per star) and 144 for neko (0.006 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. neko is listed as Apache-2.0, 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 neko. This is a procurement signal, not legal advice.
In Self-Hosted, both immich (119,439 stars) and neko (22,688 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, neko is open source.
The lead is split. immich is furthest ahead on fork community (100 to 83), while neko is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
immich finishes ahead at 92.6 against neko at 90.7, a 1.9 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 | neko |
|---|---|---|
| GitHub stars | 119,439 | 22,688 |
| Forks | 7,638 | 1,662 |
| Open issues | 725 | 144 |
| Adoption | 100 | 86 |
| Activity | 100 | 100 |
| Community | 100 | 83 |
| Issue health | 84 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 90.7 |
High performance self-hosted photo and video management solution.
A self hosted virtual browser that runs in docker and uses WebRTC.
immich has more GitHub stars: 119,439 versus 22,688 for neko. The gap is 96,751 stars.
immich was pushed more recently: 17 November 2026 versus 16 November 2026 for neko. That is 1 days apart.
Yes. This catalog marks both immich and neko 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. neko is listed as Apache-2.0, 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.
immich scores 92.6 and neko scores 90.7. This page calls that a narrow lead for immich.