Skip to content
DevUtils Online

Workflow Automation

Agent-Reach vs automa

Agent-Reach leads by 33.7 · decisive

B

automa

63.7

21,723 stars · license n/a

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

Agent-Reach has 112,653 GitHub stars to automa's 21,723, a gap of 90,930 (5.19×). Forks are 10,094 for Agent-Reach and 2,341 for automa. On the log scale used inside this pair, adoption is 100 versus 86, and the fork community is 100 versus 84.

Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and automa was last pushed on 02 March 2026 (260 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 379 for automa (0.017 per star). Issue-health scores are 96 and 84; activity scores are 92 and 36.

Agent-Reach is listed as MIT, 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. 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. License scores in this pair are 96 for Agent-Reach and 30 for automa. This is a procurement signal, not legal advice.

Only Agent-Reach is marked self-hostable here (112,653 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: Agent-Reach is open source, automa is unpriced in this catalog.

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

Agent-Reach finishes ahead at 97.4 against automa at 63.7, a 33.7 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.

Agent-Reach versus automa metrics
Signal Agent-Reach automa
GitHub stars 112,653 21,723
Forks 10,094 2,341
Open issues 133 379
Adoption 100 86
Activity 92 36
Community 100 84
Issue health 96 84
License 96 30
Self-hosting 100 35
Composite 97.4 63.7

Agent-Reach

Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Agent-Reach or automa?

Agent-Reach has more GitHub stars: 112,653 versus 21,723 for automa. The gap is 90,930 stars.

Which was updated more recently, Agent-Reach or automa?

Agent-Reach was pushed more recently: 08 November 2026 versus 02 March 2026 for automa. That is 251 days apart.

Can I self-host both Agent-Reach and automa?

Only Agent-Reach is marked self-hostable. automa is not.

Which license is easier to embed in a commercial product, Agent-Reach or automa?

Agent-Reach is listed as MIT, 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.

Who wins the Agent-Reach vs automa score?

Agent-Reach scores 97.4 and automa scores 63.7. This page calls that a decisive lead for Agent-Reach.

Related comparisons