A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 17.5 · decisive
A · leads
96.5
25,581 stars · MIT
B
79.0
13,096 stars · license n/a
Activepieces versus Meshroom 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; Meshroom is written mainly in Python. The composite score is 96.5 for Activepieces and 79.0 for Meshroom.
Activepieces has 25,581 GitHub stars to Meshroom's 13,096, a gap of 12,485 (1.95×). Forks are 4,476 for Activepieces and 1,243 for Meshroom. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 100 versus 85.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and Meshroom was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 549 for Meshroom (0.042 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. Meshroom 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 Meshroom. This is a procurement signal, not legal advice.
Only Activepieces is marked self-hostable here (25,581 stars, deploy score 100). Meshroom is not (13,096 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, Meshroom is unpriced in this catalog.
Activepieces is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is issue health at 0 points (70 vs 70).
Activepieces finishes ahead at 96.5 against Meshroom at 79.0, a 17.5 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 | Meshroom |
|---|---|---|
| GitHub stars | 25,581 | 13,096 |
| Forks | 4,476 | 1,243 |
| Open issues | 961 | 549 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 70 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 96.5 | 79.0 |
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.
Node-based Visual Programming Toolbox
Activepieces has more GitHub stars: 25,581 versus 13,096 for Meshroom. The gap is 12,485 stars.
Both were last pushed on 17 November 2026.
Only Activepieces is marked self-hostable. Meshroom 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. Meshroom 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 Meshroom scores 79.0. This page calls that a decisive lead for Activepieces.