grocyvsRecipeSage
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| grocy | RecipeSage | |
|---|---|---|
| Score | 75/100 | 57/100 |
| Rank in category | #2 of 15 in Home Management | #5 of 18 in Recipe Management |
| GitHub stars | 9 624 | 983 |
| Stars, last 30 days | +101 | +18 |
| Stable releases, 12 months | 3 | 27 |
| Latest release | v4.7.1 · 4 Sept 2026 | v4.1.0 · 26 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | No | Yes |
| License | MIT | AGPL-3.0-only OR Proprietary |
| Main language | Blade | Typescript |
Which one should you pick?
grocy scores 75/100 against 57/100 for RecipeSage, so it is the safer default.
RecipeSage ships more often: 27 stable releases in the past year, against 3 for grocy.
If you want the quickest setup, grocy is easier to run; RecipeSage needs more configuration.
grocy is growing faster right now (+101 stars in 30 days).
grocy details →RecipeSage details →
Swap a project
Keep grocy, compare it with
Keep RecipeSage, compare it with