A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 2.8 · narrow
A · leads
97.9
50,147 stars · MIT
B
95.1
30,151 stars · Apache-2.0
nanobot versus sim 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; sim is written mainly in TypeScript. The composite score is 97.9 for nanobot and 95.1 for sim.
nanobot has 50,147 GitHub stars to sim's 30,151, a gap of 19,996 (1.66×). Forks are 8,755 for nanobot and 3,915 for sim. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 91.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and sim was last pushed on 17 November 2026 (0 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 330 for sim (0.011 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. sim 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. License scores in this pair are 96 for nanobot and 96 for sim. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 stars) and sim (30,151 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, sim is open source.
nanobot is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 9 points (100 vs 91), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against sim at 95.1, a 2.8 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 | nanobot | sim |
|---|---|---|
| GitHub stars | 50,147 | 30,151 |
| Forks | 8,755 | 3,915 |
| Open issues | 872 | 330 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 91 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 95.1 |
Your lightweight open-source personal agent.
Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.
nanobot has more GitHub stars: 50,147 versus 30,151 for sim. The gap is 19,996 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobot and sim 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. sim 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
nanobot scores 97.9 and sim scores 95.1. This page calls that a narrow lead for nanobot.