Skip to content
DevUtils Online

Self-Hosted

peach vs Stirling-PDF

Stirling-PDF leads by 6.6 · narrow

A

peach

84.6

15,125 stars · AGPL-3.0

peach 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. peach is written mainly in Python; Stirling-PDF is written mainly in TypeScript. The composite score is 84.6 for peach and 91.2 for Stirling-PDF.

Stirling-PDF has 96,832 GitHub stars to peach's 15,125, a gap of 81,707 (6.40×). Forks are 1,781 for peach and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 82 versus 100.

Push history: peach 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 183 for peach (0.012 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.

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

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

The lead is split. peach is furthest ahead on license flexibility (52 to 30), while Stirling-PDF is furthest ahead on fork community (100 to 82). Choose the dimension a rollout cannot compromise on.

Stirling-PDF finishes ahead at 91.2 against peach at 84.6, a 6.6 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.

peach versus Stirling-PDF metrics
Signal peach Stirling-PDF
GitHub stars 15,125 96,832
Forks 1,781 9,373
Open issues 183 448
Adoption 84 100
Activity 100 100
Community 82 100
Issue health 84 96
License 52 30
Self-hosting 100 100
Composite 84.6 91.2

Questions this page answers

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

Stirling-PDF has more GitHub stars: 96,832 versus 15,125 for peach. The gap is 81,707 stars.

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

Both were last pushed on 17 November 2026.

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

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

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

Stirling-PDF scores 91.2 and peach scores 84.6. This page calls that a narrow lead for Stirling-PDF.

Related comparisons