Skip to content
DevUtils Online

Workflow Automation

Activepieces vs leon

Activepieces leads by 1.6 · narrow

B

leon

94.9

17,690 stars · MIT

Activepieces versus leon 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 94.9 for leon.

Activepieces has 25,581 GitHub stars to leon's 17,690, a gap of 7,891 (1.45×). Forks are 4,476 for Activepieces and 1,484 for leon. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 87.

Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and leon was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 118 for leon (0.007 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.

Both Activepieces and leon are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Workflow Automation, both Activepieces (25,581 stars) and leon (17,690 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, leon is open source.

The lead is split. Activepieces is furthest ahead on fork community (100 to 87), while leon is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.

Activepieces finishes ahead at 96.5 against leon at 94.9, a 1.6 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

Activepieces versus leon metrics
Signal Activepieces leon
GitHub stars 25,581 17,690
Forks 4,476 1,484
Open issues 961 118
Adoption 100 96
Activity 100 100
Community 100 87
Issue health 70 84
License 96 96
Self-hosting 100 100
Composite 96.5 94.9

Activepieces

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Activepieces or leon?

Activepieces has more GitHub stars: 25,581 versus 17,690 for leon. The gap is 7,891 stars.

Which was updated more recently, Activepieces or leon?

Both were last pushed on 17 November 2026.

Can I self-host both Activepieces and leon?

Yes. This catalog marks both Activepieces and leon as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Activepieces or leon?

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. leon 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the Activepieces vs leon score?

Activepieces scores 96.5 and leon scores 94.9. This page calls that a narrow lead for Activepieces.

Related comparisons