A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 18.2 · decisive
A · leads
97.9
50,147 stars · MIT
B
79.7
10,094 stars · license n/a
nanobot versus superplane 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; superplane is written mainly in Go. The composite score is 97.9 for nanobot and 79.7 for superplane.
nanobot has 50,147 GitHub stars to superplane's 10,094, a gap of 40,053 (4.97×). Forks are 8,755 for nanobot and 710 for superplane. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 72.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and superplane was last pushed on 17 November 2026 (0 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 266 for superplane (0.026 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. superplane is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for nanobot and 30 for superplane. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 stars) and superplane (10,094 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, superplane is unpriced in this catalog.
nanobot is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against superplane at 79.7, a 18.2 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 | superplane |
|---|---|---|
| GitHub stars | 50,147 | 10,094 |
| Forks | 8,755 | 710 |
| Open issues | 872 | 266 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 79.7 |
Your lightweight open-source personal agent.
Open source factory for one-shot engineering
nanobot has more GitHub stars: 50,147 versus 10,094 for superplane. The gap is 40,053 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobot and superplane 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. superplane is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
nanobot scores 97.9 and superplane scores 79.7. This page calls that a decisive lead for nanobot.