CookCLI vs groceri.es
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
groceri.es
Recipe manager and meal planning tool
| Feature | CookCLI | groceri.es |
|---|---|---|
| Deploy effort | Read-the-docs project | Under-an-hour setup |
| Health score | 84 · Excellent | 11 · At risk |
| Category | Recipe Managers | Recipe Managers |
| License | MIT | MIT |
| Language | Rust | HTML |
| Setup difficulty | Medium | Easy |
| Min. RAM | 128 MB | 256 MB |
| Deployment | binary, source | docker, source |
| GitHub stars | ★ 1,390 | ★ 392 |
| First released | 2021 | 2020 |
| Replaces | Paprika, Crouton | Paprika, Mealie |
What are CookCLI and groceri.es?
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
groceri.es
groceri.es is a self-hosted recipe manager and meal planning tool built with Flask. Scheduling recipes onto a weekly planner automatically adds the required ingredients to a grocery list.
- Recipe collection management
- Weekly meal planner
- Automatic grocery lists
- Built with Flask
CookCLI vs groceri.es: key differences
CookCLI is written in Rust, while groceri.es is built with HTML. CookCLI is the lighter option, starting around 128 MB of RAM against 256 MB for groceri.es. CookCLI has the considerably larger community, at 1,390 GitHub stars versus 392. Groceri.es 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 groceri.es if…
- Released under the MIT license
- Easy to set up — beginner-friendly
- First-class Docker support for quick deployment
- Written in HTML
Frequently asked questions
Is CookCLI or groceri.es better?
Neither is universally better. CookCLI has the larger community, while groceri.es is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.
Are CookCLI and groceri.es free and open-source?
Yes. CookCLI is licensed under MIT and groceri.es under MIT. Both can be self-hosted at no software cost.
Can I run CookCLI and groceri.es with Docker?
CookCLI: check the project docs for container support. groceri.es: yes.
Which is lighter on resources, CookCLI or groceri.es?
CookCLI has the smaller minimum footprint at 128 MB of RAM, compared to about 256 MB for groceri.es. Real-world usage depends on library size, user count, and enabled features.