What Technology Stack and Project Resources Does Mealie Use?

Mealie is a self-hosted recipe manager whose documentation lists a defined technology stack plus separate resources for users, API consumers, and contributors. If you are deciding whether to deploy it yourself or build on top of it, the useful signals are the documented installation paths, the API reference, and the contributor and developer guides. The documentation does not publish a full dependency list or version numbers on the pages referenced here, so treat the stack as described at a category level rather than as a pinned specification.

What the documentation says about the technology stack

The documentation includes a dedicated "Technology stack" section alongside Installation, Feature overview, Import from other apps, and Project links. That grouping matters: the stack is presented as one of the project's identifying characteristics, not buried in a changelog.

The same documentation set also covers AI Providers as a configuration topic, which tells you the application is designed to integrate with external AI services rather than shipping a fixed built-in model. The specific providers are not enumerated in the material available here, so check the AI Providers page in the docs before assuming a particular vendor is supported.

Database options

Two database paths are documented:

If you want the lowest-friction self-hosted setup, SQLite is the documented default recommendation. PostgreSQL is the option to evaluate when you expect concurrent access, larger datasets, or you already run Postgres in your environment. The docs do not state migration tooling between the two here, so plan that as a separate question.

Installation and deployment resources

The Installation section is structured as a checklist rather than a single command, which is a reasonable indicator that deployment involves several decisions rather than one script. Documented installation-related topics include:

• Installation Checklist — the starting point for a new deployment
• Backend Configuration — server-side settings
• Security — hardening and access considerations
• Logs — where to look when something fails
• Updating — how to move between versions
• Version 1 Migration — a path for users coming from an older major version

Authentication is documented with LDAP and OpenID Connect support, which is the relevant detail if you need Mealie to sit behind an existing identity provider instead of managing its own accounts. There is also a Reverse Proxy (SWAG) community guide, useful if you are fronting the app with a proxy rather than exposing it directly.

Project links and developer resources

The documentation separates audiences clearly, which is a good sign for anyone evaluating long-term maintenance:

• API — an API reference exists, so programmatic access is a first-class concern rather than an afterthought.
• Contributors Guide — split into Non-Code (including Translating) and Developers Guide.
• Developers Guide — covers Building Packages, Code Contributions, Dev Getting Started, and Database Changes.
• Maintainers Guide and Migration Guide — governance and upgrade paths.
• Road Map — forward-looking plans.
• FAQ — common questions.

The presence of a translating workflow, a database-changes section, and a maintainers guide indicates an active multi-contributor project rather than a single-author script. For a self-hoster, that generally means upgrade instructions and issue triage are more likely to exist; for a developer, it means there is a documented path to submit changes rather than reverse-engineering the codebase.

Community guides worth knowing about

Beyond core documentation, the community guides cover practical integration and automation tasks:

• Bring API without internet exposure — relevant if you want API access on a network that is not publicly reachable
• Automating Backups with n8n — backup automation via an external workflow tool
• Bulk URL Import — importing many recipes at once
• Home Assistant Import — pulling recipes from a Home Assistant instance
• Bookmarklet and iOS Shortcut — capturing recipes from a browser or phone

These are user-contributed rather than core docs, so verify steps against your own version before relying on them.

How to use this to make a decision

If your goal is self-hosting a recipe manager, the documented SQLite-recommended path plus the installation checklist and reverse proxy guide give you a workable starting sequence; the LDAP/OpenID Connect support is the deciding factor if you need SSO.

If your goal is building on Mealie, the API reference and the developer guide sections on dev setup and database changes are your entry points, and the road map tells you where the project is heading.

If your goal is contributing, start with the contributors guide and pick the non-code or developer track depending on whether you are translating or writing code.

What the documentation does not give you here is a versioned dependency manifest, a support matrix, or a release cadence. Those are the gaps to close by checking the project links and the API reference directly before committing to a deployment or an integration.