A · leads
NocoDB
92.6
65,557 stars · AGPL-3.0
Self-Hosted
NocoDB leads by 7.6 · clear
A · leads
92.6
65,557 stars · AGPL-3.0
B
85.0
14,400 stars · AGPL-3.0
NocoDB versus romm 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; romm is written mainly in Python. The composite score is 92.6 for NocoDB and 85.0 for romm.
NocoDB has 65,557 GitHub stars to romm's 14,400, a gap of 51,157 (4.55×). Forks are 5,142 for NocoDB and 822 for romm. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 79.
Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and romm was last pushed on 17 November 2026 (0 days ago). Open issues stand at 526 for NocoDB (0.008 per star) and 214 for romm (0.015 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both NocoDB and romm 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 romm (14,400 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, romm 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 fork community at 21 points (100 vs 79), and the tightest is self-hosting at 0 points (100 vs 100).
NocoDB finishes ahead at 92.6 against romm at 85.0, a 7.6 point clear 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 | romm |
|---|---|---|
| GitHub stars | 65,557 | 14,400 |
| Forks | 5,142 | 822 |
| Open issues | 526 | 214 |
| Adoption | 100 | 86 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 84 | 84 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 85.0 |
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.
A beautiful, powerful, self-hosted ROM manager and player.
NocoDB has more GitHub stars: 65,557 versus 14,400 for romm. The gap is 51,157 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both NocoDB and romm 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. romm 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 romm scores 85.0. This page calls that a clear lead for NocoDB.