A
local-deep-research
82.6
9,596 stars · MIT
Self-Hosted
uptime-kuma leads by 15.3 · decisive
A
82.6
9,596 stars · MIT
B · leads
97.9
94,538 stars · MIT
local-deep-research 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. local-deep-research is written mainly in Python; uptime-kuma is written mainly in JavaScript. The composite score is 82.6 for local-deep-research and 97.9 for uptime-kuma.
uptime-kuma has 94,538 GitHub stars to local-deep-research's 9,596, a gap of 84,942 (9.85×). Forks are 929 for local-deep-research and 8,860 for uptime-kuma. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 75 versus 100.
Push history: local-deep-research was last pushed on 17 November 2026 (0 days ago), and uptime-kuma was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,481 for local-deep-research (0.154 per star) and 852 for uptime-kuma (0.009 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
Both local-deep-research 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 local-deep-research (9,596 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: local-deep-research is open source, uptime-kuma is open source.
uptime-kuma is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 50 points (34 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
uptime-kuma finishes ahead at 97.9 against local-deep-research at 82.6, a 15.3 point decisive 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 | local-deep-research | uptime-kuma |
|---|---|---|
| GitHub stars | 9,596 | 94,538 |
| Forks | 929 | 8,860 |
| Open issues | 1,481 | 852 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 75 | 100 |
| Issue health | 34 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.6 | 97.9 |
~95% on SimpleQA (e.g. Qwen3.6-27B on a 3090). Supports all local and cloud LLMs (llama.cpp, Ollama, Google, ...). 10+ search engines - arXiv, PubMed, your private documents. Everything Local & Encrypted.
A fancy self-hosted monitoring tool
uptime-kuma has more GitHub stars: 94,538 versus 9,596 for local-deep-research. The gap is 84,942 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both local-deep-research and uptime-kuma as self-hostable. Confirm each project's deploy docs before you plan a migration.
local-deep-research 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.
uptime-kuma scores 97.9 and local-deep-research scores 82.6. This page calls that a decisive lead for uptime-kuma.