A · level
neko
92.8
22,688 stars · Apache-2.0
Self-Hosted
Too close to call · 92.8 to 92.6
A · level
92.8
22,688 stars · Apache-2.0
B · level
92.6
65,557 stars · AGPL-3.0
neko versus NocoDB is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. neko is written mainly in Go; NocoDB is written mainly in TypeScript. The composite score is 92.8 for neko and 92.6 for NocoDB.
NocoDB has 65,557 GitHub stars to neko's 22,688, a gap of 42,869 (2.89×). Forks are 1,662 for neko and 5,142 for NocoDB. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 87 versus 100.
Push history: neko was last pushed on 16 November 2026 (1 day ago), and NocoDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 144 for neko (0.006 per star) and 526 for NocoDB (0.008 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
neko 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. 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. License scores in this pair are 96 for neko and 52 for NocoDB. This is a procurement signal, not legal advice.
In Self-Hosted, both neko (22,688 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: neko is open source, NocoDB is freemium.
The lead is split. neko is furthest ahead on license flexibility (96 to 52), while NocoDB is furthest ahead on fork community (100 to 87). Choose the dimension a rollout cannot compromise on.
Composite score: neko 92.8, NocoDB 92.6. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | neko | NocoDB |
|---|---|---|
| GitHub stars | 22,688 | 65,557 |
| Forks | 1,662 | 5,142 |
| Open issues | 144 | 526 |
| Adoption | 90 | 100 |
| Activity | 100 | 100 |
| Community | 87 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.8 | 92.6 |
A self hosted virtual browser that runs in docker and uses WebRTC.
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 22,688 for neko. The gap is 42,869 stars.
NocoDB was pushed more recently: 17 November 2026 versus 16 November 2026 for neko. That is 1 days apart.
Yes. This catalog marks both neko and NocoDB as self-hostable. Confirm each project's deploy docs before you plan a migration.
neko 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. 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.
Neither tool clears a one-point margin. neko scores 92.8 and NocoDB scores 92.6.