A
Activepieces
91.4
25,581 stars · MIT
Workflow Automation
puppeteer leads by 7.7 · clear
A
91.4
25,581 stars · MIT
B · leads
99.1
95,849 stars · Apache-2.0
Activepieces versus puppeteer 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 91.4 for Activepieces and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to Activepieces's 25,581, a gap of 70,268 (3.75×). Forks are 4,476 for Activepieces and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 92 versus 100.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 70 and 96; 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. puppeteer 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 puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and puppeteer (95,849 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, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 26 points (70 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against Activepieces at 91.4, a 7.7 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 | puppeteer |
|---|---|---|
| GitHub stars | 25,581 | 95,849 |
| Forks | 4,476 | 9,607 |
| Open issues | 961 | 201 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.4 | 99.1 |
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.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 25,581 for Activepieces. The gap is 70,268 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and puppeteer 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. puppeteer 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.
puppeteer scores 99.1 and Activepieces scores 91.4. This page calls that a clear lead for puppeteer.