OpenEats vs Tamari
A side-by-side comparison of two self-hosted recipe managers options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
OpenEats
Self-hosted recipe management web application
VS
Tamari
Fully-featured self-hosted recipe manager
| Feature | OpenEats | Tamari |
|---|---|---|
| Category | Recipe Managers | Recipe Managers |
| License | MIT | MIT |
| Language | Dockerfile | Python |
| Setup difficulty | Medium | Easy |
| Min. RAM | 512 MB | 256 MB |
| Deployment | docker, source | docker, source |
| GitHub stars | ★ 698 | ★ 135 |
| First released | 2017 | 2021 |
| Replaces | Paprika, Yummly | Paprika, Mealie |
Why pick each one
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 OpenEats or Tamari better?
Neither is universally better. OpenEats 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 OpenEats and Tamari free and open-source?
Yes. OpenEats is licensed under MIT and Tamari under MIT. Both can be self-hosted at no software cost.
Can I run OpenEats and Tamari with Docker?
OpenEats: yes. Tamari: yes.