A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 17.4 · decisive
A · leads
97.9
50,147 stars · MIT
B
80.5
1,635 stars · Apache-2.0
nanobot versus rulego 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; rulego is written mainly in Go. The composite score is 97.9 for nanobot and 80.5 for rulego.
nanobot has 50,147 GitHub stars to rulego's 1,635, a gap of 48,512 (30.67×). Forks are 8,755 for nanobot and 164 for rulego. On the log scale used inside this pair, adoption is 100 versus 68, and the fork community is 100 versus 56.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and rulego was last pushed on 13 November 2026 (4 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 4 for rulego (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
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. rulego 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 rulego. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 stars) and rulego (1,635 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, rulego is open source.
The lead is split. nanobot is furthest ahead on fork community (100 to 56), while rulego is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
nanobot finishes ahead at 97.9 against rulego at 80.5, a 17.4 point decisive 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 | rulego |
|---|---|---|
| GitHub stars | 50,147 | 1,635 |
| Forks | 8,755 | 164 |
| Open issues | 872 | 4 |
| Adoption | 100 | 68 |
| Activity | 100 | 92 |
| Community | 100 | 56 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 80.5 |
Your lightweight open-source personal agent.
⛓️RuleGo is a lightweight, high-performance, embedded, next-generation component orchestration rule engine framework for Go.
nanobot has more GitHub stars: 50,147 versus 1,635 for rulego. The gap is 48,512 stars.
nanobot was pushed more recently: 17 November 2026 versus 13 November 2026 for rulego. That is 4 days apart.
Yes. This catalog marks both nanobot and rulego 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. rulego 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 rulego scores 80.5. This page calls that a decisive lead for nanobot.