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