KitchenOwl
Smart grocery list and recipe manager
KitchenOwl is a self-hosted grocery list and recipe management application. It offers shared shopping lists, recipe storage, and meal planning with Flutter-based mobile and web clients.
Key features
- Shared grocery lists
- Recipe storage and import
- Meal planning
- Native mobile apps
Pros & cons
Strengths
- Great mobile experience
- Real-time list sync
Trade-offs
- Smaller recipe feature set
- Younger project
KitchenOwl replaces
Last reviewed Sep 13, 2026 · 738 words
The test for a shared grocery list is whether your partner keeps using it after week 2, and KitchenOwl is the first self-hosted one that passed that test in my house. The reason is the client: native Flutter apps on iOS, Android and F-Droid that open in under a second, sync in real time, and work offline in a supermarket with no signal. The recipe manager bolted onto the side is decent and improving, but if recipes are your main goal, Mealie or Tandoor are the bigger projects and the safer pick. Buy KitchenOwl for the list.
What the list does that a notes app cannot
Items are shared objects, not lines of text. Tick "milk" on your phone and it disappears from the other phone within a second or two, with no refresh. Items carry a category (produce, dairy, bakery, whatever you define), and the list sorts itself in the order you walk the aisles once you have arranged the categories to match your shop. Typing "on" suggests "onions" because you have bought them before, and recent purchases sit one tap away in a row under the search box. Multiple households are supported, so a flat-share and a family can share one server with separate lists, and each household can hold several lists (weekly shop, hardware store, holiday). Those four behaviours are the entire product for most people, and they are exactly what AnyList and Bring charge for or wrap in ads.
Recipes: fine for cooking, thin for collecting
Recipes import from a URL through the usual schema.org scraper, so most food blogs land cleanly with ingredients, steps and a photo. The link to the list is the good part: any recipe's ingredients can be added to the shopping list in one tap, scaled to the number of servings, with items you already have unticked. Meal planning is a week view where you drop recipes onto days and then generate the list from the plan. What is missing compared to Mealie: no cookbook organisation beyond tags, no nutrition data, no OCR of paper recipes, weaker search, and a print view that is basic. If you have 400 recipes and want to curate them, you will feel the difference. If you have 40 that you actually cook, you will not.
Deploying it takes one container
services:
kitchenowl:
image: tombursch/kitchenowl:latest
ports:
- "8080:8080"
environment:
- JWT_SECRET_KEY=change-me-to-a-long-random-string
volumes:
- ./kitchenowl:/data
restart: unless-stopped
The default database is SQLite in /data, which is right for a household; a database URL variable switches it to PostgreSQL if you want that, and I would not bother below about 10 users. Memory sits around 100 to 150 MB in practice against the 256 MB listed minimum. Put it behind your usual reverse proxy with HTTPS, because the mobile apps need a URL they can reach from the supermarket, which means either a public hostname or a VPN such as Tailscale on every family phone. The first account you create becomes the admin; close registration afterwards with the OPEN_REGISTRATION setting so the sign-up screen on your public URL stops accepting strangers.
The trade you are making on age
KitchenOwl dates from 2021 and is largely one developer's project, which shows in two ways. Releases come often and the changelog is honest, which is good. Some features arrive half-built and get finished over months, and the recipe side has had schema changes that needed a migration step on update, which is less good. Back up /data before every upgrade; it is a single directory and the whole state lives there. The AGPL-3.0 licence and the 3,600-star count put it in the same tier as Tandoor, so it is not obscure, but it is not Mealie's community either, and a bug report may wait a while.
What I'd do
Run KitchenOwl as the household grocery list, install the app on every phone, spend 10 minutes setting up categories in aisle order, and stop there. Keep or add Mealie if you are the kind of cook who collects recipes, and let its own shopping-list feature sit unused, because KitchenOwl's is better on the phone. For a single person who mostly wants recipes, skip it and go straight to the recipes category for the bigger options.
Compare KitchenOwl
1 head-to-head comparisons.
Similar recipe managers apps
Mealie
Recipe ManagersSelf-hosted recipe manager and meal planner
Replaces Paprika, Plan to Eat
Grocy
Recipe ManagersERP for your home groceries and pantry
Replaces Pantry Check, AnyList
Tandoor Recipes
Recipe ManagersRecipe manager for organizing and planning meals
Replaces Paprika, Plan to Eat
CookCLI
Recipe ManagersPlain-text recipe markup with a CLI and server
Replaces Paprika, Crouton
Bar Assistant
Recipe ManagersManage your home bar while adding your ingredients, searching
RecipeSage
Recipe ManagersRecipe keeper, meal planner, and shopping list
Replaces Paprika, Pepperplate