Deploy RAGFlow
RAGFlow v1.0.0 RAG engine: Elasticsearch, MinIO, MySQL, all on volumes
Just deployed
/data
Elasticsearch
Just deployed
/usr/share/elasticsearch/data
Just deployed
/data
Just deployed
/var/lib/mysql
Just deployed
/var/lib/kvrocks
Just deployed
Deploy and Host RAGFlow on Railway
RAGFlow is an open-source retrieval-augmented generation (RAG) engine by InfiniFlow. It parses PDFs, Word and Excel files, slides, scans and web pages into searchable chunks, then answers questions over them with citations. You build chat assistants, search apps and agent workflows on top of your own documents, with the LLM provider you choose.
About Hosting RAGFlow
RAGFlow v1.0.0 is a stack of six parts: the RAGFlow server (web UI, API, admin console and ingestion worker), Elasticsearch for full-text and vector search, MinIO for uploaded files, MySQL for metadata, Kvrocks for cache and run state, and NATS JetStream for the parsing queue. This template deploys all six, wired over Railway's private network, with every image pinned to a version and digest and every stateful service on its own volume. All passwords are generated per deployment, self-registration is off, and only the RAGFlow web service is public. Plan for about 3 GB of memory at rest; parsing large PDFs is CPU-heavy.
Common Use Cases
- Chat with your company's documents, contracts, manuals or papers, with answers that cite the source passages
- Build a private knowledge base and search app over PDFs, spreadsheets and scanned files
- Create agent workflows that retrieve from your datasets and call an LLM of your choice (OpenAI, Anthropic, Gemini, Ollama and more)
Dependencies for RAGFlow Hosting
- An API key for an LLM and an embedding model provider (added in RAGFlow's UI after deploy, not in Railway)
- About 3 GB of memory for the whole stack at rest
Deployment Dependencies
- RAGFlow v1.0.0 release: https://github.com/infiniflow/ragflow/releases/tag/v1.0.0
- RAGFlow docs: https://ragflow.io/docs/
- Template repo (Dockerfiles, changelog): https://github.com/aalfath/ragflow-railway-template
Implementation Details
What you get: RAGFlow (public, port 80), Elasticsearch 8.11.3, MinIO (pgsty/silo), MySQL 8.4, Kvrocks 2.16 and NATS 2.14, each built from a folder of the template repo. Volumes hold Elasticsearch indexes, uploaded files, the MySQL database, Kvrocks data and the NATS queue, so a redeploy or restart keeps everything.
After deploy:
- Open your RAGFlow URL and add
/admin. Sign in asadmin@ragflow.iowith the value ofDEFAULT_SUPERUSER_PASSWORDfrom the RAGFlow service's Variables tab. This account is for the admin console only. - Under User management, create your own account and one for each teammate. Self-registration is off; set
ENABLE_REGISTER=1on the RAGFlow service to open it. - Sign in at your RAGFlow URL with your new account, add a model provider under Model providers, then create a dataset, upload documents and parse them.
Updates: the services build from the public repo aalfath/ragflow-railway-template. When a new RAGFlow version is tested there, Railway shows you an "update available" notice. Read CHANGELOG.md in the repo first, and back up the MySQL and MinIO volumes before a major upgrade.
Not included: GPU mode and the local embedding server (Railway has no GPUs), and the agent code sandbox, which needs the Docker socket.
Why Deploy RAGFlow on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying RAGFlow on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content

