# CookCLI vs Snipe-IT

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | CookCLI | Snipe-IT |
|---|---|---|
| Score | 61/100 | 77/100 ✓ |
| Rank in category | #3 of 18 in Recipe Management | #1 of 15 in Asset Management |
| GitHub stars | 1 422 | 15 109 ✓ |
| Stars, last 30 days | +32 | +138 ✓ |
| Stable releases, 12 months | 21 ✓ | 17 |
| Latest release | v0.39.0 · 24 Oct 2026 ✓ | v8.8.3 · 22 Oct 2026 |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | AGPL-3.0 |
| Main language | Rust | PHP |

## Which one should you pick?

Snipe-IT scores 77/100 against 61/100 for CookCLI, so it is the safer default.

CookCLI ships more often: 21 stable releases in the past year, against 17 for Snipe-IT.

If you want the quickest setup, CookCLI is easier to run; Snipe-IT needs more configuration.

Snipe-IT is growing faster right now (+138 stars in 30 days).

## Details

- [CookCLI](https://selfhost.directory/project/cookcli) (markdown: https://selfhost.directory/project/cookcli.md)
- [Snipe-IT](https://selfhost.directory/project/snipe-it) (markdown: https://selfhost.directory/project/snipe-it.md)

---
Source: https://selfhost.directory/compare/cookcli-vs-snipe-it