A
BubbleLab
63.2
1,100 stars · Apache-2.0
Workflow Automation
puppeteer leads by 35.9 · decisive
A
63.2
1,100 stars · Apache-2.0
B · leads
99.1
95,849 stars · Apache-2.0
BubbleLab versus puppeteer 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 63.2 for BubbleLab and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to BubbleLab's 1,100, a gap of 94,749 (87.14×). Forks are 182 for BubbleLab 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: BubbleLab was last pushed on 30 April 2026 (201 days ago), and puppeteer was last pushed on 17 November 2026 (0 days ago). Open issues stand at 41 for BubbleLab (0.037 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 70 and 96; activity scores are 36 and 100.
Both BubbleLab 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 BubbleLab (1,100 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: BubbleLab is open source, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is recent activity at 64 points (36 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against BubbleLab at 63.2, a 35.9 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 | BubbleLab | puppeteer |
|---|---|---|
| GitHub stars | 1,100 | 95,849 |
| Forks | 182 | 9,607 |
| Open issues | 41 | 201 |
| Adoption | 61 | 100 |
| Activity | 36 | 100 |
| Community | 57 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 63.2 | 99.1 |
Open-core workflow engine powering Bubble Lab — and fully runnable, hostable, and extensible on its own.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 1,100 for BubbleLab. The gap is 94,749 stars.
puppeteer was pushed more recently: 17 November 2026 versus 30 April 2026 for BubbleLab. That is 201 days apart.
Yes. This catalog marks both BubbleLab and puppeteer as self-hostable. Confirm each project's deploy docs before you plan a migration.
BubbleLab 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 BubbleLab scores 63.2. This page calls that a decisive lead for puppeteer.