A
local-deep-research
84.2
9,596 stars · MIT
Self-Hosted
NocoDB leads by 8.4 · clear
A
84.2
9,596 stars · MIT
B · leads
92.6
65,557 stars · AGPL-3.0
local-deep-research versus NocoDB 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; NocoDB is written mainly in TypeScript. The composite score is 84.2 for local-deep-research and 92.6 for NocoDB.
NocoDB has 65,557 GitHub stars to local-deep-research's 9,596, a gap of 55,961 (6.83×). Forks are 929 for local-deep-research and 5,142 for NocoDB. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 80 versus 100.
Push history: local-deep-research was last pushed on 17 November 2026 (0 days ago), and NocoDB 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 526 for NocoDB (0.008 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
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. NocoDB 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. License scores in this pair are 96 for local-deep-research and 52 for NocoDB. This is a procurement signal, not legal advice.
In Self-Hosted, both local-deep-research (9,596 stars) and NocoDB (65,557 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, NocoDB is freemium.
The lead is split. local-deep-research is furthest ahead on license flexibility (96 to 52), while NocoDB is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
NocoDB finishes ahead at 92.6 against local-deep-research at 84.2, a 8.4 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 | NocoDB |
|---|---|---|
| GitHub stars | 9,596 | 65,557 |
| Forks | 929 | 5,142 |
| Open issues | 1,481 | 526 |
| Adoption | 83 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 34 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 84.2 | 92.6 |
~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.
NocoDB turns a relational database into a spreadsheet-style workspace with views, forms, and an API. It is used when the system of record should stay in Postgres or MySQL.
NocoDB has more GitHub stars: 65,557 versus 9,596 for local-deep-research. The gap is 55,961 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both local-deep-research and NocoDB 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. NocoDB 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
NocoDB scores 92.6 and local-deep-research scores 84.2. This page calls that a clear lead for NocoDB.