Thanks! The Community Edition is intentionally a 'primitive' – single container, zero config
However, I disagree on the 'maintenance tax'. ClawRAG isn't a weekend project; it's the retrieval engine extracted directly from our Enterprise RAG Core V4 system. It keeps the same connection pooling and health checks, so it is built to be 'always-on' without babying
The full V4 system adds Governance (Solomon Consensus/Multi-lane validation), not basic stability. You don't need the Enterprise layer just to keep the lights on
Re: PAIO – if they implement an MCP Client, ClawRAG can serve them. But I'd argue: if you already run a host, adding a container gives you provable privacy vs. 'trust us' managed services. I prefer owning the keys AND the lock ;-)
preparing to and found a pilot project with endboss pdf which im able to handle already.... but i focus on 100% quality in the db, so there is always a hitl below 100% confi...cant wait to proof im able to have a "hallucination free" rag..... main goal so far....next headache will be the update of data in the rag
Hi HN,
I built this "Community Edition" kit because I wanted a clean, self-hosted way to chat with my documents AND my codebase without sending data to the cloud.
It's a Docker Compose setup that wires together:
Docling for parsing (handles PDFs/Tables really well)
ChromaDB for vector storage
FastAPI backend + Simple UI
Ollama for local embeddings/LLM
The main feature: It separates "Code" and "Docs" into different collections with optimized chunking strategies, so you can ask "How does the auth middleware work?" and get actual code snippets back.
It's open source (MIT). I stripped out the heavy async worker queues from my enterprise version to keep this kit lightweight enough for a standard VPS or local machine.
Repo: https://github.com/2dogsandanerd/Knowledge-Base-Self-Hosting...
I'd love your feedback on the architecture or the parsing quality!