Skip to content
DevUtils Online

Self-Hosted

llama-gpt vs Stirling-PDF

Stirling-PDF leads by 22.2 · decisive

llama-gpt 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 69.0 for llama-gpt and 91.2 for Stirling-PDF.

Stirling-PDF has 96,832 GitHub stars to llama-gpt's 10,923, a gap of 85,909 (8.86×). Forks are 701 for llama-gpt and 9,373 for Stirling-PDF. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 72 versus 100.

Push history: llama-gpt was last pushed on 23 April 2024 (938 days ago), and Stirling-PDF was last pushed on 17 November 2026 (0 days ago). Open issues stand at 98 for llama-gpt (0.009 per star) and 448 for Stirling-PDF (0.005 per star). Issue-health scores are 84 and 96; activity scores are 16 and 100.

llama-gpt 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 llama-gpt and 30 for Stirling-PDF. This is a procurement signal, not legal advice.

In Self-Hosted, both llama-gpt (10,923 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: llama-gpt is open source, Stirling-PDF is unpriced in this catalog.

The lead is split. llama-gpt is furthest ahead on license flexibility (96 to 30), while Stirling-PDF is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.

Stirling-PDF finishes ahead at 91.2 against llama-gpt at 69.0, a 22.2 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

llama-gpt versus Stirling-PDF metrics
Signal llama-gpt Stirling-PDF
GitHub stars 10,923 96,832
Forks 701 9,373
Open issues 98 448
Adoption 81 100
Activity 16 100
Community 72 100
Issue health 84 96
License 96 30
Self-hosting 100 100
Composite 69.0 91.2

llama-gpt

A self-hosted, offline, ChatGPT-like chatbot. Powered by Llama 2. 100% private, with no data leaving your device. New: Code Llama support!

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, llama-gpt or Stirling-PDF?

Stirling-PDF has more GitHub stars: 96,832 versus 10,923 for llama-gpt. The gap is 85,909 stars.

Which was updated more recently, llama-gpt or Stirling-PDF?

Stirling-PDF was pushed more recently: 17 November 2026 versus 23 April 2024 for llama-gpt. That is 938 days apart.

Can I self-host both llama-gpt and Stirling-PDF?

Yes. This catalog marks both llama-gpt and Stirling-PDF as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, llama-gpt or Stirling-PDF?

llama-gpt 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.

Who wins the llama-gpt vs Stirling-PDF score?

Stirling-PDF scores 91.2 and llama-gpt scores 69.0. This page calls that a decisive lead for Stirling-PDF.

Related comparisons