CookCLI vs Tamari
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
Tamari
Fully-featured self-hosted recipe manager
| Feature | CookCLI | Tamari |
|---|---|---|
| Deploy effort | Read-the-docs project | Under-an-hour setup |
| Health score | 84 · Excellent | 73 · Good |
| Category | Recipe Managers | Recipe Managers |
| License | MIT | MIT |
| Language | Rust | Python |
| Setup difficulty | Medium | Easy |
| Min. RAM | 128 MB | 256 MB |
| Deployment | binary, source | docker, source |
| GitHub stars | ★ 1,390 | ★ 139 |
| First released | 2021 | 2021 |
| Replaces | Paprika, Crouton | Paprika, Mealie |
What are CookCLI and Tamari?
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
Tamari
Tamari is a fully-featured recipe manager web application built with Python and Flask. It stores recipes with ingredients, instructions, nutrition, and photos, and includes meal planning, shopping lists, and an API.
- Detailed recipe records with photos
- Search-as-you-type
- Meal plans and shopping lists
- REST API
CookCLI vs Tamari: key differences
CookCLI is written in Rust, while Tamari is built with Python. CookCLI is the lighter option, starting around 128 MB of RAM against 256 MB for Tamari. CookCLI has the considerably larger community, at 1,390 GitHub stars versus 139. Tamari 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 Tamari if…
- Released under the MIT license
- Easy to set up — beginner-friendly
- First-class Docker support for quick deployment
- Written in Python
Frequently asked questions
Is CookCLI or Tamari better?
Neither is universally better. CookCLI has the larger community, while Tamari is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.
Are CookCLI and Tamari free and open-source?
Yes. CookCLI is licensed under MIT and Tamari under MIT. Both can be self-hosted at no software cost.
Can I run CookCLI and Tamari with Docker?
CookCLI: check the project docs for container support. Tamari: yes.
Which is lighter on resources, CookCLI or Tamari?
CookCLI has the smaller minimum footprint at 128 MB of RAM, compared to about 256 MB for Tamari. Real-world usage depends on library size, user count, and enabled features.