Item detail
github.com

infiniflow/ragflow

RepoRadar surfaced infiniflow/ragflow — a developer tool — into the RAG and Agent Infrastructure section, where it sits at Gold tier with a 'watch' verdict. Its strongest signal is workflow potential, scored 9.7 out of 10.

Score8.9
Popularity94.0
Riskconditional
TierGold
Score breakdown
Usefulness9.0
Novelty7.0
Momentum8.0
Maturity8.8
Open-source/build8.4
Evidence7.2
Workflow potential9.7
Setup ease4.2

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Adopt RAGFlow when you already run RAG-heavy products and want a stronger orchestration layer for connectors, retrieval, and agent context handling.

Who should use it

AI app builders shipping search-and-answer products data-platform teams evaluating self-hosted RAG infrastructure agent product teams needing shared context pipelines

Who should skip it

Move on from infiniflow/ragflow if the licensing terms, language support, or platform requirements do not fit your project.

About this signal

infiniflow/ragflow is tracked by RepoRadar as a developer tool in the RAG and Agent Infrastructure section. First seen 2026-06-18; the source record was last checked on 2026-06-18. The current verdict is 'watch' with a Gold tier and advanced setup difficulty. The standout signals for infiniflow/ragflow are workflow potential (9.7) and practical usefulness (9.0), while setup ease (4.2) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The infiniflow/ragflow record combines a 8.9/10 composite score with separate popularity (94.0), risk (conditional), and setup (advanced) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

Operationally heavy: retrieval/graph components need careful resource planning; Production-grade deployments need governance around data retention and access control.

Evidence links
Closest alternatives / related signals
rag agentic-retrieval infrastructure python llm
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

47 dated snapshots retained from 2026-06-18 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.9 current · +0.0 net
Repository momentum10.0 current · +2.0 net
GitHub stars (observed)87,951 current · +3,008 net
GitHub stars87,951 exact observation
Versionnightly
Last release2025-12-01T13:17:42Z
Maintenanceactive
Current riskconditional
Current verdictwatch
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.910.087,951conditionalwatchactive
2026-08-128.910.087,467conditionalwatchactive
2026-08-118.99.687,247conditionalwatchactive
2026-08-108.99.687,172conditionalwatchactive
2026-08-098.99.687,106conditionalwatchactive
2026-08-088.99.687,070conditionalwatchactive
2026-08-078.910.086,701conditionalwatchactive
2026-08-068.98.0Not recordedconditionalwatchnot recorded
2026-08-058.98.0Not recordedconditionalwatchnot recorded
2026-08-048.910.086,701conditionalwatchactive
2026-08-038.910.086,701conditionalwatchactive
2026-08-028.99.686,599conditionalwatchactive

Why the record changed

stars changed

Stars changed: 87467 → 87951.

stars changed

Stars changed: 87247 → 87467.

stars changed

Stars changed: 87172 → 87247.

stars changed

Stars changed: 87106 → 87172.

stars changed

Stars changed: 87070 → 87106.

stars changed

Stars changed: 86701 → 87070.

stars changed

Stars changed: 86599 → 86701.

stars changed

Stars changed: 86551 → 86599.

stars changed

Source-observed stars changed: 86527 → 86551. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Source-observed stars changed: 86526 → 86527. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 86229 → 86317.

stars changed

Source-observed stars changed: 86206 → 86229. This reports the retained observation delta and does not infer why the upstream change occurred.