A
oh-my-openagent
81.6
70,968 stars · license n/a
AI Agents
ragflow leads by 16.3 · decisive
A
81.6
70,968 stars · license n/a
B · leads
97.9
94,309 stars · Apache-2.0
oh-my-openagent versus ragflow is a AI Agents comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. oh-my-openagent is written mainly in TypeScript; ragflow is written mainly in Go. The composite score is 81.6 for oh-my-openagent and 97.9 for ragflow.
ragflow has 94,309 GitHub stars to oh-my-openagent's 70,968, a gap of 23,341 (1.33×). Forks are 5,847 for oh-my-openagent and 11,335 for ragflow. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 93 versus 100.
Push history: oh-my-openagent was last pushed on 17 November 2026 (0 days ago), and ragflow was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,966 for oh-my-openagent (0.042 per star) and 1,317 for ragflow (0.014 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
oh-my-openagent 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. ragflow 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 30 for oh-my-openagent and 96 for ragflow. This is a procurement signal, not legal advice.
Only ragflow is marked self-hostable here (94,309 stars, deploy score 100). oh-my-openagent is not (70,968 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: oh-my-openagent is unpriced in this catalog, ragflow is open source.
ragflow is ahead on every scored dimension that is not level. Level dimensions: recent activity. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is recent activity at 0 points (100 vs 100).
ragflow finishes ahead at 97.9 against oh-my-openagent at 81.6, a 16.3 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 | oh-my-openagent | ragflow |
|---|---|---|
| GitHub stars | 70,968 | 94,309 |
| Forks | 5,847 | 11,335 |
| Open issues | 2,966 | 1,317 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 93 | 100 |
| Issue health | 70 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 81.6 | 97.9 |
OmO: Just type "mass ulw" keyword with your prompt. Now you are the master of graph engineering.
RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
ragflow has more GitHub stars: 94,309 versus 70,968 for oh-my-openagent. The gap is 23,341 stars.
Both were last pushed on 17 November 2026.
Only ragflow is marked self-hostable. oh-my-openagent is not.
oh-my-openagent 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. ragflow 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.
ragflow scores 97.9 and oh-my-openagent scores 81.6. This page calls that a decisive lead for ragflow.