Skip to content
DevUtils Online

Workflow Automation

Agent-Reach vs awx

Agent-Reach leads by 24.9 · decisive

B

awx

72.5

15,630 stars · license n/a

Agent-Reach versus awx 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 97.4 for Agent-Reach and 72.5 for awx.

Agent-Reach has 112,653 GitHub stars to awx's 15,630, a gap of 97,023 (7.21×). Forks are 10,094 for Agent-Reach and 3,698 for awx. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 89.

Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and awx was last pushed on 17 November 2026 (0 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 1,941 for awx (0.124 per star). Issue-health scores are 96 and 34; activity scores are 92 and 100.

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. awx 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 awx. This is a procurement signal, not legal advice.

Only Agent-Reach is marked self-hostable here (112,653 stars, deploy score 100). awx is not (15,630 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, awx is unpriced in this catalog.

The lead is split. Agent-Reach is furthest ahead on license flexibility (96 to 30), while awx is furthest ahead on recent activity (100 to 92). Choose the dimension a rollout cannot compromise on.

Agent-Reach finishes ahead at 97.4 against awx at 72.5, a 24.9 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 awx metrics
Signal Agent-Reach awx
GitHub stars 112,653 15,630
Forks 10,094 3,698
Open issues 133 1,941
Adoption 100 83
Activity 92 100
Community 100 89
Issue health 96 34
License 96 30
Self-hosting 100 35
Composite 97.4 72.5

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

awx

AWX provides a web-based user interface, REST API, and task engine built on top of Ansible. It is one of the upstream projects for Red Hat Ansible Automation Platform.

Project site · GitHub · Full profile

Questions this page answers

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

Agent-Reach has more GitHub stars: 112,653 versus 15,630 for awx. The gap is 97,023 stars.

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

awx was pushed more recently: 17 November 2026 versus 08 November 2026 for Agent-Reach. That is 9 days apart.

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

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

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

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. awx 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 awx score?

Agent-Reach scores 97.4 and awx scores 72.5. This page calls that a decisive lead for Agent-Reach.

Related comparisons