Skip to content
DevUtils Online

Self-Hosted

new-api vs Stirling-PDF

Stirling-PDF leads by 1.4 · narrow

A

new-api

89.4

52,087 stars · AGPL-3.0

new-api 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. new-api is written mainly in Go; Stirling-PDF is written mainly in TypeScript. The composite score is 89.4 for new-api and 90.8 for Stirling-PDF.

Stirling-PDF has 96,832 GitHub stars to new-api's 52,087, a gap of 44,745 (1.86×). Forks are 12,719 for new-api and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 100 versus 97.

Push history: new-api 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 1,474 for new-api (0.028 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.

new-api 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 new-api and 30 for Stirling-PDF. This is a procurement signal, not legal advice.

In Self-Hosted, both new-api (52,087 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: new-api is open source, Stirling-PDF is unpriced in this catalog.

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

Stirling-PDF finishes ahead at 90.8 against new-api at 89.4, a 1.4 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.

new-api versus Stirling-PDF metrics
Signal new-api Stirling-PDF
GitHub stars 52,087 96,832
Forks 12,719 9,373
Open issues 1,474 448
Adoption 95 100
Activity 100 100
Community 100 97
Issue health 70 96
License 52 30
Self-hosting 100 100
Composite 89.4 90.8

new-api

Open-source AI gateway. Self-hosted LLM gateway with OpenAI-, Claude- and Gemini-compatible APIs, model routing, access control, usage tracking and cost accounting.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, new-api or Stirling-PDF?

Stirling-PDF has more GitHub stars: 96,832 versus 52,087 for new-api. The gap is 44,745 stars.

Which was updated more recently, new-api or Stirling-PDF?

Both were last pushed on 17 November 2026.

Can I self-host both new-api and Stirling-PDF?

Yes. This catalog marks both new-api 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, new-api or Stirling-PDF?

new-api 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 new-api vs Stirling-PDF score?

Stirling-PDF scores 90.8 and new-api scores 89.4. This page calls that a narrow lead for Stirling-PDF.

Related comparisons