The compose file ships a placeholder signing key
KitchenOwl is a self-hosted grocery list and recipe manager. The backend is made with Flask and the frontend with Flutter. Easily add items to your shopping list before you go shopping. You can also create recipes and add items based on what you want to cook.
At a glance
- What is it?
- KitchenOwl is a self-hosted grocery list and recipe manager, a Flutter client over a Flask backend, published as mobile apps and as container images. The default deployment file is honest about what it expects you to change, which makes it a good place to start reading.
- Who is it for?
- KitchenOwl suits a household that wants its grocery list and recipes on its own hardware and does not mind being the operator of a container stack. Four things to check before you point a family at it.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly Dart, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 13, 2026, and from our analysis. They are not legal advice.
Star history
- TomBursch/kitchenowl3,854 ★ · +178
| Repository | 2026-09-11 | 2026-11-13 |
|---|---|---|
| TomBursch/kitchenowl | 3.7k | 3.9k |
178 Stars in the last 63 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The shipped compose file contains a placeholder signing secret and publishes port 80
This is the whole default deployment, and it has two lines worth stopping on:
services:
front:
image: tombursch/kitchenowl-web:latest
restart: unless-stopped
ports:
- "80:80"and, in the backend service, an environment entry reading JWT_SECRET_KEY=PLEASE_CHANGE_ME. The value is uncommented, so a deployment that copies the file and runs it signs its tokens with a key that is published in a public repository. That is a genuine risk rather than a theoretical one, because the key is the thing standing between a forged session and someone's grocery list. The second line is the other half of the same problem. The port mapping has no bind address, so the frontend is published on every interface of the host rather than on loopback, which is the right default for a self-hosted app on a private network and the wrong one on a laptop tethered to a café network. Neither of these is a criticism of the project so much as a consequence of what a self-hosted stack has to assume about the operator. Two other lines are commented out and worth reading, because they are where the project's own opinion shows. One enables an MCP endpoint at /mcp, and the other sets a front URL, pointing at the advanced self-hosting documentation.
Four compose files, and a message queue is one of the backing store choices
The repository root carries four compose files, which tells you the deployment has more than one shape rather than a single supported path. There is the default file shown above, a Postgres variant, a RabbitMQ variant, and a single-container variant. Postgres is the obvious alternative for the relational store. RabbitMQ is the more interesting one, because a message broker is not something a grocery list structurally requires, so its presence implies the backend does asynchronous or fan-out work, most plausibly for the integrations and scraping paths rather than for list items. The single-container file exists for people who do not want a compose stack at all, which is a reasonable concession given the target audience. State lives in a named volume called kitchenowl_data, mounted at /data in the backend, which is the piece you need to back up. Note that all four files are tracked alongside a Dockerfile that builds both halves from source, so the images on Docker Hub and the ones you could build yourself are two different routes to the same application.
An MCP endpoint exists in the configuration and not in the feature list
Buried in the commented environment block of the default compose file is an entry that enables an MCP endpoint at the path /mcp, gated behind a variable named for enabling it and marked optional. Nothing in the feature list mentions it. The seven advertised capabilities are shopping lists with real-time multi-user sync, partial offline support, recipes, recipe sharing, a meal plan, household balances and expense tracking, and the mobile, web and desktop clients. An MCP endpoint is none of those, and it is the only feature in the file that lets something outside the application read or act on your household's data through a protocol designed for tool use. It ships disabled, which is the right default and means an unconfigured instance is not exposed. But it is undocumented outside a comment in a compose file, so if you are reviewing an instance someone else deployed, check whether that variable has been set rather than assuming the surface is only the web UI.
The web build clones the Flutter SDK from GitHub and then upgrades it
The Dockerfile builds the client from source, and the first stage is where a deployment inherits its reproducibility. The base is a rolling Debian tag, not a pinned digest. The build then clones the entire Flutter repository from GitHub on the stable branch, puts it on the path, enables web support, disables analytics, and runs an upgrade before building. So the toolchain version is whatever stable pointed at on the day the image was built, plus whatever the upgrade moved it to, which means two builds of the same commit can differ. The actual application build is a single command with one flag that matters:
RUN flutter build web --release --no-web-resources-cdnDisabling the web resources CDN stops the built page from fetching its own rendering resources from a Google endpoint at runtime, which is the right call for a self-hosted privacy-respecting application and means the container serves everything itself. The same stage copies a localization configuration and a lockfile alongside the manifest, so the client is pinned by pubspec.lock even though the compiler is not.
The backend builder installs a Fortran toolchain and two BLAS libraries
The second stage is a Python 3.14 slim image, and the package list is far larger than a Flask application would suggest. Alongside the usual build essentials it installs gfortran, an OpenBLAS development package, a LAPACK development package, and cmake and ninja, plus a set of C library headers including libicu, libssl, libsqlite3 and libexpat. Fortran and BLAS toolchains in a grocery list backend mean a compiled numerical dependency is being pulled in transitively, most likely through a scientific package that some other dependency requires. It is not a criticism, since a general-purpose Flask app that pulls in a numeric stack is a common and accepted outcome, but it has two practical effects. The backend image is large, and the native build step means you cannot swap the Python image for a different tag without checking whether those compiled extensions still build. If you are pinning images for a reproducible deployment, this is the stage to test first.
The public checklist still has only the alpha box ticked
The project publishes a three-step status ladder and marks the first one complete. Public Alpha is done, with a parenthetical that says things are still being worked on and that rarely things might break. Public Beta, described as stable with most planned features complete, is unticked, as is Public, described as production-ready. So the author is telling you directly that this is alpha software, and the README says the same thing a second time in the body, asking you to keep in mind that the project is still in development. The release history supports that reading without contradicting it: three consecutive patch releases, 0.7.8 in April, 0.7.9 in June, and 0.7.10 in late July 2026, on a cadence of roughly six to eight weeks, with the last commit on the default branch dated 2026-09-26. A nightly-moving container tag against a monthly-ish release is the combination to be careful with, because the tag you deploy is not the release you tested.
The roadmap is a Projects board outside the repository, and four client channels ship separately
The README does not contain a roadmap file. Planned features are pointed at a GitHub Projects board belonging to the maintainer's user account, which means the plan lives outside version control entirely: it can change without a commit, without a review, and without any history that tells you what changed or when. For a project inviting contributions that is a meaningful gap, since the contributing guidance asks you to open an issue before implementing a feature so the work will not be wasted, and that coordination happens against the board rather than against anything in the tree. The same pattern runs through the distribution story. The mobile app ships on the Play Store, on F-Droid, and in the Apple App Store, the backend and website live in their own repositories, a Python client lives in another, and the Home Assistant integration is a fifth repository entirely. So evaluating what you are actually installing means matching a version across five trees, none of which is pinned to the others by anything in this repository.
Editorial conclusion
KitchenOwl suits a household that wants its grocery list and recipes on its own hardware and does not mind being the operator of a container stack. Four things to check before you point a family at it. Replace the placeholder JWT signing key, because the default compose file ships it uncommented and it is the only thing between a forged session and your shopping list. Decide whether the frontend should be published on every interface or on loopback, since the default mapping is unrestricted. Check whether the optional MCP endpoint at /mcp has been enabled on any instance you did not configure yourself, because it appears only in a compose comment rather than in the feature list. And note that the licence is AGPL-3.0 while the app also ships as closed distribution-channel binaries, so read the terms against the way you actually plan to run it.
Frequently asked questions
how to use kitchenowl
Run one of the four compose files in the repository root, which cover the default stack, a Postgres variant, a RabbitMQ variant and a single-container option. The web image publishes port 80 and the backend keeps its state in a named volume mounted at /data. Ready-made clients exist for Android, iOS and the web, and the self-hosting guide covers the setup in more detail.
What is KitchenOwl built from and where do the images come from?
A Flask backend with a Flutter client, built for mobile, web and desktop from the same codebase. Prebuilt images are published to Docker Hub as kitchenowl-web and kitchenowl-backend, and the repository also carries a Dockerfile that builds both halves from source, so there are two routes to the same application.
Is KitchenOwl ready for production use?
The project marks only its first status tier complete. Public Alpha is ticked, with a note that things are still being worked on and rarely things might break, while Public Beta and Public, described as production-ready, are both unticked. Releases move at roughly six to eight week intervals on the 0.7 line.
Does KitchenOwl need Postgres or RabbitMQ to run?
Not for the default deployment. The root holds four compose files: a default one, a Postgres variant, a RabbitMQ variant and a single-container variant, so a message queue is a supported option rather than a requirement. In all of them application state lives in the named volume kitchenowl_data mounted at /data.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/tombursch-kitchenowl)Star history chart for your README
[](https://hysenlabs.com/projects/tombursch-kitchenowl)Was this useful?