A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 5.9 · narrow
A · leads
96.5
25,581 stars · MIT
B
90.6
9,557 stars · Apache-2.0
Activepieces versus cadence 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; cadence is written mainly in Go. The composite score is 96.5 for Activepieces and 90.6 for cadence.
Activepieces has 25,581 GitHub stars to cadence's 9,557, a gap of 16,024 (2.68×). Forks are 4,476 for Activepieces and 931 for cadence. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 81.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and cadence was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 220 for cadence (0.023 per star). Issue-health scores are 70 and 70; 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. cadence 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 Activepieces and 96 for cadence. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and cadence (9,557 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, cadence is open source.
Activepieces is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 19 points (100 vs 81), and the tightest is self-hosting at 0 points (100 vs 100).
Activepieces finishes ahead at 96.5 against cadence at 90.6, a 5.9 point narrow 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 | cadence |
|---|---|---|
| GitHub stars | 25,581 | 9,557 |
| Forks | 4,476 | 931 |
| Open issues | 961 | 220 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 70 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 90.6 |
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.
Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
Activepieces has more GitHub stars: 25,581 versus 9,557 for cadence. The gap is 16,024 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and cadence 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. cadence 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.
Activepieces scores 96.5 and cadence scores 90.6. This page calls that a narrow lead for Activepieces.