A · level
nanobot
94.4
50,147 stars · MIT
Workflow Automation
Too close to call · 94.4 to 94.7
A · level
94.4
50,147 stars · MIT
B · level
94.7
114,484 stars · MIT
nanobot versus paperclip 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; paperclip is written mainly in TypeScript. The composite score is 94.4 for nanobot and 94.7 for paperclip.
paperclip has 114,484 GitHub stars to nanobot's 50,147, a gap of 64,337 (2.28×). Forks are 8,755 for nanobot and 18,987 for paperclip. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 92 versus 100.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and paperclip was last pushed on 17 November 2026 (0 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 6,806 for paperclip (0.059 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
Both nanobot and paperclip 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 paperclip (114,484 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, paperclip is open source.
The lead is split. nanobot is furthest ahead on issue health (84 to 52), while paperclip is furthest ahead on fork community (100 to 92). Choose the dimension a rollout cannot compromise on.
Composite score: nanobot 94.4, paperclip 94.7. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | nanobot | paperclip |
|---|---|---|
| GitHub stars | 50,147 | 114,484 |
| Forks | 8,755 | 18,987 |
| Open issues | 872 | 6,806 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.4 | 94.7 |
Your lightweight open-source personal agent.
The open-source app everyone uses to manage agents at work
paperclip has more GitHub stars: 114,484 versus 50,147 for nanobot. The gap is 64,337 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobot and paperclip as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. paperclip 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.
Neither tool clears a one-point margin. nanobot scores 94.4 and paperclip scores 94.7.