CookCLIvsRecipeSage
Two self-hosted Recipe Management projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| CookCLI | RecipeSage | |
|---|---|---|
| Score | 61/100 | 57/100 |
| Rank in category | #3 of 18 in Recipe Management | #5 of 18 in Recipe Management |
| GitHub stars | 1 422 | 984 |
| Stars, last 30 days | +32 | +19 |
| Stable releases, 12 months | 21 | 27 |
| Latest release | v0.39.0 · 24 Oct 2026 | v4.1.0 · 26 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | MIT | AGPL-3.0-only OR Proprietary |
| Main language | Rust | Typescript |
Which one should you pick?
CookCLI scores 61/100 against 57/100 for RecipeSage, so it is the safer default.
RecipeSage ships more often: 27 stable releases in the past year, against 21 for CookCLI.
If you want the quickest setup, CookCLI is easier to run; RecipeSage needs more configuration.
CookCLI details →RecipeSage details →All Recipe Management projects →
Swap a project
Keep CookCLI, compare it with
Keep RecipeSage, compare it with