Skip to content
DevUtils Online

Self-Hosted

rakazo vs Stirling-PDF

Stirling-PDF leads by 4.4 · narrow

A

rakazo

86.8

8,995 stars · Apache-2.0

rakazo 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 86.8 for rakazo and 91.2 for Stirling-PDF.

Stirling-PDF has 96,832 GitHub stars to rakazo's 8,995, a gap of 87,837 (10.77×). Forks are 1,614 for rakazo and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 79 versus 100, and the fork community is 81 versus 100.

Push history: rakazo 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 236 for rakazo (0.026 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.

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

In Self-Hosted, both rakazo (8,995 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: rakazo is open source, Stirling-PDF is unpriced in this catalog.

The lead is split. rakazo is furthest ahead on license flexibility (96 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 91.2 against rakazo at 86.8, a 4.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.

rakazo versus Stirling-PDF metrics
Signal rakazo Stirling-PDF
GitHub stars 8,995 96,832
Forks 1,614 9,373
Open issues 236 448
Adoption 79 100
Activity 100 100
Community 81 100
Issue health 70 96
License 96 30
Self-hosting 100 100
Composite 86.8 91.2

Questions this page answers

Which has more GitHub stars, rakazo or Stirling-PDF?

Stirling-PDF has more GitHub stars: 96,832 versus 8,995 for rakazo. The gap is 87,837 stars.

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

Both were last pushed on 17 November 2026.

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

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

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. 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 rakazo vs Stirling-PDF score?

Stirling-PDF scores 91.2 and rakazo scores 86.8. This page calls that a narrow lead for Stirling-PDF.

Related comparisons