A
Activepieces
93.4
25,581 stars · MIT
Workflow Automation
nanobot leads by 4.5 · narrow
A
93.4
25,581 stars · MIT
B · leads
97.9
50,147 stars · MIT
Activepieces versus nanobot is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Activepieces is written mainly in TypeScript; nanobot is written mainly in Python. The composite score is 93.4 for Activepieces and 97.9 for nanobot.
nanobot has 50,147 GitHub stars to Activepieces's 25,581, a gap of 24,566 (1.96×). Forks are 4,476 for Activepieces and 8,755 for nanobot. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 93 versus 100.
Push history: Activepieces 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 961 for Activepieces (0.038 per star) and 872 for nanobot (0.017 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Both Activepieces 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 Activepieces (25,581 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: Activepieces is open source, nanobot is open source.
nanobot is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 14 points (70 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against Activepieces at 93.4, a 4.5 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 | Activepieces | nanobot |
|---|---|---|
| GitHub stars | 25,581 | 50,147 |
| Forks | 4,476 | 8,755 |
| Open issues | 961 | 872 |
| Adoption | 94 | 100 |
| Activity | 100 | 100 |
| Community | 93 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.4 | 97.9 |
Activepieces is a TypeScript workflow tool positioned as a self-hosted automation builder. It focuses on connecting business apps with a visual builder and an MIT-licensed core.
Your lightweight open-source personal agent.
nanobot has more GitHub stars: 50,147 versus 25,581 for Activepieces. The gap is 24,566 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and nanobot as self-hostable. Confirm each project's deploy docs before you plan a migration.
Activepieces 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 Activepieces scores 93.4. This page calls that a narrow lead for nanobot.