A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 1.8 · narrow
A · leads
96.5
25,581 stars · MIT
B
94.7
16,776 stars · Apache-2.0
Activepieces 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. Both projects are written mainly in TypeScript. The composite score is 96.5 for Activepieces and 94.7 for trigger.dev.
Activepieces has 25,581 GitHub stars to trigger.dev's 16,776, a gap of 8,805 (1.52×). Forks are 4,476 for Activepieces and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 87.
Push history: Activepieces 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 961 for Activepieces (0.038 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Activepieces 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 Activepieces and 96 for trigger.dev. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 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: Activepieces is open source, trigger.dev is open source.
The lead is split. Activepieces is furthest ahead on fork community (100 to 87), while trigger.dev is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Activepieces finishes ahead at 96.5 against trigger.dev at 94.7, a 1.8 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 | Activepieces | trigger.dev |
|---|---|---|
| GitHub stars | 25,581 | 16,776 |
| Forks | 4,476 | 1,534 |
| Open issues | 961 | 268 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 94.7 |
Activepieces is a TypeScript workflow tool positioned as a self-hosted automation builder. It focuses on connecting business apps with a visual builder and an MIT-licensed core.
Trigger.dev – build and deploy durable AI agents and workflows
Activepieces has more GitHub stars: 25,581 versus 16,776 for trigger.dev. The gap is 8,805 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.
Activepieces 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.
Activepieces scores 96.5 and trigger.dev scores 94.7. This page calls that a narrow lead for Activepieces.