CookCLI vs RecipeSage
A side-by-side comparison of two self-hosted recipe managers options — licensing, setup difficulty, resource needs, and what each one replaces.
CookCLI
Plain-text recipe markup with a CLI and server
VS
RecipeSage
Recipe keeper, meal planner, and shopping list
| Feature | CookCLI | RecipeSage |
|---|---|---|
| Deploy effort | Read-the-docs project | Under-an-hour setup |
| Health score | 84 · Excellent | 82 · Excellent |
| Category | Recipe Managers | Recipe Managers |
| License | MIT | AGPL-3.0 |
| Language | Rust | TypeScript |
| Setup difficulty | Medium | Medium |
| Min. RAM | 128 MB | 512 MB |
| Deployment | binary, source | docker, source |
| GitHub stars | ★ 1,390 | ★ 965 |
| First released | 2021 | 2018 |
| Replaces | Paprika, Crouton | Paprika, Pepperplate |
What are CookCLI and RecipeSage?
CookCLI
Cooklang is an open-source recipe markup language with a companion CLI and web server called Chef. Recipes are written in plain text and can be served, scaled, and turned into shopping lists.
- Plain-text recipe markup
- Built-in web server
- Shopping list generation
- Recipe scaling
RecipeSage
RecipeSage is a self-hostable recipe management, meal planning, and shopping list application. It supports recipe clipping from any website and collaborative recipe sharing.
- Clip recipes from any site
- Meal planning calendar
- Shopping list generation
- Recipe sharing and collaboration
CookCLI vs RecipeSage: key differences
CookCLI is written in Rust, while RecipeSage is built with TypeScript. Licensing differs — MIT for CookCLI versus AGPL-3.0 for RecipeSage. CookCLI is the lighter option, starting around 128 MB of RAM against 512 MB for RecipeSage. RecipeSage is the more established project (first released 2018), while CookCLI arrived in 2021. RecipeSage lists first-class Docker deployment; CookCLI does not.
Why pick each one
Choose CookCLI if…
- Version-controllable recipes
- No database needed
Watch out for
- Requires learning the syntax
- Minimal UI
Choose RecipeSage if…
- Strong web clipper
- Cross-device sync
Watch out for
- Heavier deployment
- Modest community
Frequently asked questions
Is CookCLI or RecipeSage better?
Neither is universally better. CookCLI has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.
Are CookCLI and RecipeSage free and open-source?
Yes. CookCLI is licensed under MIT and RecipeSage under AGPL-3.0. Both can be self-hosted at no software cost.
Can I run CookCLI and RecipeSage with Docker?
CookCLI: check the project docs for container support. RecipeSage: yes.
Which is lighter on resources, CookCLI or RecipeSage?
CookCLI has the smaller minimum footprint at 128 MB of RAM, compared to about 512 MB for RecipeSage. Real-world usage depends on library size, user count, and enabled features.