A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 20.5 · decisive
A · leads
96.5
25,581 stars · MIT
B
76.0
4,319 stars · MIT
Activepieces versus open-claude-cowork is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Activepieces is written mainly in TypeScript; open-claude-cowork is written mainly in JavaScript. The composite score is 96.5 for Activepieces and 76.0 for open-claude-cowork.
Activepieces has 25,581 GitHub stars to open-claude-cowork's 4,319, a gap of 21,262 (5.92×). Forks are 4,476 for Activepieces and 701 for open-claude-cowork. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 78.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and open-claude-cowork was last pushed on 23 May 2026 (178 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 16 for open-claude-cowork (0.004 per star). Issue-health scores are 70 and 96; activity scores are 100 and 36.
Both Activepieces and open-claude-cowork are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and open-claude-cowork (4,319 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, open-claude-cowork is open source.
The lead is split. Activepieces is furthest ahead on recent activity (100 to 36), while open-claude-cowork is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
Activepieces finishes ahead at 96.5 against open-claude-cowork at 76.0, a 20.5 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 | Activepieces | open-claude-cowork |
|---|---|---|
| GitHub stars | 25,581 | 4,319 |
| Forks | 4,476 | 701 |
| Open issues | 961 | 16 |
| Adoption | 100 | 82 |
| Activity | 100 | 36 |
| Community | 100 | 78 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 76.0 |
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.
Open Source version of Claude Cowork with 500+ SaaS app integrations
Activepieces has more GitHub stars: 25,581 versus 4,319 for open-claude-cowork. The gap is 21,262 stars.
Activepieces was pushed more recently: 17 November 2026 versus 23 May 2026 for open-claude-cowork. That is 178 days apart.
Yes. This catalog marks both Activepieces and open-claude-cowork 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. open-claude-cowork 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.
Activepieces scores 96.5 and open-claude-cowork scores 76.0. This page calls that a decisive lead for Activepieces.