A
budibase
79.0
28,420 stars · license n/a
Workflow Automation
puppeteer leads by 20.1 · decisive
A
79.0
28,420 stars · license n/a
B · leads
99.1
95,849 stars · Apache-2.0
budibase 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 79.0 for budibase and 99.1 for puppeteer.
puppeteer has 95,849 GitHub stars to budibase's 28,420, a gap of 67,429 (3.37×). Forks are 2,237 for budibase and 9,607 for puppeteer. On the log scale used inside this pair, adoption is 89 versus 100, and the fork community is 84 versus 100.
Push history: budibase 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 318 for budibase (0.011 per star) and 201 for puppeteer (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
budibase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for budibase and 96 for puppeteer. This is a procurement signal, not legal advice.
Only puppeteer is marked self-hostable here (95,849 stars, deploy score 100). budibase is not (28,420 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: budibase is unpriced in this catalog, puppeteer is open source.
puppeteer is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is recent activity at 0 points (100 vs 100).
puppeteer finishes ahead at 99.1 against budibase at 79.0, a 20.1 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 | budibase | puppeteer |
|---|---|---|
| GitHub stars | 28,420 | 95,849 |
| Forks | 2,237 | 9,607 |
| Open issues | 318 | 201 |
| Adoption | 89 | 100 |
| Activity | 100 | 100 |
| Community | 84 | 100 |
| Issue health | 84 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 79.0 | 99.1 |
AI agents, automations and apps that run your operations. Model agnostic.
JavaScript API for Chrome and Firefox
puppeteer has more GitHub stars: 95,849 versus 28,420 for budibase. The gap is 67,429 stars.
Both were last pushed on 17 November 2026.
Only puppeteer is marked self-hostable. budibase is not.
budibase is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 budibase scores 79.0. This page calls that a decisive lead for puppeteer.