A · level
unsloth
97.1
79,671 stars · Apache-2.0
Self-Hosted
Too close to call · 97.1 to 97.9
A · level
97.1
79,671 stars · Apache-2.0
B · level
97.9
94,538 stars · MIT
unsloth 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. unsloth is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 97.1 for unsloth and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to unsloth's 79,671, a gap of 14,867 (1.19×). Forks are 7,439 for unsloth and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 98 versus 100.
Push history: unsloth 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 469 for unsloth (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.
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. 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 96 for unsloth and 96 for uptime-kuma. This is a procurement signal, not legal advice.
In Self-Hosted, both unsloth (79,671 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: unsloth is open source, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 2 points (98 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Composite score: unsloth 97.1, uptime-kuma 97.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | unsloth | uptime-kuma |
|---|---|---|
| GitHub stars | 79,671 | 94,538 |
| Forks | 7,439 | 8,860 |
| Open issues | 469 | 852 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 98 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.1 | 97.9 |
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.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 79,671 for unsloth. The gap is 14,867 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both unsloth and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
Neither tool clears a one-point margin. unsloth scores 97.1 and uptime-kuma scores 97.9.