Skip to content
DevUtils Online

Self-Hosted

NocoDB vs Stirling-PDF

Too close to call · 90.6 to 91.2

A · level

NocoDB

90.6

65,557 stars · AGPL-3.0

NocoDB versus Stirling-PDF 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 90.6 for NocoDB and 91.2 for Stirling-PDF.

Stirling-PDF has 96,832 GitHub stars to NocoDB's 65,557, a gap of 31,275 (1.48×). Forks are 5,142 for NocoDB and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 93 versus 100.

Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and Stirling-PDF was last pushed on 17 November 2026 (0 days ago). Open issues stand at 526 for NocoDB (0.008 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 84 and 96; 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. Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 52 for NocoDB and 30 for Stirling-PDF. This is a procurement signal, not legal advice.

In Self-Hosted, both NocoDB (65,557 stars) and Stirling-PDF (96,832 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, Stirling-PDF is unpriced in this catalog.

The lead is split. NocoDB is furthest ahead on license flexibility (52 to 30), while Stirling-PDF is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.

Composite score: NocoDB 90.6, Stirling-PDF 91.2. 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.

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 Stirling-PDF metrics
Signal NocoDB Stirling-PDF
GitHub stars 65,557 96,832
Forks 5,142 9,373
Open issues 526 448
Adoption 97 100
Activity 100 100
Community 93 100
Issue health 84 96
License 52 30
Self-hosting 100 100
Composite 90.6 91.2

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 Stirling-PDF?

Stirling-PDF has more GitHub stars: 96,832 versus 65,557 for NocoDB. The gap is 31,275 stars.

Which was updated more recently, NocoDB or Stirling-PDF?

Both were last pushed on 17 November 2026.

Can I self-host both NocoDB and Stirling-PDF?

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

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. Stirling-PDF is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the NocoDB vs Stirling-PDF score?

Neither tool clears a one-point margin. NocoDB scores 90.6 and Stirling-PDF scores 91.2.

Related comparisons