A
cadence
86.1
9,557 stars · Apache-2.0
Workflow Automation
puppeteer leads by 13.0 · clear
A
86.1
9,557 stars · Apache-2.0
B · leads
99.1
95,849 stars · Apache-2.0
cadence versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cadence is written mainly in Go; puppeteer is written mainly in TypeScript. The composite score is 86.1 for cadence and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to cadence's 9,557, a gap of 86,292 (10.03×). Forks are 931 for cadence and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 75 versus 100.
Push history: cadence 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 220 for cadence (0.023 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.
Both cadence and puppeteer are listed as Apache-2.0. 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 cadence (9,557 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: cadence 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 cadence at 86.1, a 13.0 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 | cadence | puppeteer |
|---|---|---|
| GitHub stars | 9,557 | 95,849 |
| Forks | 931 | 9,607 |
| Open issues | 220 | 201 |
| Adoption | 80 | 100 |
| Activity | 100 | 100 |
| Community | 75 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.1 | 99.1 |
Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 9,557 for cadence. The gap is 86,292 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both cadence and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. 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 cadence scores 86.1. This page calls that a clear lead for puppeteer.