rag-agent-platform vs rag-web-ui
Self-hosted RAG applications compared
rag-agent-platform and rag-web-ui both provide self-hostable ways to build document-based question-answering systems. rag-agent-platform adds configurable agents and MCP tool connections, while rag-web-ui focuses on knowledge-base chat, citations, and model and vector-store options.

rag-agent-platform: Self-Host RAG Agents and MCP Tools
A self-hosted Java and Next.js platform for combining document retrieval, LLM-powered agents, and MCP tools. It suits teams that want a configurable knowledge and agent workflow under their own infrastructure, with external services to operate.

rag-web-ui: Build Knowledge-Base Q&A with RAG
RAG Web UI is a self-hostable web application for creating question-answering systems over your own documents. It combines document ingestion, vector search, and configurable cloud or local language models, with a web interface and OpenAPI access.
| rag-agent-platform | rag-web-ui | |
|---|---|---|
| Language | Java | TypeScript |
| License | MIT | Apache-2.0 |
| Stars | 89 | 3.3k |
| Forks | 7 | 373 |
| Last analyzed | Oct 14, 2026 | Oct 3, 2026 |
Key differences
- rag-agent-platform combines document retrieval with agent publishing and MCP tools; rag-web-ui centers on multi-turn knowledge-base Q&A with citations and an OpenAPI interface.
- rag-agent-platform is written in Java with a Next.js frontend; rag-web-ui is written in TypeScript.
- rag-agent-platform uses PostgreSQL with PGVector and RabbitMQ for asynchronous document jobs; rag-web-ui supports ChromaDB or Qdrant and uses MinIO for object storage.
- rag-agent-platform is licensed under MIT, while rag-web-ui uses Apache-2.0.
- rag-agent-platform requires manual MCP gateway and tool-container configuration, and its Compose setup is described as a deployment reference rather than a one-command installation.
- rag-web-ui is described as actively developed but not ready for production, making it more suited to learning, prototyping, and evaluation.
Choose rag-agent-platform if you…
- need configurable agents alongside document retrieval and MCP tool connections.
- want to run a Java-based platform under your own infrastructure and can operate its supporting services.
- are prepared to configure MCP gateways and tool containers manually.
Choose rag-web-ui if you…
- want a web interface and OpenAPI access for document-grounded Q&A.
- need to compare cloud and local model options, including Ollama, and vector stores such as ChromaDB or Qdrant.
- are evaluating or prototyping a RAG system rather than assuming production readiness.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.