A
n8n-as-code
76.5
1,663 stars · MIT
Workflow Automation
nanobot leads by 21.4 · decisive
A
76.5
1,663 stars · MIT
B · leads
97.9
50,147 stars · MIT
n8n-as-code versus nanobot is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. n8n-as-code is written mainly in TypeScript; nanobot is written mainly in Python. The composite score is 76.5 for n8n-as-code and 97.9 for nanobot.
nanobot has 50,147 GitHub stars to n8n-as-code's 1,663, a gap of 48,484 (30.15×). Forks are 190 for n8n-as-code and 8,755 for nanobot. On the log scale used inside this pair, adoption is 68 versus 100, and the fork community is 58 versus 100.
Push history: n8n-as-code was last pushed on 01 November 2026 (16 days ago), and nanobot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 20 for n8n-as-code (0.012 per star) and 872 for nanobot (0.017 per star). Issue-health scores are 84 and 84; activity scores are 78 and 100.
Both n8n-as-code 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 n8n-as-code (1,663 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: n8n-as-code is open source, nanobot is open source.
nanobot is ahead on every scored dimension that is not level. Level dimensions: issue health, license flexibility, self-hosting. The widest gap is fork community at 42 points (58 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against n8n-as-code at 76.5, a 21.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 | n8n-as-code | nanobot |
|---|---|---|
| GitHub stars | 1,663 | 50,147 |
| Forks | 190 | 8,755 |
| Open issues | 20 | 872 |
| Adoption | 68 | 100 |
| Activity | 78 | 100 |
| Community | 58 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 76.5 | 97.9 |
Give your AI agent n8n superpowers. 537 nodes with full schemas, 7,700+ templates, Git-like sync, and TypeScript workflows.
Your lightweight open-source personal agent.
nanobot has more GitHub stars: 50,147 versus 1,663 for n8n-as-code. The gap is 48,484 stars.
nanobot was pushed more recently: 17 November 2026 versus 01 November 2026 for n8n-as-code. That is 16 days apart.
Yes. This catalog marks both n8n-as-code and nanobot as self-hostable. Confirm each project's deploy docs before you plan a migration.
n8n-as-code 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 n8n-as-code scores 76.5. This page calls that a decisive lead for nanobot.