A · leads
Appwrite
95.7
58,177 stars · BSD-3-Clause
Self-Hosted
Appwrite leads by 4.5 · narrow
A · leads
95.7
58,177 stars · BSD-3-Clause
B
91.2
96,832 stars · license n/a
Appwrite 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 95.7 for Appwrite and 91.2 for Stirling-PDF.
Stirling-PDF has 96,832 GitHub stars to Appwrite's 58,177, a gap of 38,655 (1.66×). Forks are 5,897 for Appwrite and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 95 versus 100.
Push history: Appwrite 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 744 for Appwrite (0.013 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Appwrite is listed as BSD-3-Clause, 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 Appwrite and 30 for Stirling-PDF. This is a procurement signal, not legal advice.
In Self-Hosted, both Appwrite (58,177 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: Appwrite is freemium, Stirling-PDF is unpriced in this catalog.
The lead is split. Appwrite is furthest ahead on license flexibility (96 to 30), while Stirling-PDF is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
Appwrite finishes ahead at 95.7 against Stirling-PDF at 91.2, a 4.5 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 | Appwrite | Stirling-PDF |
|---|---|---|
| GitHub stars | 58,177 | 96,832 |
| Forks | 5,897 | 9,373 |
| Open issues | 744 | 448 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 95 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 95.7 | 91.2 |
Appwrite is a backend server for auth, databases, storage, and functions. It is built for product teams that want a self-hosted alternative to a proprietary backend-as-a-service.
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Stirling-PDF has more GitHub stars: 96,832 versus 58,177 for Appwrite. The gap is 38,655 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Appwrite and Stirling-PDF as self-hostable. Confirm each project's deploy docs before you plan a migration.
Appwrite is listed as BSD-3-Clause, 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.
Appwrite scores 95.7 and Stirling-PDF scores 91.2. This page calls that a narrow lead for Appwrite.