Skip to content
DevUtils Online

Self-Hosted

llama-gpt vs uptime-kuma

uptime-kuma leads by 28.8 · decisive

llama-gpt versus uptime-kuma is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. llama-gpt is written mainly in TypeScript; uptime-kuma is written mainly in JavaScript. The composite score is 69.1 for llama-gpt and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to llama-gpt's 10,923, a gap of 83,615 (8.65×). Forks are 701 for llama-gpt and 8,860 for uptime-kuma. 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 uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 98 for llama-gpt (0.009 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 84 and 84; activity scores are 16 and 100.

Both llama-gpt and uptime-kuma are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Self-Hosted, both llama-gpt (10,923 stars) and uptime-kuma (94,538 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, uptime-kuma is open source.

uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is recent activity at 84 points (16 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).

uptime-kuma finishes ahead at 97.9 against llama-gpt at 69.1, a 28.8 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 uptime-kuma metrics
Signal llama-gpt uptime-kuma
GitHub stars 10,923 94,538
Forks 701 8,860
Open issues 98 852
Adoption 81 100
Activity 16 100
Community 72 100
Issue health 84 84
License 96 96
Self-hosting 100 100
Composite 69.1 97.9

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 uptime-kuma?

uptime-kuma has more GitHub stars: 94,538 versus 10,923 for llama-gpt. The gap is 83,615 stars.

Which was updated more recently, llama-gpt or uptime-kuma?

uptime-kuma 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 uptime-kuma?

Yes. This catalog marks both llama-gpt and uptime-kuma 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 uptime-kuma?

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. uptime-kuma 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the llama-gpt vs uptime-kuma score?

uptime-kuma scores 97.9 and llama-gpt scores 69.1. This page calls that a decisive lead for uptime-kuma.

Related comparisons