mealie
Mealie is a self-hosted recipe manager and meal planner with REST API backend and Vue.js frontend. It allows users to import recipes from URLs, plan meals, generate shopping lists, and organize recipes into cookbooks.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | mealie-recipes/mealie |
| Owner | mealie-recipes |
| Primary language | Python |
| License | AGPL-3.0 — OSI-approved |
| Stars | 12.7k |
| Forks | 1.4k |
| Open issues | 212 |
| Latest release | v3.20.1 (2026-06-26) |
| Last updated | 2026-07-08 |
| Source | https://github.com/mealie-recipes/mealie |
What mealie is
Python-based self-hosted application with REST API backend and Vue.js reactive frontend. Supports Docker deployment, recipe scraping/import from URLs, meal planning, and shopping list generation with multi-language support (35+).
Get the mealie source
Clone the repository and explore it locally.
git clone https://github.com/mealie-recipes/mealie.gitcd mealie# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Docker deployment is primary distribution method; requires container orchestration knowledge and persistent volume management for recipe/user data.
- Database backend (type not specified in excerpt) must be provisioned separately; schema migrations between releases should be tested.
- Vue.js frontend and Python REST API are tightly coupled; frontend build and backend service deployment must be coordinated.
- URL-based recipe import depends on stable external website HTML/schema parsing; brittle to recipe site layout changes without active maintenance.
- AGPL-3.0 licensing requires source code distribution if modified and deployed; internal deployment strategy must account for compliance audit.
When to avoid it — and what to weigh
- Proprietary/Closed-Source Requirement — AGPL-3.0 licensing requires source code disclosure and derivative work compliance. Commercial deployment requires legal review.
- Minimal Self-Hosting Capability — Requires Docker and infrastructure management expertise. Not suitable for organizations seeking fully managed SaaS solutions.
- Large-Scale Multi-Tenant SaaS — AGPL-3.0 copyleft restrictions complicate commercial SaaS deployments. Designed for single-instance self-hosted use.
- Enterprise Integration Dependency — While REST API exists, no documented enterprise system integrations (ERP, LDAP, SSO) are described. Requires custom development.
License & commercial use
AGPL-3.0 (GNU Affero General Public License v3.0) applies. This is a strong copyleft license requiring disclosure of source code and licensing of derivative works under AGPL-3.0 when software is distributed or deployed as a network service.
AGPL-3.0 is not a standard permissive license (e.g., MIT, Apache 2.0). Commercial use is permitted, but modifications and network-deployed instances trigger source disclosure and copyleft obligations. Proprietary SaaS or closed-source derivatives are restricted. Internal business use (private deployment) may be defensible but requires legal review to confirm non-network-service use case. Requires explicit legal assessment before commercial adoption.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Self-hosted deployments require secure configuration: network isolation, encrypted database connections, authentication (mechanism not detailed), and HTTPS/TLS for frontend/API. URL-based recipe import functionality may pose risks if web scraper inadequately sandboxes HTML parsing. No security audit results, vulnerability disclosure policy, or authentication details provided in excerpt. Users are responsible for patching and infrastructure security in self-hosted model.
Alternatives to consider
Tandoor Recipes
Similar self-hosted recipe manager with Django backend; offers comparable feature set (import, meal planning, sharing). Alternative if permissive licensing (e.g., Apache 2.0) is required.
Grocerycrud or commercial SaaS (Paprika, Plan2Eat)
Proprietary or permissive-license alternatives if AGPL-3.0 compliance overhead is unacceptable or fully managed SaaS preferred.
Custom REST API + Database
If recipe and meal planning workflows are tightly integrated with existing enterprise systems, building a minimal custom solution may avoid licensing complexity.
Build on mealie with DEV.co software developers
Self-hosted recipe management with strong community support, but AGPL-3.0 licensing and deployment complexity require careful assessment. Review licensing obligations and infrastructure readiness before adoption. Consult our team on integration strategy and compliance concerns.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
mealie FAQ
Can we use Mealie for a commercial SaaS platform?
What database system does Mealie use?
Is there a managed hosting option?
How are recipe URLs parsed and imported?
Custom software development services
Adopting mealie is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source devops software in production.
Evaluate Mealie for Your Recipe & Meal Planning Needs
Self-hosted recipe management with strong community support, but AGPL-3.0 licensing and deployment complexity require careful assessment. Review licensing obligations and infrastructure readiness before adoption. Consult our team on integration strategy and compliance concerns.