A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 14.1 · clear
A · leads
96.5
25,581 stars · MIT
B
82.4
11,787 stars · license n/a
Activepieces versus ekko-studio 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 82.4 for ekko-studio.
Activepieces has 25,581 GitHub stars to ekko-studio's 11,787, a gap of 13,794 (2.17×). Forks are 4,476 for Activepieces and 1,476 for ekko-studio. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 87.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and ekko-studio was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 592 for ekko-studio (0.050 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. ekko-studio 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 ekko-studio. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and ekko-studio (11,787 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, ekko-studio is unpriced in this catalog.
Activepieces is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is self-hosting at 0 points (100 vs 100).
Activepieces finishes ahead at 96.5 against ekko-studio at 82.4, a 14.1 point clear 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 | ekko-studio |
|---|---|---|
| GitHub stars | 25,581 | 11,787 |
| Forks | 4,476 | 1,476 |
| Open issues | 961 | 592 |
| Adoption | 100 | 92 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 70 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 82.4 |
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.
Ekko Studio is a local-first AI workspace for multi-agent chat, coding, and visual workflows, available on desktop and the web.
Activepieces has more GitHub stars: 25,581 versus 11,787 for ekko-studio. The gap is 13,794 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and ekko-studio 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. ekko-studio 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 ekko-studio scores 82.4. This page calls that a clear lead for Activepieces.