Skip to content
DevUtils Online

Self-Hosted

khoj vs uptime-kuma

uptime-kuma leads by 17.9 · decisive

A

khoj

80.0

38,157 stars · AGPL-3.0

khoj 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. khoj is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 80.0 for khoj and 97.9 for uptime-kuma.

uptime-kuma has 94,538 GitHub stars to khoj's 38,157, a gap of 56,381 (2.48×). Forks are 2,555 for khoj and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 86 versus 100.

Push history: khoj was last pushed on 02 August 2026 (107 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 173 for khoj (0.005 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 96 and 84; activity scores are 58 and 100.

khoj 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. 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. License scores in this pair are 52 for khoj and 96 for uptime-kuma. This is a procurement signal, not legal advice.

In Self-Hosted, both khoj (38,157 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: khoj is open source, uptime-kuma is open source.

The lead is split. khoj is furthest ahead on issue health (96 to 84), while uptime-kuma is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.

uptime-kuma finishes ahead at 97.9 against khoj at 80.0, a 17.9 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.

khoj versus uptime-kuma metrics
Signal khoj uptime-kuma
GitHub stars 38,157 94,538
Forks 2,555 8,860
Open issues 173 852
Adoption 92 100
Activity 58 100
Community 86 100
Issue health 96 84
License 52 96
Self-hosting 100 100
Composite 80.0 97.9

khoj

Your AI second brain. Self-hostable. Get answers from the web or your docs. Build custom agents, schedule automations, do deep research. Turn any online or local LLM into your personal, autonomous AI (gpt, claude, gemini, llama, qwen, mistral). Get started - free.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, khoj or uptime-kuma?

uptime-kuma has more GitHub stars: 94,538 versus 38,157 for khoj. The gap is 56,381 stars.

Which was updated more recently, khoj or uptime-kuma?

uptime-kuma was pushed more recently: 17 November 2026 versus 02 August 2026 for khoj. That is 107 days apart.

Can I self-host both khoj and uptime-kuma?

Yes. This catalog marks both khoj 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, khoj or uptime-kuma?

khoj 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. 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 khoj vs uptime-kuma score?

uptime-kuma scores 97.9 and khoj scores 80.0. This page calls that a decisive lead for uptime-kuma.

Related comparisons