A
TREK
86.3
15,696 stars · AGPL-3.0
Self-Hosted
unsloth leads by 11.6 · clear
A
86.3
15,696 stars · AGPL-3.0
B · leads
97.9
79,671 stars · Apache-2.0
TREK versus unsloth is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. TREK is written mainly in TypeScript; unsloth is written mainly in Python. The composite score is 86.3 for TREK and 97.9 for unsloth.
unsloth has 79,671 GitHub stars to TREK's 15,696, a gap of 63,975 (5.08×). Forks are 1,342 for TREK and 7,439 for unsloth. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 81 versus 100.
Push history: TREK was last pushed on 17 November 2026 (0 days ago), and unsloth was last pushed on 17 November 2026 (0 days ago). Open issues stand at 19 for TREK (0.001 per star) and 469 for unsloth (0.006 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. unsloth 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 TREK and 96 for unsloth. This is a procurement signal, not legal advice.
In Self-Hosted, both TREK (15,696 stars) and unsloth (79,671 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: TREK is open source, unsloth is open source.
The lead is split. TREK is furthest ahead on issue health (96 to 84), while unsloth is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
unsloth finishes ahead at 97.9 against TREK at 86.3, a 11.6 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 | TREK | unsloth |
|---|---|---|
| GitHub stars | 15,696 | 79,671 |
| Forks | 1,342 | 7,439 |
| Open issues | 19 | 469 |
| Adoption | 86 | 100 |
| Activity | 100 | 100 |
| Community | 81 | 100 |
| Issue health | 96 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.3 | 97.9 |
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.
Local UI to run and train LLMs and diffusion models. Supports GGUF, MLX, Qwen3.8, DeepSeek-V4.1, MiniMax-H3, Gemma 4, FLUX and more.
unsloth has more GitHub stars: 79,671 versus 15,696 for TREK. The gap is 63,975 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both TREK and unsloth as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. unsloth 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.
unsloth scores 97.9 and TREK scores 86.3. This page calls that a clear lead for unsloth.