A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 12.6 · clear
A · leads
97.4
112,653 stars · MIT
B
84.8
15,409 stars · MIT
Agent-Reach versus RD-Agent 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 84.8 for RD-Agent.
Agent-Reach has 112,653 GitHub stars to RD-Agent's 15,409, a gap of 97,244 (7.31×). Forks are 10,094 for Agent-Reach and 2,055 for RD-Agent. On the log scale used inside this pair, adoption is 100 versus 83, and the fork community is 100 versus 83.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and RD-Agent was last pushed on 21 October 2026 (27 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 250 for RD-Agent (0.016 per star). Issue-health scores are 96 and 84; activity scores are 92 and 78.
Both Agent-Reach and RD-Agent are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both Agent-Reach (112,653 stars) and RD-Agent (15,409 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: Agent-Reach is open source, RD-Agent is open source.
Agent-Reach is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 17 points (100 vs 83), and the tightest is self-hosting at 0 points (100 vs 100).
Agent-Reach finishes ahead at 97.4 against RD-Agent at 84.8, a 12.6 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 | Agent-Reach | RD-Agent |
|---|---|---|
| GitHub stars | 112,653 | 15,409 |
| Forks | 10,094 | 2,055 |
| Open issues | 133 | 250 |
| Adoption | 100 | 83 |
| Activity | 92 | 78 |
| Community | 100 | 83 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 84.8 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Research and development (R&D) is crucial for the enhancement of industrial productivity, especially in the AI era, where the core aspects of R&D are mainly focused on data and models. We are committed to automating these high-value generic R&D processes through R&D-Agent, which lets AI drive data-driven AI. 🔗https://aka.ms/RD-Agent-Tech-Report
Agent-Reach has more GitHub stars: 112,653 versus 15,409 for RD-Agent. The gap is 97,244 stars.
Agent-Reach was pushed more recently: 08 November 2026 versus 21 October 2026 for RD-Agent. That is 18 days apart.
Yes. This catalog marks both Agent-Reach and RD-Agent as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. RD-Agent 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Agent-Reach scores 97.4 and RD-Agent scores 84.8. This page calls that a clear lead for Agent-Reach.