A
gpt-researcher
94.7
30,757 stars · Apache-2.0
Workflow Automation
nanobot leads by 3.2 · narrow
A
94.7
30,757 stars · Apache-2.0
B · leads
97.9
50,147 stars · MIT
gpt-researcher versus nanobot is a Workflow Automation 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 94.7 for gpt-researcher and 97.9 for nanobot.
nanobot has 50,147 GitHub stars to gpt-researcher's 30,757, a gap of 19,390 (1.63×). Forks are 4,236 for gpt-researcher and 8,755 for nanobot. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 92 versus 100.
Push history: gpt-researcher was last pushed on 12 November 2026 (4 days ago), and nanobot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 56 for gpt-researcher (0.002 per star) and 872 for nanobot (0.017 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.
gpt-researcher is listed as Apache-2.0, 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. nanobot 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 96 for gpt-researcher and 96 for nanobot. This is a procurement signal, not legal advice.
In Workflow Automation, both gpt-researcher (30,757 stars) and nanobot (50,147 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: gpt-researcher is open source, nanobot is open source.
The lead is split. gpt-researcher is furthest ahead on issue health (96 to 84), while nanobot is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.
nanobot finishes ahead at 97.9 against gpt-researcher at 94.7, a 3.2 point narrow 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 | gpt-researcher | nanobot |
|---|---|---|
| GitHub stars | 30,757 | 50,147 |
| Forks | 4,236 | 8,755 |
| Open issues | 56 | 872 |
| Adoption | 96 | 100 |
| Activity | 92 | 100 |
| Community | 92 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 97.9 |
An autonomous agent that conducts deep research on any data using any LLM providers
Your lightweight open-source personal agent.
nanobot has more GitHub stars: 50,147 versus 30,757 for gpt-researcher. The gap is 19,390 stars.
nanobot was pushed more recently: 17 November 2026 versus 12 November 2026 for gpt-researcher. That is 4 days apart.
Yes. This catalog marks both gpt-researcher and nanobot as self-hostable. Confirm each project's deploy docs before you plan a migration.
gpt-researcher is listed as Apache-2.0, 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. nanobot 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.
nanobot scores 97.9 and gpt-researcher scores 94.7. This page calls that a narrow lead for nanobot.