A
mealie
86.1
13,930 stars · AGPL-3.0
Self-Hosted
NocoDB leads by 6.5 · narrow
A
86.1
13,930 stars · AGPL-3.0
B · leads
92.6
65,557 stars · AGPL-3.0
mealie versus NocoDB is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. mealie is written mainly in Python; NocoDB is written mainly in TypeScript. The composite score is 86.1 for mealie and 92.6 for NocoDB.
NocoDB has 65,557 GitHub stars to mealie's 13,930, a gap of 51,627 (4.71×). Forks are 1,689 for mealie and 5,142 for NocoDB. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 87 versus 100.
Push history: mealie was last pushed on 17 November 2026 (0 days ago), and NocoDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 114 for mealie (0.008 per star) and 526 for NocoDB (0.008 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both mealie and NocoDB are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Self-Hosted, both mealie (13,930 stars) and NocoDB (65,557 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: mealie is open source, NocoDB is freemium.
NocoDB is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is adoption at 14 points (86 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
NocoDB finishes ahead at 92.6 against mealie at 86.1, a 6.5 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | mealie | NocoDB |
|---|---|---|
| GitHub stars | 13,930 | 65,557 |
| Forks | 1,689 | 5,142 |
| Open issues | 114 | 526 |
| Adoption | 86 | 100 |
| Activity | 100 | 100 |
| Community | 87 | 100 |
| Issue health | 84 | 84 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 86.1 | 92.6 |
Mealie is a self hosted recipe manager and meal planner with a RestAPI backend and a reactive frontend application built in Vue for a pleasant user experience for the whole family. Easily add recipes into your database by providing the url and mealie will automatically import the relevant data or add a family recipe with the UI editor
NocoDB turns a relational database into a spreadsheet-style workspace with views, forms, and an API. It is used when the system of record should stay in Postgres or MySQL.
NocoDB has more GitHub stars: 65,557 versus 13,930 for mealie. The gap is 51,627 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both mealie and NocoDB as self-hostable. Confirm each project's deploy docs before you plan a migration.
mealie is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. NocoDB is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
NocoDB scores 92.6 and mealie scores 86.1. This page calls that a narrow lead for NocoDB.