A · leads
NocoDB
92.6
65,557 stars · AGPL-3.0
Self-Hosted
NocoDB leads by 6.2 · narrow
A · leads
92.6
65,557 stars · AGPL-3.0
B
86.4
15,125 stars · AGPL-3.0
NocoDB versus peach is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. NocoDB is written mainly in TypeScript; peach is written mainly in Python. The composite score is 92.6 for NocoDB and 86.4 for peach.
NocoDB has 65,557 GitHub stars to peach's 15,125, a gap of 50,432 (4.33×). Forks are 5,142 for NocoDB and 1,781 for peach. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 88.
Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and peach was last pushed on 17 November 2026 (0 days ago). Open issues stand at 526 for NocoDB (0.008 per star) and 183 for peach (0.012 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both NocoDB and peach 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 NocoDB (65,557 stars) and peach (15,125 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: NocoDB is freemium, peach is open source.
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 13 points (100 vs 87), and the tightest is self-hosting at 0 points (100 vs 100).
NocoDB finishes ahead at 92.6 against peach at 86.4, a 6.2 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 | NocoDB | peach |
|---|---|---|
| GitHub stars | 65,557 | 15,125 |
| Forks | 5,142 | 1,781 |
| Open issues | 526 | 183 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 84 | 84 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 86.4 |
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.
Peach: Local-first video metadata scraper and media manager.
NocoDB has more GitHub stars: 65,557 versus 15,125 for peach. The gap is 50,432 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both NocoDB and peach as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. peach 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 peach scores 86.4. This page calls that a narrow lead for NocoDB.