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