English
KitchenOwl Hosting
Plan meals, manage recipes, and share smart shopping lists with your household in real time.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- tombursch/kitchenowl:latest
- Default port
- 8080
How KitchenOwl works
KitchenOwl groups people into households where members can add and complete shopping-list items in real time. Recipes provide reusable ingredient sets, and users can place planned dishes on a meal calendar before adding the required ingredients to a shared list.
Expense and balance tools help a household record purchases and track who paid, while native mobile, web, and desktop clients connect to the same server. Partial offline support lets a client retain useful shopping information during weak connectivity and synchronise changes when it can reach the hosted instance again.
Key KitchenOwl features
The combined model reduces the gap between deciding what to cook and knowing what to buy. Shared recipes can feed the grocery list, meal plans provide context for upcoming purchases, and household balances keep food-related spending near the planning workflow rather than in a separate spreadsheet.
The upstream project explicitly notes that it is still in development. Client behaviour, features, migrations, or compatibility can change as releases evolve. The hosting plan covers the KitchenOwl server application; mobile stores, desktop packages, device notifications, recipe sources, and external services remain separate.
KitchenOwl vs AnyList
KitchenOwl provides self-hosted household lists, recipes, meal planning, expenses, balances, and clients for several device types. AnyList is a provider-operated consumer service with shared grocery lists, recipe organisation, website recipe import, meal-planning calendars, and paid access to expanded web and desktop functionality.
AnyList may be preferable for users who want a mature managed account experience and vendor-maintained applications without running a server. KitchenOwl appeals to households that want control of their shared data and can accept an actively developing project, client setup, account administration, backups, and occasional workflow changes.
Who uses KitchenOwl
Families use KitchenOwl to maintain one shopping list, collect regular recipes, plan dinners, and record shared purchases. Roommates can track household staples and balances, while small community kitchens may coordinate recurring menus and supply runs with a limited group of members.
KitchenOwl is not an online grocery retailer, nutrition service, recipe licensing provider, or payment platform. It organises information entered by users. Ingredient availability, recipe accuracy, dietary safety, expense settlement, and purchase decisions remain the responsibility of the household.
Self-hosting KitchenOwl: requirements and cost
Resource use depends on household members, list updates, recipes, images, meal plans, expense records, synchronisation frequency, and active clients. The catalogue records PostgreSQL and MariaDB as Not required; local application data, uploaded content, and account records still need to remain together during updates and recovery.
On AvaHost, KitchenOwl uses Plan 1 at €2. The hosted KitchenOwl package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The hosting offer supplies the KitchenOwl server. Mobile and desktop clients, app-store accounts, device notifications, recipe rights, grocery delivery, payment processing, and nutritional or dietary advice are not included. The upstream project remains under active development.
F.A.Q
KitchenOwl begins at €2 on Plan 1. A household with ordinary lists, recipes, meal plans, and expense records fits the entry profile. More members, recipe images, frequent synchronisation, long expense history, and several active clients can raise demand. Review usage after importing a large recipe collection.
A custom hostname can expose KitchenOwl through automated HTTPS after its DNS record points to AvaHost. Enter that final server address in each supported client and verify account sign-in, list updates, meal plans, and synchronisation. Remove obsolete server addresses from devices after every member has completed a successful sync.
The AvaHost plan supplies the KitchenOwl server application. Upstream provides clients for mobile, web, and desktop platforms, but app-store distribution, device compatibility, installation, notifications, and client updates are separate. Each household member must install a supported client or use the web interface and connect it to the hosted address.
The upstream project states that it is still in development. Features, clients, migrations, and workflows can change between releases. Automatic application updates and scheduled backups are included, but households should review release changes, keep critical recipes or expense records exportable, and verify list synchronisation after a significant version change.