Recipya 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?
Recipya
Clean self-hosted recipe manager in Go
VS
What To Cook?
Get a recipe to cook today, based on the ingredients you have at home
| Feature | Recipya | What To Cook? |
|---|---|---|
| Category | Recipe Managers | Recipe Managers |
| License | GPL-3.0 | AGPL-3.0 |
| Language | Go | Java |
| Setup difficulty | Easy | Medium |
| Min. RAM | 128 MB | 512 MB |
| Deployment | docker, binary, source | docker |
| GitHub stars | ★ 408 | ★ 67 |
| First released | 2022 | 2025 |
| Replaces | Paprika, Whisk | — |
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 Recipya or What To Cook? better?
Recipya is the stronger all-round pick: it has both the larger community and the simpler easy setup. Consider What To Cook? if its specific feature set fits your needs better.
Are Recipya and What To Cook? free and open-source?
Yes. Recipya is licensed under GPL-3.0 and What To Cook? under AGPL-3.0. Both can be self-hosted at no software cost.
Can I run Recipya and What To Cook? with Docker?
Recipya: yes. What To Cook?: yes.