Mealie Hosting

How Mealie works

Mealie stores recipes with ingredients, instructions, categories, tags, nutrition fields, images, and source links. Users can create recipes manually or import from supported web pages, then add meals to a calendar and generate shopping-list entries. Groups and households separate membership and shared data inside the installation.

Web imports depend on the structure and accessibility of the source page. A site can block requests, change its markup, omit quantities, or present ambiguous ingredient text. Imported recipes need review before cooking, and ingredient parsing is not a food-safety, allergy, nutrition, or medical verification service.

Key Mealie features

Meal plans connect the recipe library with upcoming cooking, while shopping lists help consolidate ingredients and household additions. The API and supported integrations can extend workflows when the customer supplies permitted clients and credentials. Shared editing is useful, but administrators should set household membership deliberately because recipes and lists may contain private preferences or health-related notes.

The catalogue uses Mealie’s fixed upstream first-run credentials changeme@example.com / MyPassword; they must be changed immediately. SMTP variables are blank and platform application email is disabled, so invitation, reset, and notification mail cannot be sent. External recipe sources, mobile wrappers, nutrition databases, grocery delivery, and barcode services are not bundled.

Mealie vs Paprika

Mealie runs as a shared browser application with local account, household, recipe, meal-plan, and shopping-list administration. Paprika sells native recipe-management applications for supported platforms and uses its cloud synchronisation service to keep recipes, grocery lists, and meal plans available across purchased devices.

Paprika may suit individuals who want polished native apps, provider-managed synchronisation, and less server administration. Mealie fits households that prefer a shared self-hosted web service, need API access and multi-user organisation, and accept responsibility for credentials, updates, source imports, and browser-based access.

Who uses Mealie

Families organise favourite recipes and weekly meals, housemates collaborate on shopping lists, and cooking groups maintain a shared collection with tags and categories. Individuals also use Mealie to replace scattered bookmarks and documents with searchable recipes and a repeatable planning process.

Mealie is not a dietitian, allergy checker, grocery retailer, food-safety authority, or guarantee that imported instructions are complete. Users must verify ingredients, cooking temperatures, dietary suitability, and source rights themselves.

Self-hosting Mealie: requirements and cost

Mealie demand grows with recipes, users, households, images, imports, shopping lists, meal plans, API traffic, and search activity. The catalogue records PostgreSQL and MariaDB as Not required and persists /app/data. Images and a large recipe collection generally increase storage faster than ordinary editing increases processor demand.

On AvaHost, Mealie uses Plan 1 at €2. The hosted Mealie package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. Replace the fixed changeme@example.com / MyPassword credentials before inviting anyone. Application email is disabled, so reset, invitation, and notification messages cannot send. Recipe websites, nutrition services, mobile clients, grocery delivery, barcode tools, and food-safety verification are not included. Review imported recipes and maintain independent exports of valued content.