OpenEats vs What To Cook?
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
What To Cook?
Get a recipe to cook today, based on the ingredients you have at home
| Feature | OpenEats | What To Cook? |
|---|---|---|
| Category | Recipe Managers | Recipe Managers |
| License | MIT | AGPL-3.0 |
| Language | Dockerfile | Java |
| Setup difficulty | Medium | Medium |
| Min. RAM | 512 MB | 512 MB |
| Deployment | docker, source | docker |
| GitHub stars | ★ 698 | ★ 67 |
| First released | 2017 | 2025 |
| Replaces | Paprika, Yummly | — |
Why pick each one
Choose What To Cook? if…
- Released under the AGPL-3.0 license
- First-class Docker support for quick deployment
- Written in Java
- Lightweight — runs in 512 MB RAM
Frequently asked questions
Is OpenEats or What To Cook? better?
Neither is universally better. OpenEats has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.
Are OpenEats and What To Cook? free and open-source?
Yes. OpenEats is licensed under MIT and What To Cook? under AGPL-3.0. Both can be self-hosted at no software cost.
Can I run OpenEats and What To Cook? with Docker?
OpenEats: yes. What To Cook?: yes.