Skip to content
DevUtils Online

Self-Hosted

NocoDB vs rakazo

NocoDB leads by 4.1 · narrow

A · leads

NocoDB

92.6

65,557 stars · AGPL-3.0

B

rakazo

88.5

8,995 stars · Apache-2.0

NocoDB versus rakazo 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 88.5 for rakazo.

NocoDB has 65,557 GitHub stars to rakazo's 8,995, a gap of 56,562 (7.29×). Forks are 5,142 for NocoDB and 1,614 for rakazo. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 86.

Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and rakazo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 526 for NocoDB (0.008 per star) and 236 for rakazo (0.026 per star). Issue-health scores are 84 and 70; 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. rakazo 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 rakazo. This is a procurement signal, not legal advice.

In Self-Hosted, both NocoDB (65,557 stars) and rakazo (8,995 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, rakazo is open source.

The lead is split. NocoDB is furthest ahead on adoption (100 to 82), while rakazo is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.

NocoDB finishes ahead at 92.6 against rakazo at 88.5, a 4.1 point narrow 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.

NocoDB versus rakazo metrics
Signal NocoDB rakazo
GitHub stars 65,557 8,995
Forks 5,142 1,614
Open issues 526 236
Adoption 100 82
Activity 100 100
Community 100 86
Issue health 84 70
License 52 96
Self-hosting 100 100
Composite 92.6 88.5

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, NocoDB or rakazo?

NocoDB has more GitHub stars: 65,557 versus 8,995 for rakazo. The gap is 56,562 stars.

Which was updated more recently, NocoDB or rakazo?

Both were last pushed on 17 November 2026.

Can I self-host both NocoDB and rakazo?

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

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

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

Who wins the NocoDB vs rakazo score?

NocoDB scores 92.6 and rakazo scores 88.5. This page calls that a narrow lead for NocoDB.

Related comparisons