A
NocoDB
92.5
65,557 stars · AGPL-3.0
Self-Hosted
pentagi leads by 4.6 · narrow
A
92.5
65,557 stars · AGPL-3.0
B · leads
97.1
34,396 stars · MIT
NocoDB versus pentagi 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; pentagi is written mainly in Go. The composite score is 92.5 for NocoDB and 97.1 for pentagi.
NocoDB has 65,557 GitHub stars to pentagi's 34,396, a gap of 31,161 (1.91×). Forks are 5,142 for NocoDB and 5,447 for pentagi. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 99 versus 100.
Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and pentagi was last pushed on 13 November 2026 (3 days ago). Open issues stand at 526 for NocoDB (0.008 per star) and 76 for pentagi (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
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. pentagi is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 52 for NocoDB and 96 for pentagi. This is a procurement signal, not legal advice.
In Self-Hosted, both NocoDB (65,557 stars) and pentagi (34,396 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, pentagi is open source.
The lead is split. NocoDB is furthest ahead on adoption (100 to 94), while pentagi is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
pentagi finishes ahead at 97.1 against NocoDB at 92.5, a 4.6 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 | pentagi |
|---|---|---|
| GitHub stars | 65,557 | 34,396 |
| Forks | 5,142 | 5,447 |
| Open issues | 526 | 76 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 99 | 100 |
| Issue health | 84 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.5 | 97.1 |
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.
Fully autonomous AI Agents system capable of performing complex penetration testing tasks
NocoDB has more GitHub stars: 65,557 versus 34,396 for pentagi. The gap is 31,161 stars.
NocoDB was pushed more recently: 17 November 2026 versus 13 November 2026 for pentagi. That is 3 days apart.
Yes. This catalog marks both NocoDB and pentagi 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. pentagi is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
pentagi scores 97.1 and NocoDB scores 92.5. This page calls that a narrow lead for pentagi.