A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 12.9 · clear
A · leads
97.9
50,147 stars · MIT
B
85.0
18,618 stars · AGPL-3.0
nanobot versus Windmill 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; Windmill is written mainly in Rust. The composite score is 97.9 for nanobot and 85.0 for Windmill.
nanobot has 50,147 GitHub stars to Windmill's 18,618, a gap of 31,529 (2.69×). Forks are 8,755 for nanobot and 1,165 for Windmill. On the log scale used inside this pair, adoption is 100 versus 91, and the fork community is 100 versus 78.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and Windmill was last pushed on 17 November 2026 (0 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 889 for Windmill (0.048 per star). Issue-health scores are 84 and 70; 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. Windmill 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 nanobot and 52 for Windmill. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 stars) and Windmill (18,618 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, Windmill is open source.
nanobot is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against Windmill at 85.0, a 12.9 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 | nanobot | Windmill |
|---|---|---|
| GitHub stars | 50,147 | 18,618 |
| Forks | 8,755 | 1,165 |
| Open issues | 872 | 889 |
| Adoption | 100 | 91 |
| Activity | 100 | 100 |
| Community | 100 | 78 |
| Issue health | 84 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 85.0 |
Your lightweight open-source personal agent.
Windmill runs scripts and approval flows as internal apps, with workers you can scale. It is used by teams that want automation closer to a developer platform than a no-code zap.
nanobot has more GitHub stars: 50,147 versus 18,618 for Windmill. The gap is 31,529 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobot and Windmill 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. Windmill 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.
nanobot scores 97.9 and Windmill scores 85.0. This page calls that a clear lead for nanobot.