A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 31.4 · decisive
A · leads
97.4
112,653 stars · MIT
B
66.0
10,062 stars · LGPL-3.0
Agent-Reach versus tpot 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; tpot is written mainly in Jupyter Notebook. The composite score is 97.4 for Agent-Reach and 66.0 for tpot.
Agent-Reach has 112,653 GitHub stars to tpot's 10,062, a gap of 102,591 (11.20×). Forks are 10,094 for Agent-Reach and 1,557 for tpot. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 80.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and tpot was last pushed on 11 September 2025 (431 days ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 312 for tpot (0.031 per star). Issue-health scores are 96 and 70; activity scores are 92 and 16.
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. tpot is listed as LGPL-3.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. License scores in this pair are 96 for Agent-Reach and 78 for tpot. This is a procurement signal, not legal advice.
In Workflow Automation, both Agent-Reach (112,653 stars) and tpot (10,062 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, tpot is open source.
Agent-Reach is ahead on every scored dimension that is not level. Level dimensions: self-hosting. The widest gap is recent activity at 76 points (92 vs 16), and the tightest is self-hosting at 0 points (100 vs 100).
Agent-Reach finishes ahead at 97.4 against tpot at 66.0, a 31.4 point decisive 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 | tpot |
|---|---|---|
| GitHub stars | 112,653 | 10,062 |
| Forks | 10,094 | 1,557 |
| Open issues | 133 | 312 |
| Adoption | 100 | 79 |
| Activity | 92 | 16 |
| Community | 100 | 80 |
| Issue health | 96 | 70 |
| License | 96 | 78 |
| Self-hosting | 100 | 100 |
| Composite | 97.4 | 66.0 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
A Python Automated Machine Learning tool that optimizes machine learning pipelines using genetic programming.
Agent-Reach has more GitHub stars: 112,653 versus 10,062 for tpot. The gap is 102,591 stars.
Agent-Reach was pushed more recently: 08 November 2026 versus 11 September 2025 for tpot. That is 422 days apart.
Yes. This catalog marks both Agent-Reach and tpot 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. tpot is listed as LGPL-3.0, which this catalog treats as a weak-copyleft grant. Commercial use is generally expected, and source duties tend to follow modified copies of this project rather than the entire surrounding application. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Agent-Reach scores 97.4 and tpot scores 66.0. This page calls that a decisive lead for Agent-Reach.