A · level
Stirling-PDF
91.2
96,832 stars · license n/a
Self-Hosted
Too close to call · 91.2 to 91.3
A · level
91.2
96,832 stars · license n/a
B · level
91.3
16,893 stars · Apache-2.0
Stirling-PDF versus SurfSense is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Stirling-PDF is written mainly in TypeScript; SurfSense is written mainly in Python. The composite score is 91.2 for Stirling-PDF and 91.3 for SurfSense.
Stirling-PDF has 96,832 GitHub stars to SurfSense's 16,893, a gap of 79,939 (5.73×). Forks are 9,373 for Stirling-PDF and 1,613 for SurfSense. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 81.
Push history: Stirling-PDF was last pushed on 17 November 2026 (0 days ago), and SurfSense was last pushed on 14 November 2026 (3 days ago). Open issues stand at 448 for Stirling-PDF (0.005 per star) and 64 for SurfSense (0.004 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
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. SurfSense 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. License scores in this pair are 30 for Stirling-PDF and 96 for SurfSense. This is a procurement signal, not legal advice.
In Self-Hosted, both Stirling-PDF (96,832 stars) and SurfSense (16,893 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: Stirling-PDF is unpriced in this catalog, SurfSense is open source.
The lead is split. Stirling-PDF is furthest ahead on fork community (100 to 81), while SurfSense is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
Composite score: Stirling-PDF 91.2, SurfSense 91.3. 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.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Stirling-PDF | SurfSense |
|---|---|---|
| GitHub stars | 96,832 | 16,893 |
| Forks | 9,373 | 1,613 |
| Open issues | 448 | 64 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 96 | 96 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.2 | 91.3 |
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Air-gapped, privacy-focused, open-source NotebookLM alternative. AI agent that researches, transforms, and edits your documents. Join our Discord: https://discord.gg/ejRNvftDp9
Stirling-PDF has more GitHub stars: 96,832 versus 16,893 for SurfSense. The gap is 79,939 stars.
Stirling-PDF was pushed more recently: 17 November 2026 versus 14 November 2026 for SurfSense. That is 3 days apart.
Yes. This catalog marks both Stirling-PDF and SurfSense as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. SurfSense 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. Stirling-PDF scores 91.2 and SurfSense scores 91.3.