A · leads
NocoDB
92.6
65,557 stars · AGPL-3.0
Self-Hosted
NocoDB leads by 1.2 · narrow
A · leads
92.6
65,557 stars · AGPL-3.0
B
91.4
15,349 stars · Apache-2.0
NocoDB versus openship is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 92.6 for NocoDB and 91.4 for openship.
NocoDB has 65,557 GitHub stars to openship's 15,349, a gap of 50,208 (4.27×). Forks are 5,142 for NocoDB and 1,415 for openship. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 85.
Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and openship was last pushed on 17 November 2026 (0 days ago). Open issues stand at 526 for NocoDB (0.008 per star) and 177 for openship (0.012 per star). Issue-health scores are 84 and 84; 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. openship is listed as Apache-2.0, 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 openship. This is a procurement signal, not legal advice.
In Self-Hosted, both NocoDB (65,557 stars) and openship (15,349 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, openship is open source.
The lead is split. NocoDB is furthest ahead on fork community (100 to 85), while openship is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
NocoDB finishes ahead at 92.6 against openship at 91.4, a 1.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 | openship |
|---|---|---|
| GitHub stars | 65,557 | 15,349 |
| Forks | 5,142 | 1,415 |
| Open issues | 526 | 177 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 84 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 91.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.
Self-hosted deployment platform
NocoDB has more GitHub stars: 65,557 versus 15,349 for openship. The gap is 50,208 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both NocoDB and openship 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. openship is listed as Apache-2.0, 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.
NocoDB scores 92.6 and openship scores 91.4. This page calls that a narrow lead for NocoDB.