A
budibase
78.6
28,420 stars · license n/a
Workflow Automation
Scrapling leads by 20.5 · decisive
A
78.6
28,420 stars · license n/a
B · leads
99.1
103,871 stars · BSD-3-Clause
budibase versus Scrapling is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. budibase is written mainly in TypeScript; Scrapling is written mainly in Python. The composite score is 78.6 for budibase and 99.1 for Scrapling.
Scrapling has 103,871 GitHub stars to budibase's 28,420, a gap of 75,451 (3.65×). Forks are 2,237 for budibase and 10,835 for Scrapling. On the log scale used inside this pair, adoption is 89 versus 100, and the fork community is 83 versus 100.
Push history: budibase was last pushed on 17 November 2026 (0 days ago), and Scrapling was last pushed on 17 November 2026 (0 days ago). Open issues stand at 318 for budibase (0.011 per star) and 21 for Scrapling (0.000 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. Scrapling is listed as BSD-3-Clause, 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 Scrapling. This is a procurement signal, not legal advice.
Only Scrapling is marked self-hostable here (103,871 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, Scrapling is open source.
Scrapling 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).
Scrapling finishes ahead at 99.1 against budibase at 78.6, a 20.5 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 | Scrapling |
|---|---|---|
| GitHub stars | 28,420 | 103,871 |
| Forks | 2,237 | 10,835 |
| Open issues | 318 | 21 |
| Adoption | 89 | 100 |
| Activity | 100 | 100 |
| Community | 83 | 100 |
| Issue health | 84 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 78.6 | 99.1 |
AI agents, automations and apps that run your operations. Model agnostic.
🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Scrapling has more GitHub stars: 103,871 versus 28,420 for budibase. The gap is 75,451 stars.
Both were last pushed on 17 November 2026.
Only Scrapling 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. Scrapling is listed as BSD-3-Clause, 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.
Scrapling scores 99.1 and budibase scores 78.6. This page calls that a decisive lead for Scrapling.