A
leon
91.9
17,690 stars · MIT
Workflow Automation
nanobot leads by 6.0 · narrow
A
91.9
17,690 stars · MIT
B · leads
97.9
50,147 stars · MIT
leon versus nanobot is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. leon is written mainly in TypeScript; nanobot is written mainly in Python. The composite score is 91.9 for leon and 97.9 for nanobot.
nanobot has 50,147 GitHub stars to leon's 17,690, a gap of 32,457 (2.83×). Forks are 1,484 for leon and 8,755 for nanobot. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 80 versus 100.
Push history: leon was last pushed on 17 November 2026 (0 days ago), and nanobot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 118 for leon (0.007 per star) and 872 for nanobot (0.017 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both leon and nanobot 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 leon (17,690 stars) and nanobot (50,147 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: leon is open source, nanobot 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 20 points (80 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against leon at 91.9, a 6.0 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 | leon | nanobot |
|---|---|---|
| GitHub stars | 17,690 | 50,147 |
| Forks | 1,484 | 8,755 |
| Open issues | 118 | 872 |
| Adoption | 90 | 100 |
| Activity | 100 | 100 |
| Community | 80 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.9 | 97.9 |
🧠 Leon is your open-source personal assistant.
Your lightweight open-source personal agent.
nanobot has more GitHub stars: 50,147 versus 17,690 for leon. The gap is 32,457 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both leon and nanobot as self-hostable. Confirm each project's deploy docs before you plan a migration.
leon 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
nanobot scores 97.9 and leon scores 91.9. This page calls that a narrow lead for nanobot.