Deploy KitchenOwl
Shared grocery lists, recipes and meal planning for your household
KitchenOwl
Just deployed
/data
Just deployed
/var/lib/postgresql/data
Deploy and Host KitchenOwl on Railway
KitchenOwl is an open-source grocery list and recipe manager for households. Members share shopping lists that sync in real time, collect recipes (including imports from recipe websites), plan meals for the week and split household expenses. It has a web app plus Android and iOS apps that connect to your own server.
About Hosting KitchenOwl
Hosting KitchenOwl means running its Python backend (which also serves the web app) next to a database, keeping uploaded photos on persistent storage, and securing the first account. This template builds KitchenOwl v0.8.1 from the official tombursch/kitchenowl image, pinned by version and digest, and uses Railway's PostgreSQL for the data. Uploads sit on a volume at /data. On every boot a small wrapper waits for Postgres and runs the database migrations. On the first boot it creates the admin account with a generated password before the web server starts, so nobody else can claim your instance first.
Common Use Cases
- Shared grocery lists for a family or flatmates that update live on every phone
- A private recipe collection with web imports and a weekly meal planner that fills the shopping list
- Tracking and splitting shared household expenses
Dependencies for KitchenOwl Hosting
- KitchenOwl v0.8.1 (official all-in-one image: Flask backend under uWSGI plus the Flutter web app)
- PostgreSQL (Railway's Postgres service) for users, households, lists, recipes and expenses
Deployment Dependencies
- KitchenOwl source and releases: https://github.com/TomBursch/kitchenowl/releases/tag/v0.8.1
- Self-hosting docs: https://docs.kitchenowl.org/latest/self-hosting/
- Configuration options: https://docs.kitchenowl.org/latest/self-hosting/advanced/
- Template repository: https://github.com/aalfath/kitchenowl-railway-template
Implementation Details
Services:
- KitchenOwl: web app and API on port 8080 with a public domain, health check on
/api/health/…, volume at/datafor uploaded photos. Built from the template repository, so you get Railway's update notice when a new KitchenOwl version is pinned there. - Postgres: Railway's PostgreSQL with its own volume, reached over the private network through
DATABASE_URL.
After deploying:
- Open the KitchenOwl service's public URL.
- Log in as
admin. The password isKITCHENOWL_ADMIN_PASSWORDon the KitchenOwl service's Variables tab (used only on the first boot). - Create your household and add other members under Settings, Server, Users. Public sign-up is off; set
OPEN_REGISTRATION=trueif you want it. - In the mobile apps, enter
https://YOUR-DOMAINas the server.
Optional settings you can add later on the KitchenOwl service: SMTP (SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASS, SMTP_FROM) for password-reset emails, OIDC single sign-on (OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET), and LLM_MODEL with a provider key for AI ingredient parsing.
Resources: both services run within 0.5 GB RAM and 1 vCPU each (KitchenOwl idles at about 300 MB). Give KitchenOwl 1 GB if you enable an LLM model.
Updates: when a new KitchenOwl release is pinned in the template repository, Railway offers you the update. Applying it rebuilds the service and runs the database migrations on start; your data in Postgres and /data stays. Read the repository's CHANGELOG.md first and back up before large jumps.
Why Deploy KitchenOwl on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying KitchenOwl on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
