Household Organisation Stack

Last reviewed Oct 11, 2026 · 664 words

Mealie and Grocy overlap more than the stack card suggests, and the setup succeeds or fails on one decision: which app owns recipes and which owns the shopping list. My answer is Mealie for recipes and meal plans, Grocy for stock and chores, and one shopping list that the household agrees to use. The pair needs about 768 MB of RAM by the directory's estimates: 512 MB for Mealie and 256 MB for Grocy.

What each one actually does

Mealie is a recipe manager first. Paste a URL and it scrapes the recipe into a clean, consistent format, though the catalogue notes import accuracy varies by site. Recipes feed a meal-planning calendar, and the plan generates shopping lists. It has a REST API, is rated Easy, and is pleasant enough that non-technical household members will use it unprompted.

Grocy is closer to a small household ERP. It tracks what is in the pantry, freezer and cupboards, with quantities and best-before dates, and also handles chores and tasks. It has recipes and shopping lists of its own, which is where the overlap starts. The catalogue rates it Medium and lists a busy interface and the initial data-entry effort as its downsides, and both are fair.

Do Mealie and Grocy sync with each other?

Not out of the box, as far as either project's built-in features go. Each keeps its own database, its own users and its own lists, and adding an ingredient in one does nothing in the other. You can bridge them through their APIs with a script or an automation tool, but most households do better by dividing the work: plan meals in Mealie, check Grocy for what is already in stock, and add only the missing items to whichever list is the household's single list. That manual check takes a minute and avoids maintaining glue code.

Deploy in this order

Mealie first, because it delivers value on the first evening. Import the twenty recipes you actually cook, plan one week, and see whether the household uses the shopping list. Grocy second, and only once someone is willing to do the initial stock-take; the app is only as useful as its data, and a half-entered pantry is worse than none because nobody trusts it. Start with one category, such as the freezer, where expiry dates matter most.

Both are small enough to run on anything. Put them behind your reverse proxy on their own subdomains so phones in the kitchen and at the shop reach them on the same address. Neither holds anything sensitive enough to warrant SSO in front, and forward-auth tends to get in the way of mobile use; each app's own login is enough.

The mistake: keeping recipes in both

The common failure is entering recipes into Grocy because it has a recipe feature, then importing the same ones into Mealie because its importer is nicer. Within weeks the two copies diverge, the meal plan lives in one app and the stock in the other, and the household stops opening either. Keep recipes in Mealie only, and treat Grocy's recipe screens as features you do not use.

Backups

Each app keeps its data in one volume. Back up both, and make a habit of checking that Mealie's recipe images came along, since they are what makes the collection pleasant to browse.

What I'd do

Run Mealie now, add Grocy when someone in the house volunteers to own the stock-take, and agree on one shopping list before either goes live. The recipes category lists lighter alternatives if Mealie's 512 MB floor matters on your hardware.