Skip to content
DevUtils Online

Self-Hosted

core vs NocoDB

NocoDB leads by 7.6 · clear

A

core

85.0

8,853 stars · AGPL-3.0

B · leads

NocoDB

92.6

65,557 stars · AGPL-3.0

core versus NocoDB is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. core is written mainly in PHP; NocoDB is written mainly in TypeScript. The composite score is 85.0 for core and 92.6 for NocoDB.

NocoDB has 65,557 GitHub stars to core's 8,853, a gap of 56,704 (7.41×). Forks are 2,061 for core and 5,142 for NocoDB. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 89 versus 100.

Push history: core 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 146 for core (0.016 per star) and 526 for NocoDB (0.008 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Both core and NocoDB 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 core (8,853 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: core is open source, NocoDB is freemium.

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 18 points (82 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

NocoDB finishes ahead at 92.6 against core at 85.0, a 7.6 point clear margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

core versus NocoDB metrics
Signal core NocoDB
GitHub stars 8,853 65,557
Forks 2,061 5,142
Open issues 146 526
Adoption 82 100
Activity 100 100
Community 89 100
Issue health 84 84
License 52 52
Self-hosting 100 100
Composite 85.0 92.6

NocoDB

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, core or NocoDB?

NocoDB has more GitHub stars: 65,557 versus 8,853 for core. The gap is 56,704 stars.

Which was updated more recently, core or NocoDB?

NocoDB was pushed more recently: 17 November 2026 versus 16 November 2026 for core. That is 1 days apart.

Can I self-host both core and NocoDB?

Yes. This catalog marks both core and NocoDB as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, core or NocoDB?

core 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. 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.

Who wins the core vs NocoDB score?

NocoDB scores 92.6 and core scores 85.0. This page calls that a clear lead for NocoDB.

Related comparisons