A
kandev
68.5
1,138 stars · AGPL-3.0
Workflow Automation
puppeteer leads by 30.6 · decisive
A
68.5
1,138 stars · AGPL-3.0
B · leads
99.1
95,849 stars · Apache-2.0
kandev versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. kandev is written mainly in Go; puppeteer is written mainly in TypeScript. The composite score is 68.5 for kandev and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to kandev's 1,138, a gap of 94,711 (84.23×). Forks are 188 for kandev and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 61 versus 100, and the fork community is 57 versus 100.
Push history: kandev 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 287 for kandev (0.252 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 34 and 96; activity scores are 100 and 100.
kandev is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 52 for kandev and 96 for puppeteer. This is a procurement signal, not legal advice.
In Workflow Automation, both kandev (1,138 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: kandev is open source, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is issue health at 62 points (34 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against kandev at 68.5, a 30.6 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 | kandev | puppeteer |
|---|---|---|
| GitHub stars | 1,138 | 95,849 |
| Forks | 188 | 9,607 |
| Open issues | 287 | 201 |
| Adoption | 61 | 100 |
| Activity | 100 | 100 |
| Community | 57 | 100 |
| Issue health | 34 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 68.5 | 99.1 |
AI Kanban & Development Environment. Orchestrate multiple agents, review changes, open PRs. Multi-provider, self-hostable, no telemetry.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 1,138 for kandev. The gap is 94,711 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both kandev and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
kandev is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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 kandev scores 68.5. This page calls that a decisive lead for puppeteer.