A
docuseal
85.4
19,074 stars · AGPL-3.0
Self-Hosted
Stirling-PDF leads by 5.8 · narrow
A
85.4
19,074 stars · AGPL-3.0
B · leads
91.2
96,832 stars · license n/a
docuseal 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. docuseal is written mainly in Ruby; Stirling-PDF is written mainly in TypeScript. The composite score is 85.4 for docuseal and 91.2 for Stirling-PDF.
Stirling-PDF has 96,832 GitHub stars to docuseal's 19,074, a gap of 77,758 (5.08×). Forks are 1,960 for docuseal and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 83 versus 100.
Push history: docuseal was last pushed on 16 November 2026 (1 day ago), and Stirling-PDF was last pushed on 17 November 2026 (0 days ago). Open issues stand at 133 for docuseal (0.007 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
docuseal 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 docuseal and 30 for Stirling-PDF. This is a procurement signal, not legal advice.
In Self-Hosted, both docuseal (19,074 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: docuseal is open source, Stirling-PDF is unpriced in this catalog.
The lead is split. docuseal is furthest ahead on license flexibility (52 to 30), while Stirling-PDF is furthest ahead on fork community (100 to 83). Choose the dimension a rollout cannot compromise on.
Stirling-PDF finishes ahead at 91.2 against docuseal at 85.4, a 5.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 | docuseal | Stirling-PDF |
|---|---|---|
| GitHub stars | 19,074 | 96,832 |
| Forks | 1,960 | 9,373 |
| Open issues | 133 | 448 |
| Adoption | 86 | 100 |
| Activity | 100 | 100 |
| Community | 83 | 100 |
| Issue health | 84 | 96 |
| License | 52 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 85.4 | 91.2 |
Open source DocuSign alternative. Create, fill, and sign digital documents ✍️
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Stirling-PDF has more GitHub stars: 96,832 versus 19,074 for docuseal. The gap is 77,758 stars.
Stirling-PDF was pushed more recently: 17 November 2026 versus 16 November 2026 for docuseal. That is 1 days apart.
Yes. This catalog marks both docuseal and Stirling-PDF as self-hostable. Confirm each project's deploy docs before you plan a migration.
docuseal 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.
Stirling-PDF scores 91.2 and docuseal scores 85.4. This page calls that a narrow lead for Stirling-PDF.