Skip to content
DevUtils Online

Workflow Automation

puppeteer vs sim

puppeteer leads by 6.0 · narrow

A · leads

puppeteer

99.1

95,849 stars · Apache-2.0

B

sim

93.1

30,151 stars · Apache-2.0

puppeteer versus sim 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 99.1 for puppeteer and 93.1 for sim.

puppeteer has 95,849 GitHub stars to sim's 30,151, a gap of 65,698 (3.18×). Forks are 9,607 for puppeteer and 3,915 for sim. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 90.

Push history: puppeteer was last pushed on 17 November 2026 (0 days ago), and sim was last pushed on 17 November 2026 (0 days ago). Open issues stand at 201 for puppeteer (0.002 per star) and 330 for sim (0.011 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

Both puppeteer and sim 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 puppeteer (95,849 stars) and sim (30,151 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: puppeteer is open source, sim 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 12 points (96 vs 84), and the tightest is self-hosting at 0 points (100 vs 100).

puppeteer finishes ahead at 99.1 against sim at 93.1, a 6.0 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

puppeteer versus sim metrics
Signal puppeteer sim
GitHub stars 95,849 30,151
Forks 9,607 3,915
Open issues 201 330
Adoption 100 90
Activity 100 100
Community 100 90
Issue health 96 84
License 96 96
Self-hosting 100 100
Composite 99.1 93.1

sim

Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, puppeteer or sim?

puppeteer has more GitHub stars: 95,849 versus 30,151 for sim. The gap is 65,698 stars.

Which was updated more recently, puppeteer or sim?

Both were last pushed on 17 November 2026.

Can I self-host both puppeteer and sim?

Yes. This catalog marks both puppeteer and sim as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, puppeteer or sim?

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. sim 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.

Who wins the puppeteer vs sim score?

puppeteer scores 99.1 and sim scores 93.1. This page calls that a narrow lead for puppeteer.

Related comparisons