A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 17.0 · decisive
A · leads
97.9
50,147 stars · MIT
B
80.9
1,886 stars · MIT
nanobot versus OpenAdapt is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 97.9 for nanobot and 80.9 for OpenAdapt.
nanobot has 50,147 GitHub stars to OpenAdapt's 1,886, a gap of 48,261 (26.59×). Forks are 8,755 for nanobot and 284 for OpenAdapt. On the log scale used inside this pair, adoption is 100 versus 70, and the fork community is 100 versus 62.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and OpenAdapt was last pushed on 16 November 2026 (1 day ago). Open issues stand at 872 for nanobot (0.017 per star) and 88 for OpenAdapt (0.047 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
Both nanobot and OpenAdapt 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 nanobot (50,147 stars) and OpenAdapt (1,886 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, OpenAdapt 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 fork community at 38 points (100 vs 62), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against OpenAdapt at 80.9, a 17.0 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 | OpenAdapt |
|---|---|---|
| GitHub stars | 50,147 | 1,886 |
| Forks | 8,755 | 284 |
| Open issues | 872 | 88 |
| Adoption | 100 | 70 |
| Activity | 100 | 100 |
| Community | 100 | 62 |
| Issue health | 84 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 80.9 |
Your lightweight open-source personal agent.
For EHRs, payer portals, and any app your team clicks through. A person or an agent shows the task; OpenAdapt turns it into a local program that repeats the steps with no model calls, checks each save, and stops when something doesn't match.
nanobot has more GitHub stars: 50,147 versus 1,886 for OpenAdapt. The gap is 48,261 stars.
nanobot was pushed more recently: 17 November 2026 versus 16 November 2026 for OpenAdapt. That is 1 days apart.
Yes. This catalog marks both nanobot and OpenAdapt 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. OpenAdapt 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 OpenAdapt scores 80.9. This page calls that a decisive lead for nanobot.