A
docs
87.4
16,995 stars · MIT
Self-Hosted
Stirling-PDF leads by 3.8 · narrow
A
87.4
16,995 stars · MIT
B · leads
91.2
96,832 stars · license n/a
docs 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 87.4 for docs and 91.2 for Stirling-PDF.
Stirling-PDF has 96,832 GitHub stars to docs's 16,995, a gap of 79,837 (5.70×). Forks are 704 for docs and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 85 versus 100, and the fork community is 72 versus 100.
Push history: docs 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 351 for docs (0.021 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
docs is listed as MIT, 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 docs and 30 for Stirling-PDF. This is a procurement signal, not legal advice.
In Self-Hosted, both docs (16,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: docs is open source, Stirling-PDF is unpriced in this catalog.
The lead is split. docs is furthest ahead on license flexibility (96 to 30), while Stirling-PDF is furthest ahead on fork community (100 to 72). Choose the dimension a rollout cannot compromise on.
Stirling-PDF finishes ahead at 91.2 against docs at 87.4, a 3.8 point narrow margin under the published weights.
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 | docs | Stirling-PDF |
|---|---|---|
| GitHub stars | 16,995 | 96,832 |
| Forks | 704 | 9,373 |
| Open issues | 351 | 448 |
| Adoption | 85 | 100 |
| Activity | 100 | 100 |
| Community | 72 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 87.4 | 91.2 |
Docs is an open-source text editor: web-native, made for real-time collaboration, cleanly structured documents and sub-documents with full ownership of your data. Built to scale with Django and React.
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Stirling-PDF has more GitHub stars: 96,832 versus 16,995 for docs. The gap is 79,837 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both docs and Stirling-PDF as self-hostable. Confirm each project's deploy docs before you plan a migration.
docs is listed as MIT, 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.
Stirling-PDF scores 91.2 and docs scores 87.4. This page calls that a narrow lead for Stirling-PDF.