A
robotframework
86.2
11,990 stars · Apache-2.0
Workflow Automation
Scrapling leads by 12.9 · clear
A
86.2
11,990 stars · Apache-2.0
B · leads
99.1
103,871 stars · BSD-3-Clause
robotframework versus Scrapling 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 Python. The composite score is 86.2 for robotframework and 99.1 for Scrapling.
Scrapling has 103,871 GitHub stars to robotframework's 11,990, a gap of 91,881 (8.66×). Forks are 2,589 for robotframework and 10,835 for Scrapling. On the log scale used inside this pair, adoption is 81 versus 100, and the fork community is 85 versus 100.
Push history: robotframework was last pushed on 11 November 2026 (6 days ago), and Scrapling was last pushed on 17 November 2026 (0 days ago). Open issues stand at 322 for robotframework (0.027 per star) and 21 for Scrapling (0.000 per star). Issue-health scores are 70 and 96; activity scores are 92 and 100.
robotframework 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. 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 96 for robotframework and 96 for Scrapling. This is a procurement signal, not legal advice.
In Workflow Automation, both robotframework (11,990 stars) and Scrapling (103,871 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: robotframework is open source, Scrapling is open source.
Scrapling is ahead on every scored dimension that is not level. Level dimensions: 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).
Scrapling finishes ahead at 99.1 against robotframework at 86.2, a 12.9 point clear 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 | robotframework | Scrapling |
|---|---|---|
| GitHub stars | 11,990 | 103,871 |
| Forks | 2,589 | 10,835 |
| Open issues | 322 | 21 |
| Adoption | 81 | 100 |
| Activity | 92 | 100 |
| Community | 85 | 100 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 86.2 | 99.1 |
Generic automation framework for acceptance testing and RPA
🕷️ 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 11,990 for robotframework. The gap is 91,881 stars.
Scrapling was pushed more recently: 17 November 2026 versus 11 November 2026 for robotframework. That is 6 days apart.
Yes. This catalog marks both robotframework and Scrapling as self-hostable. Confirm each project's deploy docs before you plan a migration.
robotframework 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. 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 robotframework scores 86.2. This page calls that a clear lead for Scrapling.