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