A · leads
immich
92.6
119,439 stars · AGPL-3.0
Self-Hosted
immich leads by 7.4 · clear
A · leads
92.6
119,439 stars · AGPL-3.0
B
85.2
15,696 stars · AGPL-3.0
immich versus TREK is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 92.6 for immich and 85.2 for TREK.
immich has 119,439 GitHub stars to TREK's 15,696, a gap of 103,743 (7.61×). Forks are 7,638 for immich and 1,342 for TREK. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 81.
Push history: immich was last pushed on 17 November 2026 (0 days ago), and TREK was last pushed on 17 November 2026 (0 days ago). Open issues stand at 725 for immich (0.006 per star) and 19 for TREK (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both immich and TREK are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both immich (119,439 stars) and TREK (15,696 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, TREK is open source.
The lead is split. immich is furthest ahead on fork community (100 to 81), while TREK is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
immich finishes ahead at 92.6 against TREK at 85.2, a 7.4 point clear 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 | TREK |
|---|---|---|
| GitHub stars | 119,439 | 15,696 |
| Forks | 7,638 | 1,342 |
| Open issues | 725 | 19 |
| Adoption | 100 | 83 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 84 | 96 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 85.2 |
High performance self-hosted photo and video management solution.
The most complete open-source travel planner: real-time collaboration, bookings, budgets, packing lists, journals, offline PWA, SSO and an AI-ready MCP server, with planet-wide place search and routing built in.
immich has more GitHub stars: 119,439 versus 15,696 for TREK. The gap is 103,743 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both immich and TREK 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. TREK 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
immich scores 92.6 and TREK scores 85.2. This page calls that a clear lead for immich.