CookCLIvsOpenEats
Two self-hosted Recipe Management projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| CookCLI | OpenEats | |
|---|---|---|
| Score | 61/100 | 47/100 |
| Rank in category | #3 of 18 in Recipe Management | #10 of 18 in Recipe Management |
| GitHub stars | 1 423 | 696 |
| Stars, last 30 days | +33 | — |
| Stable releases, 12 months | 21 | 0 |
| Latest release | v0.39.0 · 24 Oct 2026 | — |
| Setup | Easy | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | MIT |
| Main language | Rust | Dockerfile |
Which one should you pick?
CookCLI scores 61/100 against 47/100 for OpenEats, so it is the safer default.
CookCLI ships more often: 21 stable releases in the past year, against 0 for OpenEats.
If you want the quickest setup, CookCLI is easier to run; OpenEats needs more configuration.
CookCLI is growing faster right now (+33 stars in 30 days).
CookCLI details →OpenEats details →All Recipe Management projects →
Swap a project
Keep CookCLI, compare it with
Keep OpenEats, compare it with