Fork Recipes vs Recipya
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?
Fork Recipes
Manage your food recipes with simplicity
VS
Recipya
Clean self-hosted recipe manager in Go
| Feature | Fork Recipes | Recipya |
|---|---|---|
| Category | Recipe Managers | Recipe Managers |
| License | BSD-3-Clause | GPL-3.0 |
| Language | HTML | Go |
| Setup difficulty | Medium | Easy |
| Min. RAM | 512 MB | 128 MB |
| Deployment | docker | docker, binary, source |
| GitHub stars | ★ 68 | ★ 408 |
| First released | 2025 | 2022 |
| Replaces | — | Paprika, Whisk |
Why pick each one
Choose Fork Recipes if…
- Released under the BSD-3-Clause license
- First-class Docker support for quick deployment
- Written in HTML
- Lightweight — runs in 512 MB RAM
Frequently asked questions
Is Fork Recipes or Recipya better?
Recipya is the stronger all-round pick: it has both the larger community and the simpler easy setup. Consider Fork Recipes if its specific feature set fits your needs better.
Are Fork Recipes and Recipya free and open-source?
Yes. Fork Recipes is licensed under BSD-3-Clause and Recipya under GPL-3.0. Both can be self-hosted at no software cost.
Can I run Fork Recipes and Recipya with Docker?
Fork Recipes: yes. Recipya: yes.