A
local-deep-research
86.3
9,596 stars · MIT
Self-Hosted
serviette leads by 11.1 · clear
A
86.3
9,596 stars · MIT
B · leads
97.4
58,707 stars · MIT
local-deep-research versus serviette 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 Python. The composite score is 86.3 for local-deep-research and 97.4 for serviette.
serviette has 58,707 GitHub stars to local-deep-research's 9,596, a gap of 49,111 (6.12×). Forks are 929 for local-deep-research and 1,551 for serviette. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 93 versus 100.
Push history: local-deep-research was last pushed on 17 November 2026 (0 days ago), and serviette was last pushed on 10 November 2026 (7 days ago). Open issues stand at 1,481 for local-deep-research (0.154 per star) and 6 for serviette (0.000 per star). Issue-health scores are 34 and 96; activity scores are 100 and 92.
Both local-deep-research and serviette 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 serviette (58,707 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, serviette is open source.
The lead is split. local-deep-research is furthest ahead on recent activity (100 to 92), while serviette is furthest ahead on issue health (96 to 34). Choose the dimension a rollout cannot compromise on.
serviette finishes ahead at 97.4 against local-deep-research at 86.3, a 11.1 point clear 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 | serviette |
|---|---|---|
| GitHub stars | 9,596 | 58,707 |
| Forks | 929 | 1,551 |
| Open issues | 1,481 | 6 |
| Adoption | 84 | 100 |
| Activity | 100 | 92 |
| Community | 93 | 100 |
| Issue health | 34 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.3 | 97.4 |
~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 no-code RAG server that keeps answers in sync with your documents. Works with 8 vector databases. Built on Pathway.
serviette has more GitHub stars: 58,707 versus 9,596 for local-deep-research. The gap is 49,111 stars.
local-deep-research was pushed more recently: 17 November 2026 versus 10 November 2026 for serviette. That is 7 days apart.
Yes. This catalog marks both local-deep-research and serviette 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. serviette 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.
serviette scores 97.4 and local-deep-research scores 86.3. This page calls that a clear lead for serviette.