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