A
nightingale
89.6
13,497 stars · Apache-2.0
Self-Hosted
Stirling-PDF leads by 1.6 · narrow
A
89.6
13,497 stars · Apache-2.0
B · leads
91.2
96,832 stars · license n/a
nightingale 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. nightingale is written mainly in Go; Stirling-PDF is written mainly in TypeScript. The composite score is 89.6 for nightingale and 91.2 for Stirling-PDF.
Stirling-PDF has 96,832 GitHub stars to nightingale's 13,497, a gap of 83,335 (7.17×). Forks are 1,801 for nightingale and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 82 versus 100.
Push history: nightingale 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 243 for nightingale (0.018 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
nightingale 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 nightingale and 30 for Stirling-PDF. This is a procurement signal, not legal advice.
In Self-Hosted, both nightingale (13,497 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: nightingale is open source, Stirling-PDF is unpriced in this catalog.
The lead is split. nightingale is furthest ahead on license flexibility (96 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 nightingale at 89.6, a 1.6 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 | nightingale | Stirling-PDF |
|---|---|---|
| GitHub stars | 13,497 | 96,832 |
| Forks | 1,801 | 9,373 |
| Open issues | 243 | 448 |
| Adoption | 83 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 89.6 | 91.2 |
Open-source, self-hosted alerting for metrics, logs, and databases. Includes a built-in AI agent and MCP server.
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Stirling-PDF has more GitHub stars: 96,832 versus 13,497 for nightingale. The gap is 83,335 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nightingale and Stirling-PDF as self-hostable. Confirm each project's deploy docs before you plan a migration.
nightingale 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.
Stirling-PDF scores 91.2 and nightingale scores 89.6. This page calls that a narrow lead for Stirling-PDF.