Skip to content
DevUtils Online

Self-Hosted

neko vs unsloth

unsloth leads by 6.1 · narrow

A

neko

91.8

22,688 stars · Apache-2.0

B · leads

unsloth

97.9

79,671 stars · Apache-2.0

neko versus unsloth is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. neko is written mainly in Go; unsloth is written mainly in Python. The composite score is 91.8 for neko and 97.9 for unsloth.

unsloth has 79,671 GitHub stars to neko's 22,688, a gap of 56,983 (3.51×). Forks are 1,662 for neko and 7,439 for unsloth. On the log scale used inside this pair, adoption is 89 versus 100, and the fork community is 83 versus 100.

Push history: neko was last pushed on 16 November 2026 (1 day ago), and unsloth was last pushed on 17 November 2026 (0 days ago). Open issues stand at 144 for neko (0.006 per star) and 469 for unsloth (0.006 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Both neko and unsloth are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Self-Hosted, both neko (22,688 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: neko is open source, unsloth is open source.

unsloth 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 17 points (83 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

unsloth finishes ahead at 97.9 against neko at 91.8, a 6.1 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

neko versus unsloth metrics
Signal neko unsloth
GitHub stars 22,688 79,671
Forks 1,662 7,439
Open issues 144 469
Adoption 89 100
Activity 100 100
Community 83 100
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 91.8 97.9

unsloth

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, neko or unsloth?

unsloth has more GitHub stars: 79,671 versus 22,688 for neko. The gap is 56,983 stars.

Which was updated more recently, neko or unsloth?

unsloth was pushed more recently: 17 November 2026 versus 16 November 2026 for neko. That is 1 days apart.

Can I self-host both neko and unsloth?

Yes. This catalog marks both neko and unsloth as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, neko or unsloth?

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. 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.

Who wins the neko vs unsloth score?

unsloth scores 97.9 and neko scores 91.8. This page calls that a narrow lead for unsloth.

Related comparisons