A
arcane
88.4
9,189 stars · BSD-3-Clause
Self-Hosted
unsloth leads by 9.5 · clear
A
88.4
9,189 stars · BSD-3-Clause
B · leads
97.9
79,671 stars · Apache-2.0
arcane versus unsloth is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. arcane is written mainly in Go; unsloth is written mainly in Python. The composite score is 88.4 for arcane and 97.9 for unsloth.
unsloth has 79,671 GitHub stars to arcane's 9,189, a gap of 70,482 (8.67×). Forks are 501 for arcane and 7,439 for unsloth. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 70 versus 100.
Push history: arcane 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 11 for arcane (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.
arcane is listed as BSD-3-Clause, 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. 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 96 for arcane and 96 for unsloth. This is a procurement signal, not legal advice.
In Self-Hosted, both arcane (9,189 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: arcane is open source, unsloth is open source.
The lead is split. arcane is furthest ahead on issue health (96 to 84), while unsloth is furthest ahead on fork community (100 to 70). Choose the dimension a rollout cannot compromise on.
unsloth finishes ahead at 97.9 against arcane at 88.4, a 9.5 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 | arcane | unsloth |
|---|---|---|
| GitHub stars | 9,189 | 79,671 |
| Forks | 501 | 7,439 |
| Open issues | 11 | 469 |
| Adoption | 81 | 100 |
| Activity | 100 | 100 |
| Community | 70 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 88.4 | 97.9 |
Modern Docker Management, Designed for Everyone
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 9,189 for arcane. The gap is 70,482 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both arcane and unsloth as self-hostable. Confirm each project's deploy docs before you plan a migration.
arcane is listed as BSD-3-Clause, 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. 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 arcane scores 88.4. This page calls that a clear lead for unsloth.