OpenEats

OpenEats is a self-hosted recipe management site for creating, sharing, and storing personal recipe collections, designed for a single user or small group.

  • Other
  • Productivity
  • Tools & Utilities
OpenEats is a self-hosted recipe management site for creating, sharing, and storing personal recipe collections, designed for a single user or small group. Admin users manage accounts, cuisines, courses, and the homepage, while regular users add and share recipes.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

58/100 Fair

Maintained
68last commit 73 days ago
Popular
57696 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
60no serious findings, OpenSSF Scorecard 3.8/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 44 days ago

GitHub stars
696
Open issues
46
Last commit
2026-09-09
Latest release
1.5.1
License
MIT
Activity
stale

Checked 19 days ago - source: GitHub (open-eats/OpenEats)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • First-Run Database Initialisation OpenEats requires a MariaDB database instance. On first start the container creates all necessary SQL tables. This process takes roughly 5–10 minutes and produces no log output. Do not stop or restart the container during this period, as doing so will leave the database in a broken state. source

Fetched 45 days ago - each note links to its source

Alternatives (5)

  • Honeydew - AI-enhanced meal planner and digital cookbook, save recipes from social media, automatically generate grocery lists, and supports ingredien…
  • Mela
  • Paprika Recipe Manager - Organize your recipes.
  • Pestle - Pestle is an app that allows you to save and import recipes from anywhere online, keeping only the ingredients and steps.
  • Recipya - Recipya is a clean, self-hosted web app for managing family recipes, letting you add, organise, share and print them with cookbooks, nutrit…

Checked 51 days ago - source: AlternativeTo

Common questions

Are the released OpenEats containers easy to run on unRAID?

The released containers were reported as difficult to run on unRAID, which is why a separate unRAID Docker template was shared.

How can I self-host OpenEats without Docker?

Install it under /opt/openeats with a dedicated openeats user, install the dependencies as that user, and configure mod_wsgi to run as that user for the host.

What environment settings are needed before running OpenEats?

Create an environment file with DJANGO_SECRET_KEY, ALLOWED_HOST, and NODE_API_URL.

What first-time database setup is required?

You need to seed the database before using the app, then create a superuser by following the prompts.

Answers sourced from openeats.readthedocs.io, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads