English
Tandoor Hosting
Collect recipes, plan meals, and build shopping lists from what you are cooking this week.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Tandoor’s official links and original website
Tandoor Website
More
Tech
- Docker image
- vabene1111/recipes:latest
- Default port
- 80
- Database
- postgres
How Tandoor works
Tandoor stores recipes with ingredients, steps, keywords, images, and structured metadata. Recipes can be grouped into cookbooks, found through search and filters, or added through supported import paths. Users build meal plans from the collection and turn planned dishes into shopping-list entries.
Shopping lists combine ingredients and can be adjusted while preparing for a trip to the store. Multiple accounts support household or group use, and sharing options make selected recipes accessible to others. The first visitor to the catalogue deployment creates the initial account, so the setup page should be claimed before the hostname is distributed.
Key Tandoor features
A structured recipe library is easier to filter than folders of documents or browser bookmarks. Meal plans connect future cooking to the saved collection, while shopping lists reduce repeated transcription of ingredients. Cookbooks and tags support different cuisines, diets, seasons, or family members.
Import quality varies with the source, and an imported recipe may still need ingredient, unit, image, or instruction cleanup. Tandoor also does not purchase groceries or verify dietary suitability. Application email is disabled, so email invitations, notifications, and mail-based recovery are unavailable in the hosted configuration.
Tandoor vs Paprika
Tandoor is a self-hosted browser application for recipes, meal planning, shopping lists, cookbooks, imports, and multi-user access. Paprika is a commercial recipe manager sold as applications for supported platforms, with a built-in browser, meal plans, grocery lists, and provider-operated synchronization between purchased clients.
Paprika may suit cooks who prefer a polished native application and managed cross-device sync without running a server. Tandoor is appealing when a household wants a shared web library under its own domain and accepts the work of administering accounts, cleaning imports, and maintaining the hosted data.
Who uses Tandoor
Families use Tandoor to replace recipe binders and coordinate weekly meals. Cooking clubs can share a controlled collection, while small food businesses or community kitchens use it to document repeatable recipes and shopping preparation without turning the application into an inventory or purchasing system.
The platform works best when someone maintains consistent ingredient names, units, tags, and images. A large unreviewed import can create duplicate or hard-to-find entries. Establish a simple cataloguing convention early and test account permissions before inviting a wider group to edit the library.
Self-hosting Tandoor: requirements and cost
Tandoor capacity is shaped by recipe count, images, imports, users, search, meal plans, shopping lists, and concurrent browsing. PostgreSQL stores recipes, ingredients, meal plans, shopping lists, cookbooks, users, permissions, and metadata. Tandoor database memory is additional to the exported application minimum, so the approved tier increase applies.
AvaHost maps Tandoor to Plan 2 at €5. The one-click Tandoor stack includes PostgreSQL, which remains unmanaged by AvaHost. The Tandoor package provides automated HTTPS for a custom hostname, application updates, and scheduled backups. The first visitor creates the initial account. Application email is disabled, so invitations, notifications, and email recovery do not work; claim the setup page promptly and manage access inside Tandoor. Storage is the practical limit here: 50 GB on Plan 3 is a realistic starting point, while 100 GB on Plan 4 suits a large library.
F.A.Q
Tandoor starts at €5 on Plan 2 after allowing for PostgreSQL. Recipe count, images, imports, users, searches, meal plans, and shopping-list activity shape demand. Because food images and attachments accumulate, monitor storage even when the database remains modest and move to a larger plan as the collection grows.
The deployment creates PostgreSQL and connects Tandoor to it. Recipes, ingredients, meal plans, shopping lists, cookbooks, users, permissions, and metadata depend on the database. PostgreSQL is included but unmanaged, so application files, recipe images, secrets, and database records should be preserved and recovered together.
Tandoor is storage-driven because recipe images, imported assets, and attachments can outgrow the starting space. Plan 3 provides 50 GB as a practical next step for an established collection, while Plan 4 provides 100 GB for a large shared library. Review real image sizes and import habits rather than estimating from recipe count alone.
A household domain can point to Tandoor, with automated HTTPS applied after DNS resolves. Complete the first-account setup before sharing that address, because the first visitor can claim the installation. Application email is disabled, so invitations and mail recovery are unavailable; create accounts directly and keep the owner credential in a separate secure place.