A · leads
nanobot
97.9
50,147 stars · MIT
Workflow Automation
nanobot leads by 6.1 · narrow
A · leads
97.9
50,147 stars · MIT
B
91.8
16,776 stars · Apache-2.0
nanobot versus trigger.dev 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; trigger.dev is written mainly in TypeScript. The composite score is 97.9 for nanobot and 91.8 for trigger.dev.
nanobot has 50,147 GitHub stars to trigger.dev's 16,776, a gap of 33,371 (2.99×). Forks are 8,755 for nanobot and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 81.
Push history: nanobot was last pushed on 17 November 2026 (0 days ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 872 for nanobot (0.017 per star) and 268 for trigger.dev (0.016 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. trigger.dev is listed as Apache-2.0, 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 96 for nanobot and 96 for trigger.dev. This is a procurement signal, not legal advice.
In Workflow Automation, both nanobot (50,147 stars) and trigger.dev (16,776 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, trigger.dev is open source.
nanobot is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 19 points (100 vs 81), and the tightest is self-hosting at 0 points (100 vs 100).
nanobot finishes ahead at 97.9 against trigger.dev at 91.8, a 6.1 point narrow 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 | trigger.dev |
|---|---|---|
| GitHub stars | 50,147 | 16,776 |
| Forks | 8,755 | 1,534 |
| Open issues | 872 | 268 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 91.8 |
Your lightweight open-source personal agent.
Trigger.dev – build and deploy durable AI agents and workflows
nanobot has more GitHub stars: 50,147 versus 16,776 for trigger.dev. The gap is 33,371 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both nanobot and trigger.dev 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. trigger.dev is listed as Apache-2.0, 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 trigger.dev scores 91.8. This page calls that a narrow lead for nanobot.