A
conductor
91.4
32,478 stars · Apache-2.0
Workflow Automation
puppeteer leads by 7.7 · clear
A
91.4
32,478 stars · Apache-2.0
B · leads
99.1
95,849 stars · Apache-2.0
conductor versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. conductor is written mainly in Java; puppeteer is written mainly in TypeScript. The composite score is 91.4 for conductor and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to conductor's 32,478, a gap of 63,371 (2.95×). Forks are 1,074 for conductor and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 76 versus 100.
Push history: conductor 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 300 for conductor (0.009 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both conductor 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 conductor (32,478 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: conductor 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 fork community at 24 points (76 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against conductor 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 | conductor | puppeteer |
|---|---|---|
| GitHub stars | 32,478 | 95,849 |
| Forks | 1,074 | 9,607 |
| Open issues | 300 | 201 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 76 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 91.4 | 99.1 |
Conductor is an event driven agentic workflow engine providing durable and highly resilient execution engine for applications and AI Agents
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 32,478 for conductor. The gap is 63,371 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both conductor and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
conductor 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 conductor scores 91.4. This page calls that a clear lead for puppeteer.