RagFlow

RagFlow is an open-source retrieval-augmented generation engine that combines deep document understanding with large language models to let self-hosters build…

  • AI
RagFlow is an open-source retrieval-augmented generation engine that combines deep document understanding with large language models to let self-hosters build private Q&A systems from PDFs, Word files, Markdown notes, and other documents.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

73/100 Good

Maintained
100last commit 15 days ago
Popular
9993,778 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
1016 GB minimum RAM

Availability: platform listings confirmed today

GitHub stars
93,778
Open issues
1338
Last commit
2026-11-06
Latest release
v1.0.0
License
Apache-2.0
Activity
declining

Checked 13 days ago - source: GitHub (infiniflow/ragflow)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 4 CPU core(s), 50 GB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start the backing services first Run the provided docker compose command to start the needed service containers: MinIO (file storage), Elasticsearch (search index), Redis (queues/cache), and MySQL (settings database). If these are not running, RagFlow cannot store files, index documents, or keep its configuration. source
  • Create your .env settings file first Copy .env.example to .env before starting RagFlow, because that file becomes your local configuration and should be kept private. If it is missing or left with wrong values, the app may use defaults that do not match your storage, network, or API setup. source
  • Use your API key and port 9380 When calling the RagFlow API, replace <YOUR_API_KEY> with your real key and set base_url to your server address and port 9380. Without the correct key and port, API clients cannot connect or are rejected. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Welche Hintergrunddienste müssen vor dem Start von RagFlow laufen?

Starte zuerst MinIO, Elasticsearch, Redis und MySQL mit dem mitgelieferten Docker-Compose-Befehl. Ohne diese Container kann RagFlow Dateien nicht speichern, Dokumente nicht indizieren und seine Konfiguration nicht halten.

Warum muss .env.example vor dem Start kopiert werden?

Erstelle aus .env.example die Datei .env, weil sie als lokale, private Konfiguration dient. Fehlt sie oder enthält sie falsche Werte, verwendet RagFlow möglicherweise Standardwerte, die nicht zu deinem Storage-, Netzwerk- oder API-Setup passen.

Welches Port und welchen Schlüssel verwende ich für die RagFlow API?

Setze base_url auf deine Serveradresse mit Port 9380 und ersetze <YOUR_API_KEY> durch deinen echten API-Schlüssel. Ohne korrekten Schlüssel und Port verbinden API-Clients nicht oder werden abgelehnt.

Was kann eine instabile RagFlow-Serverausführung verursachen?

Häufige Ursachen sind Ressourcenlecks oder Deadlocks im Backend, Netzwerkfehler bei Docker-/Host-Netzwerk oder anhaltende Redis-Verbindungsprobleme. Wenn ein Backend-Prozess hängt, aber nicht beendet wird, startet das Startskript es nicht automatisch neu.

Answers sourced from github.com, ragflow.io, ragflow.io, ragflow.io

Community

Collected 48 days ago - public community threads