Deploy Ragen
Self-hosted RAG chat with cited answers, Ragen Brain, MCP and admin panel.
Ragen API
Just deployed
Storage
Just deployed
/var/lib/postgresql/data
Redis
Just deployed
/data
qdrant
Just deployed
/qdrant/storage
Ragen Worker
Just deployed
Ragen Admin
Just deployed
Ragen App
Just deployed
Just deployed
Ragen Token Vault
Just deployed
Postgres-TokenVault
Just deployed
/var/lib/postgresql/data
Ragen MCP
Just deployed
docling
Just deployed
roomy-tray
Bucket
Just deployed
Deploy and Host Ragen on Railway
Ragen is a self-hosted AI assistant that answers from your own documents, with citations to the passages it used. Upload PDFs, Word files and spreadsheets to a knowledge base and ask questions in chat. Ragen Brain turns those documents into reviewed knowledge pages, and an MCP server brings your assistants into Claude Desktop and Cursor.
About Hosting Ragen
The template deploys the whole stack into one project, and the only value you enter is an OpenRouter API key. Chat runs on Claude Sonnet 5.5, Claude Haiku 5.5 rephrases questions and summarises documents, and OpenAI text-embedding-3-small embeds them, all through that one key. Every secret is generated for you. After the first deploy, open the web service's domain and create your account: the first account becomes the platform administrator, and the template ships no demo credentials. Back up ENCRYPTION_MASTER_KEY from the web variables: chat messages are encrypted under it and cannot be recovered without it.
Common Use Cases
- An internal assistant that answers questions about company policies, procedures and contracts, citing the exact source passage
- A reviewed company knowledge base built from existing documents with Ragen Brain
- Your documents available in Claude Desktop, Cursor and other MCP clients through Ragen's MCP server
Dependencies for Ragen Hosting
- An OpenRouter API key (openrouter.ai/keys), used for chat, summaries and embeddings
- Nothing else: Postgres, Redis, Qdrant, Docling and a storage bucket are part of the template
Implementation Details
| Service | Role |
|---|---|
web | The app: chat, knowledge base, Brain, settings (public domain) |
api | Public REST API, used by the MCP server and API keys |
worker | Background jobs: document parsing, embeddings, Brain extraction |
docling | Document parser for PDF, DOCX, XLSX and more (built from the Ragen repository) |
mcp | MCP server for Claude Desktop, Cursor and other clients (public domain) |
admin | Platform administration panel (public domain) |
vault | Token vault for connector credentials, with its own Postgres |
migrate | Applies database migrations on each deploy, then exits |
| Postgres, Redis, Qdrant, bucket | Data, job queue, vector search, uploaded files |
Left out on purpose, so check before you rely on it:
- PII masking is off: there is no Presidio service, so personal data is not masked before it reaches the model.
- Content moderation needs
OPENAI_MODERATION_KEY. Without it, that guardrail logs that it is not configured and lets messages through. - Mail is not configured: verification links and invitations go to the log until you set
RESEND_API_KEYor theSMTP_*variables onweb. - Encryption uses a key in an environment variable (
ENCRYPTION_PROVIDER=local). For production, consider a KMS.
Documentation: https://docs.ragen.ai/deploy-on-railway
Why Deploy Ragen 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 Ragen 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
OPENROUTER_API_KEY
Your OpenRouter API key (openrouter.ai/keys). The one value you must enter: it serves chat, document summaries and embeddings.
docling
webamigos/RagenAIRedis
redis:8.2Postgres-TokenVault
ghcr.io/railwayapp-templates/postgres-ssl:18qdrant
qdrant/qdrantroomy-tray
Bucket


