A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 11.3 · clear
A · leads
97.4
112,653 stars · MIT
B
86.1
11,990 stars · Apache-2.0
Agent-Reach versus robotframework 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 86.1 for robotframework.
Agent-Reach has 112,653 GitHub stars to robotframework's 11,990, a gap of 100,663 (9.40×). Forks are 10,094 for Agent-Reach and 2,589 for robotframework. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 85.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and robotframework was last pushed on 11 November 2026 (6 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 322 for robotframework (0.027 per star). Issue-health scores are 96 and 70; activity scores are 92 and 92.
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. 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. License scores in this pair are 96 for Agent-Reach and 96 for robotframework. This is a procurement signal, not legal advice.
In Workflow Automation, both Agent-Reach (112,653 stars) and robotframework (11,990 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, robotframework is open source.
Agent-Reach is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 26 points (96 vs 70), and the tightest is self-hosting at 0 points (100 vs 100).
Agent-Reach finishes ahead at 97.4 against robotframework at 86.1, a 11.3 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 | robotframework |
|---|---|---|
| GitHub stars | 112,653 | 11,990 |
| Forks | 10,094 | 2,589 |
| Open issues | 133 | 322 |
| Adoption | 100 | 81 |
| Activity | 92 | 92 |
| Community | 100 | 85 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 86.1 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Generic automation framework for acceptance testing and RPA
Agent-Reach has more GitHub stars: 112,653 versus 11,990 for robotframework. The gap is 100,663 stars.
robotframework was pushed more recently: 11 November 2026 versus 08 November 2026 for Agent-Reach. That is 3 days apart.
Yes. This catalog marks both Agent-Reach and robotframework 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Agent-Reach scores 97.4 and robotframework scores 86.1. This page calls that a clear lead for Agent-Reach.