Skip to content
DevUtils Online

Workflow Automation

automa vs nanobot

nanobot leads by 31.8 · decisive

A

automa

66.1

21,723 stars · license n/a

B · leads

nanobot

97.9

50,147 stars · MIT

automa versus nanobot is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. automa is written mainly in Vue; nanobot is written mainly in Python. The composite score is 66.1 for automa and 97.9 for nanobot.

nanobot has 50,147 GitHub stars to automa's 21,723, a gap of 28,424 (2.31×). Forks are 2,341 for automa and 8,755 for nanobot. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 86 versus 100.

Push history: automa was last pushed on 02 March 2026 (260 days ago), and nanobot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 379 for automa (0.017 per star) and 872 for nanobot (0.017 per star). Issue-health scores are 84 and 84; activity scores are 36 and 100.

automa 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. 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. License scores in this pair are 30 for automa and 96 for nanobot. This is a procurement signal, not legal advice.

Only nanobot is marked self-hostable here (50,147 stars, deploy score 100). automa is not (21,723 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: automa is unpriced in this catalog, nanobot is open source.

nanobot is ahead on every scored dimension that is not level. Level dimensions: issue health. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is issue health at 0 points (84 vs 84).

nanobot finishes ahead at 97.9 against automa at 66.1, a 31.8 point decisive margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

automa versus nanobot metrics
Signal automa nanobot
GitHub stars 21,723 50,147
Forks 2,341 8,755
Open issues 379 872
Adoption 92 100
Activity 36 100
Community 86 100
Issue health 84 84
License 30 96
Self-hosting 35 100
Composite 66.1 97.9

Questions this page answers

Which has more GitHub stars, automa or nanobot?

nanobot has more GitHub stars: 50,147 versus 21,723 for automa. The gap is 28,424 stars.

Which was updated more recently, automa or nanobot?

nanobot was pushed more recently: 17 November 2026 versus 02 March 2026 for automa. That is 260 days apart.

Can I self-host both automa and nanobot?

Only nanobot is marked self-hostable. automa is not.

Which license is easier to embed in a commercial product, automa or nanobot?

automa 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. 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.

Who wins the automa vs nanobot score?

nanobot scores 97.9 and automa scores 66.1. This page calls that a decisive lead for nanobot.

Related comparisons