A
open-claude-cowork
78.8
4,319 stars · MIT
Workflow Automation
trigger.dev leads by 19.1 · decisive
A
78.8
4,319 stars · MIT
B · leads
97.9
16,776 stars · Apache-2.0
open-claude-cowork 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. open-claude-cowork is written mainly in JavaScript; trigger.dev is written mainly in TypeScript. The composite score is 78.8 for open-claude-cowork and 97.9 for trigger.dev.
trigger.dev has 16,776 GitHub stars to open-claude-cowork's 4,319, a gap of 12,457 (3.88×). Forks are 701 for open-claude-cowork and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 89 versus 100.
Push history: open-claude-cowork was last pushed on 23 May 2026 (178 days ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 16 for open-claude-cowork (0.004 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 96 and 84; activity scores are 36 and 100.
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. 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 open-claude-cowork and 96 for trigger.dev. This is a procurement signal, not legal advice.
In Workflow Automation, both open-claude-cowork (4,319 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: open-claude-cowork is open source, trigger.dev is open source.
The lead is split. open-claude-cowork is furthest ahead on issue health (96 to 84), while trigger.dev is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
trigger.dev finishes ahead at 97.9 against open-claude-cowork at 78.8, a 19.1 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 | open-claude-cowork | trigger.dev |
|---|---|---|
| GitHub stars | 4,319 | 16,776 |
| Forks | 701 | 1,534 |
| Open issues | 16 | 268 |
| Adoption | 86 | 100 |
| Activity | 36 | 100 |
| Community | 89 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 78.8 | 97.9 |
Open Source version of Claude Cowork with 500+ SaaS app integrations
Trigger.dev – build and deploy durable AI agents and workflows
trigger.dev has more GitHub stars: 16,776 versus 4,319 for open-claude-cowork. The gap is 12,457 stars.
trigger.dev 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 open-claude-cowork and trigger.dev as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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.
trigger.dev scores 97.9 and open-claude-cowork scores 78.8. This page calls that a decisive lead for trigger.dev.