Skip to content
DevUtils Online

Self-Hosted

NocoDB vs runtipi

NocoDB leads by 8.7 · clear

A · leads

NocoDB

92.6

65,557 stars · AGPL-3.0

B

runtipi

83.9

9,746 stars · GPL-3.0

NocoDB versus runtipi 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 83.9 for runtipi.

NocoDB has 65,557 GitHub stars to runtipi's 9,746, a gap of 55,811 (6.73×). Forks are 5,142 for NocoDB and 376 for runtipi. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 69.

Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and runtipi was last pushed on 17 November 2026 (0 days ago). Open issues stand at 526 for NocoDB (0.008 per star) and 78 for runtipi (0.008 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. runtipi is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 52 for NocoDB and 64 for runtipi. This is a procurement signal, not legal advice.

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

The lead is split. NocoDB is furthest ahead on fork community (100 to 69), while runtipi is furthest ahead on license flexibility (64 to 52). Choose the dimension a rollout cannot compromise on.

NocoDB finishes ahead at 92.6 against runtipi at 83.9, a 8.7 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.

NocoDB versus runtipi metrics
Signal NocoDB runtipi
GitHub stars 65,557 9,746
Forks 5,142 376
Open issues 526 78
Adoption 100 83
Activity 100 100
Community 100 69
Issue health 84 84
License 52 64
Self-hosting 100 100
Composite 92.6 83.9

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

runtipi

Runtipi is a homeserver for everyone! One command setup, one click installs for your favorites self-hosted apps. ✨

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, NocoDB or runtipi?

NocoDB has more GitHub stars: 65,557 versus 9,746 for runtipi. The gap is 55,811 stars.

Which was updated more recently, NocoDB or runtipi?

Both were last pushed on 17 November 2026.

Can I self-host both NocoDB and runtipi?

Yes. This catalog marks both NocoDB and runtipi 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 runtipi?

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. runtipi is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the NocoDB vs runtipi score?

NocoDB scores 92.6 and runtipi scores 83.9. This page calls that a clear lead for NocoDB.

Related comparisons