ragflow

infiniflow/ragflow

RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
13 Nov 2026
today
Ship score
100/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 91,447 → 93,921 (29 Sep – 10 Nov 2026)
+1,836 stars in the 28 days to 10 Nov 2026

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
94.1K
Forks
11.3K
Open issues
1.3K
Watchers
361
Primary language
Go
Created
12 Dec 2023
Owner
infiniflow · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 98 startups in the directory ship primarily in Go.

Topics

#agent-harness#agent-native-database#agentic-ai#agentic-retrieval#agentic-search#ai#ai-agents#context-engine#context-engineering#context-management#harness-engineering#knowledge-compilation#rag#retrieval-augmented-generation#retrieval-harness#search-harness

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on 22 Sep 2026 — os_startup 94%, self-hostable 76%, hosted offering 71%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the Sep 2025 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 13 Nov 2026This is the badge for infiniflow/ragflow, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/infiniflow/ragflow.svg)](https://ossean.com/infiniflow/ragflow)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.