A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 19.0 · decisive
A · leads
96.5
25,581 stars · MIT
B
77.5
12,531 stars · license n/a
Activepieces versus keep 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; keep is written mainly in Python. The composite score is 96.5 for Activepieces and 77.5 for keep.
Activepieces has 25,581 GitHub stars to keep's 12,531, a gap of 13,050 (2.04×). Forks are 4,476 for Activepieces and 1,555 for keep. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 87.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and keep was last pushed on 16 November 2026 (1 day ago). Open issues stand at 961 for Activepieces (0.038 per star) and 708 for keep (0.056 per star). Issue-health scores are 70 and 52; 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. 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. License scores in this pair are 96 for Activepieces and 30 for keep. This is a procurement signal, not legal advice.
Only Activepieces is marked self-hostable here (25,581 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: Activepieces is open source, keep is unpriced in this catalog.
Activepieces is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is recent activity at 0 points (100 vs 100).
Activepieces finishes ahead at 96.5 against keep at 77.5, a 19.0 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 | keep |
|---|---|---|
| GitHub stars | 25,581 | 12,531 |
| Forks | 4,476 | 1,555 |
| Open issues | 961 | 708 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 70 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 96.5 | 77.5 |
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.
The open-source AIOps and alert management platform
Activepieces has more GitHub stars: 25,581 versus 12,531 for keep. The gap is 13,050 stars.
Activepieces was pushed more recently: 17 November 2026 versus 16 November 2026 for keep. That is 1 days apart.
Only Activepieces is marked self-hostable. keep is not.
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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Activepieces scores 96.5 and keep scores 77.5. This page calls that a decisive lead for Activepieces.