Skip to content
DevUtils Online

Workflow Automation

bruno vs puppeteer

puppeteer leads by 6.3 · narrow

A

bruno

92.8

48,427 stars · MIT

B · leads

puppeteer

99.1

95,849 stars · Apache-2.0

bruno versus puppeteer is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bruno is written mainly in JavaScript; puppeteer is written mainly in TypeScript. The composite score is 92.8 for bruno and 99.1 for puppeteer.

puppeteer has 95,849 GitHub stars to bruno's 48,427, a gap of 47,422 (1.98×). Forks are 3,115 for bruno and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 94 versus 100, and the fork community is 88 versus 100.

Push history: bruno 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 2,002 for bruno (0.041 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 70 and 96; activity scores are 100 and 100.

bruno 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 bruno and 96 for puppeteer. This is a procurement signal, not legal advice.

In Workflow Automation, both bruno (48,427 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: bruno 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 bruno at 92.8, a 6.3 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.

bruno versus puppeteer metrics
Signal bruno puppeteer
GitHub stars 48,427 95,849
Forks 3,115 9,607
Open issues 2,002 201
Adoption 94 100
Activity 100 100
Community 88 100
Issue health 70 96
License 96 96
Self-hosting 100 100
Composite 92.8 99.1

Questions this page answers

Which has more GitHub stars, bruno or puppeteer?

puppeteer has more GitHub stars: 95,849 versus 48,427 for bruno. The gap is 47,422 stars.

Which was updated more recently, bruno or puppeteer?

Both were last pushed on 17 November 2026.

Can I self-host both bruno and puppeteer?

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

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

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

Who wins the bruno vs puppeteer score?

puppeteer scores 99.1 and bruno scores 92.8. This page calls that a narrow lead for puppeteer.

Related comparisons