Easiest Recipe Managers to self-host

Last reviewed Oct 11, 2026 · 687 words

Start with Mealie. It ranks first on this list, it has more than three times the stars of anything else here (about 13,500), and it runs as one container with SQLite by default inside the directory's 512 MB estimate. Like every recipe app in the category it rates "under an hour" rather than ≈5 minutes, because the image is published but the configuration is yours to assemble. In practice the hour goes on the reverse proxy and on changing a default password, not on Mealie itself.

The other easy picks, and who they suit

Mealie wins the default slot because its community is the largest by a wide margin, and for a beginner that means the error message you hit has usually been answered already. Recipya is the interesting runner-up: the lightest app with a real web importer, at a quarter of Mealie's RAM estimate. Tamari has about 140 stars, so treat it as a one-maintainer project and keep exports. Chowdown is the odd one out, with no importer or login at all; you write recipes as files and publish them like a blog.

What "easy" still leaves you to do

Accounts come first. Mealie starts with a default admin login that appears in every tutorial online, so change the email and password before the instance is reachable, and set ALLOW_SIGNUP=false so you invite household members rather than letting strangers register. KitchenOwl has the same issue the other way round: the first account becomes admin, so close registration once your household has signed up.

The reverse proxy matters more than usual here, because a recipe app is used in a shop or a kitchen on a phone. Put it behind HTTPS on a hostname, or put every family phone on a VPN. Set Mealie's BASE_URL to the public address, otherwise shared recipe links point at the wrong host.

Persistence is a single data volume. Mealie keeps recipes, images, and its SQLite database under /app/data; mount that and you have everything. Back it up nightly and before every upgrade.

How much RAM does a recipe manager need?

The directory's 512 MB for Mealie covers one household with room to spare, and KitchenOwl, Tamari, and groceri.es sit at 256 MB. Recipya's 128 MB estimate makes it the one to choose for a Raspberry Pi already running other things. Adding PostgreSQL to Mealie costs another container and some memory; it is worth it once several people edit at once, not before.

When to step up to Tandoor or Grocy

Mealie stops being enough in two specific ways. If you catch yourself wanting ingredient hierarchies, nested sub-recipes, or a structured archive of a big collection, Tandoor (Medium) is the step up, and the Mealie vs Tandoor comparison shows exactly what you gain. If what you want is pantry stock and expiry dates, that is Grocy, and the category's buyer's guide is frank about the discipline it demands. Neither needs more RAM than Mealie.

What I'd do

Run Mealie on SQLite with one data volume, change the default login in the first minute, turn signups off, and put it behind HTTPS so it works on a phone in the shop. Import only the 20 recipes you cook most. If your partner never opens a recipe app but always opens the grocery list, add KitchenOwl next to it rather than replacing it.