Skip to content
DevUtils Online

Workflow Automation

nanobot vs open-claude-cowork

nanobot leads by 24.5 · decisive

A · leads

nanobot

97.9

50,147 stars · MIT

nanobot versus open-claude-cowork is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. nanobot is written mainly in Python; open-claude-cowork is written mainly in JavaScript. The composite score is 97.9 for nanobot and 73.4 for open-claude-cowork.

nanobot has 50,147 GitHub stars to open-claude-cowork's 4,319, a gap of 45,828 (11.61×). Forks are 8,755 for nanobot and 701 for open-claude-cowork. On the log scale used inside this pair, adoption is 100 versus 77, and the fork community is 100 versus 72.

Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and open-claude-cowork was last pushed on 23 May 2026 (178 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 16 for open-claude-cowork (0.004 per star). Issue-health scores are 84 and 96; activity scores are 100 and 36.

Both nanobot and open-claude-cowork 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 Workflow Automation, both nanobot (50,147 stars) and open-claude-cowork (4,319 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: nanobot is open source, open-claude-cowork is open source.

The lead is split. nanobot is furthest ahead on recent activity (100 to 36), while open-claude-cowork is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.

nanobot finishes ahead at 97.9 against open-claude-cowork at 73.4, a 24.5 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.

nanobot versus open-claude-cowork metrics
Signal nanobot open-claude-cowork
GitHub stars 50,147 4,319
Forks 8,755 701
Open issues 872 16
Adoption 100 77
Activity 100 36
Community 100 72
Issue health 84 96
License 96 96
Self-hosting 100 100
Composite 97.9 73.4

Questions this page answers

Which has more GitHub stars, nanobot or open-claude-cowork?

nanobot has more GitHub stars: 50,147 versus 4,319 for open-claude-cowork. The gap is 45,828 stars.

Which was updated more recently, nanobot or open-claude-cowork?

nanobot was pushed more recently: 17 November 2026 versus 23 May 2026 for open-claude-cowork. That is 178 days apart.

Can I self-host both nanobot and open-claude-cowork?

Yes. This catalog marks both nanobot and open-claude-cowork as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, nanobot or open-claude-cowork?

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. open-claude-cowork 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 nanobot vs open-claude-cowork score?

nanobot scores 97.9 and open-claude-cowork scores 73.4. This page calls that a decisive lead for nanobot.

Related comparisons