A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 15.2 · decisive
A · leads
97.9
50,147 stars · MIT
B
82.7
21,625 stars · GPL-3.0
nanobot versus Obtainium is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. nanobot is written mainly in Python; Obtainium is written mainly in Dart. The composite score is 97.9 for nanobot and 82.7 for Obtainium.
nanobot has 50,147 GitHub stars to Obtainium's 21,625, a gap of 28,522 (2.32×). Forks are 8,755 for nanobot and 704 for Obtainium. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 72.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and Obtainium was last pushed on 01 November 2026 (16 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 403 for Obtainium (0.019 per star). Issue-health scores are 84 and 84; activity scores are 100 and 78.
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. Obtainium is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for nanobot and 64 for Obtainium. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 stars) and Obtainium (21,625 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, Obtainium is open source.
nanobot is ahead on every scored dimension that is not level. Level dimensions: issue health, self-hosting. The widest gap is license flexibility at 32 points (96 vs 64), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against Obtainium at 82.7, a 15.2 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 | Obtainium |
|---|---|---|
| GitHub stars | 50,147 | 21,625 |
| Forks | 8,755 | 704 |
| Open issues | 872 | 403 |
| Adoption | 100 | 92 |
| Activity | 100 | 78 |
| Community | 100 | 72 |
| Issue health | 84 | 84 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 82.7 |
Your lightweight open-source personal agent.
Get Android app updates straight from the source.
nanobot has more GitHub stars: 50,147 versus 21,625 for Obtainium. The gap is 28,522 stars.
nanobot was pushed more recently: 17 November 2026 versus 01 November 2026 for Obtainium. That is 16 days apart.
Yes. This catalog marks both nanobot and Obtainium 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. Obtainium is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
nanobot scores 97.9 and Obtainium scores 82.7. This page calls that a decisive lead for nanobot.