A
keep
80.6
12,531 stars · license n/a
Workflow Automation
trigger.dev leads by 17.3 · decisive
A
80.6
12,531 stars · license n/a
B · leads
97.9
16,776 stars · Apache-2.0
keep 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. keep is written mainly in Python; trigger.dev is written mainly in TypeScript. The composite score is 80.6 for keep and 97.9 for trigger.dev.
trigger.dev has 16,776 GitHub stars to keep's 12,531, a gap of 4,245 (1.34×). Forks are 1,555 for keep and 1,534 for trigger.dev. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 100 versus 100.
Push history: keep was last pushed on 16 November 2026 (1 day ago), and trigger.dev was last pushed on 17 November 2026 (0 days ago). Open issues stand at 708 for keep (0.056 per star) and 268 for trigger.dev (0.016 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
keep is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for keep and 96 for trigger.dev. This is a procurement signal, not legal advice.
Only trigger.dev is marked self-hostable here (16,776 stars, deploy score 100). keep is not (12,531 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: keep is unpriced in this catalog, trigger.dev is open source.
The lead is split. keep is furthest ahead on fork community (100 to 100), while trigger.dev is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
trigger.dev finishes ahead at 97.9 against keep at 80.6, a 17.3 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 | keep | trigger.dev |
|---|---|---|
| GitHub stars | 12,531 | 16,776 |
| Forks | 1,555 | 1,534 |
| Open issues | 708 | 268 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 100 |
| Issue health | 52 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 80.6 | 97.9 |
The open-source AIOps and alert management platform
Trigger.dev – build and deploy durable AI agents and workflows
trigger.dev has more GitHub stars: 16,776 versus 12,531 for keep. The gap is 4,245 stars.
trigger.dev was pushed more recently: 17 November 2026 versus 16 November 2026 for keep. That is 1 days apart.
Only trigger.dev is marked self-hostable. keep is not.
keep is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 keep scores 80.6. This page calls that a decisive lead for trigger.dev.