A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 9.7 · clear
A · leads
97.9
50,147 stars · MIT
B
88.2
23,434 stars · AGPL-3.0
nanobot versus skyvern 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 88.2 for skyvern.
nanobot has 50,147 GitHub stars to skyvern's 23,434, a gap of 26,713 (2.14×). Forks are 8,755 for nanobot and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 85.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for nanobot and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 stars) and skyvern (23,434 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, skyvern is open source.
nanobot is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against skyvern at 88.2, a 9.7 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 | nanobot | skyvern |
|---|---|---|
| GitHub stars | 50,147 | 23,434 |
| Forks | 8,755 | 2,246 |
| Open issues | 872 | 301 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 88.2 |
Your lightweight open-source personal agent.
Automate browser based workflows with AI
nanobot has more GitHub stars: 50,147 versus 23,434 for skyvern. The gap is 26,713 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobot and skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
nanobot scores 97.9 and skyvern scores 88.2. This page calls that a clear lead for nanobot.