A · leads
Agent-Reach
97.4
112,653 stars · MIT
Workflow Automation
Agent-Reach leads by 25.1 · decisive
A · leads
97.4
112,653 stars · MIT
B
72.3
12,531 stars · license n/a
Agent-Reach versus keep 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.3 for keep.
Agent-Reach has 112,653 GitHub stars to keep's 12,531, a gap of 100,122 (8.99×). Forks are 10,094 for Agent-Reach and 1,555 for keep. On the log scale used inside this pair, adoption is 100 versus 81, and the fork community is 100 versus 80.
Push history: Agent-Reach was last pushed on 08 November 2026 (9 days ago), and keep was last pushed on 16 November 2026 (1 day ago). Open issues stand at 133 for Agent-Reach (0.001 per star) and 708 for keep (0.056 per star). Issue-health scores are 96 and 52; 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. keep 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 keep. This is a procurement signal, not legal advice.
Only Agent-Reach is marked self-hostable here (112,653 stars, deploy score 100). keep is not (12,531 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, keep is unpriced in this catalog.
The lead is split. Agent-Reach is furthest ahead on license flexibility (96 to 30), while keep 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 keep at 72.3, a 25.1 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 | keep |
|---|---|---|
| GitHub stars | 112,653 | 12,531 |
| Forks | 10,094 | 1,555 |
| Open issues | 133 | 708 |
| Adoption | 100 | 81 |
| Activity | 92 | 100 |
| Community | 100 | 80 |
| Issue health | 96 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 97.4 | 72.3 |
Give your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
The open-source AIOps and alert management platform
Agent-Reach has more GitHub stars: 112,653 versus 12,531 for keep. The gap is 100,122 stars.
keep was pushed more recently: 16 November 2026 versus 08 November 2026 for Agent-Reach. That is 8 days apart.
Only Agent-Reach is marked self-hostable. keep is not.
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. keep 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.
Agent-Reach scores 97.4 and keep scores 72.3. This page calls that a decisive lead for Agent-Reach.