A
InstaPy
83.4
18,414 stars · GPL-3.0
Workflow Automation
nanobot leads by 14.5 · clear
A
83.4
18,414 stars · GPL-3.0
B · leads
97.9
50,147 stars · MIT
InstaPy versus nanobot 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 83.4 for InstaPy and 97.9 for nanobot.
nanobot has 50,147 GitHub stars to InstaPy's 18,414, a gap of 31,733 (2.72×). Forks are 3,896 for InstaPy and 8,755 for nanobot. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 91 versus 100.
Push history: InstaPy was last pushed on 26 October 2026 (21 days ago), and nanobot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 586 for InstaPy (0.032 per star) and 872 for nanobot (0.017 per star). Issue-health scores are 70 and 84; activity scores are 78 and 100.
InstaPy 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. 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 64 for InstaPy and 96 for nanobot. This is a procurement signal, not legal advice.
In Workflow Automation, both InstaPy (18,414 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: InstaPy is open source, nanobot is open source.
nanobot is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is license flexibility at 32 points (64 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against InstaPy at 83.4, a 14.5 point clear 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 | InstaPy | nanobot |
|---|---|---|
| GitHub stars | 18,414 | 50,147 |
| Forks | 3,896 | 8,755 |
| Open issues | 586 | 872 |
| Adoption | 91 | 100 |
| Activity | 78 | 100 |
| Community | 91 | 100 |
| Issue health | 70 | 84 |
| License | 64 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 83.4 | 97.9 |
📷 Instagram Bot - Tool for automated Instagram interactions
Your lightweight open-source personal agent.
nanobot has more GitHub stars: 50,147 versus 18,414 for InstaPy. The gap is 31,733 stars.
nanobot was pushed more recently: 17 November 2026 versus 26 October 2026 for InstaPy. That is 21 days apart.
Yes. This catalog marks both InstaPy and nanobot as self-hostable. Confirm each project's deploy docs before you plan a migration.
InstaPy 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. 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 InstaPy scores 83.4. This page calls that a clear lead for nanobot.