Skip to content
DevUtils Online

Workflow Automation

automa vs Scrapling

Scrapling leads by 35.3 · decisive

A

automa

63.8

21,723 stars · license n/a

B · leads

Scrapling

99.1

103,871 stars · BSD-3-Clause

automa versus Scrapling is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. automa is written mainly in Vue; Scrapling is written mainly in Python. The composite score is 63.8 for automa and 99.1 for Scrapling.

Scrapling has 103,871 GitHub stars to automa's 21,723, a gap of 82,148 (4.78×). Forks are 2,341 for automa and 10,835 for Scrapling. On the log scale used inside this pair, adoption is 86 versus 100, and the fork community is 84 versus 100.

Push history: automa was last pushed on 02 March 2026 (260 days ago), and Scrapling was last pushed on 17 November 2026 (0 days ago). Open issues stand at 379 for automa (0.017 per star) and 21 for Scrapling (0.000 per star). Issue-health scores are 84 and 96; activity scores are 36 and 100.

automa 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 automa 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). automa is not (21,723 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: automa is unpriced in this catalog, Scrapling is open source.

Scrapling is ahead on every scored dimension that is not level. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is issue health at 12 points (84 vs 96).

Scrapling finishes ahead at 99.1 against automa at 63.8, a 35.3 point decisive 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.

automa versus Scrapling metrics
Signal automa Scrapling
GitHub stars 21,723 103,871
Forks 2,341 10,835
Open issues 379 21
Adoption 86 100
Activity 36 100
Community 84 100
Issue health 84 96
License 30 96
Self-hosting 35 100
Composite 63.8 99.1

Scrapling

🕷️ 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

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, automa or Scrapling?

Scrapling has more GitHub stars: 103,871 versus 21,723 for automa. The gap is 82,148 stars.

Which was updated more recently, automa or Scrapling?

Scrapling was pushed more recently: 17 November 2026 versus 02 March 2026 for automa. That is 260 days apart.

Can I self-host both automa and Scrapling?

Only Scrapling is marked self-hostable. automa is not.

Which license is easier to embed in a commercial product, automa or Scrapling?

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

Who wins the automa vs Scrapling score?

Scrapling scores 99.1 and automa scores 63.8. This page calls that a decisive lead for Scrapling.

Related comparisons