Self-hosted RAG (CDOC): how it works and when to use it
Self-hosted RAG (CDOC), adds documents with auto-chunking and metadata, then runs filtered ANN search with optional reranking, no separate vector database. Here's how Crowkis does it and why it matters for cost and safety.
Your users ask the same things all day, phrased a hundred different ways. Self-hosted RAG (CDOC) is how Crowkis adds documents with auto-chunking and metadata, then runs filtered ANN search with optional reranking, no separate vector database.
How it works
Crowkis adds documents with auto-chunking and metadata, then runs filtered ANN search with optional reranking, no separate vector database. It runs inside one Redis-compatible engine, so it composes with semantic caching, agent memory, and the other intelligence layers instead of being a separate service you wire together.
CDOC ADD doc "<text>" CHUNK 512 OVERLAP 64 META team=legal CDOC SEARCH "refund window?" K 3 FILTER team=legal RERANK
Why it matters
Repetitive LLM workloads are where the money is, and semantic caching can cut costs up to 60-70% on repetitive workloads. Self-hosted RAG (CDOC) is part of what makes that reuse safe rather than reckless, the difference between a cache you trust in production and one you audit after every incident. It's one self-hosted binary, Redis-compatible, free to run.
Infrastructure earns the critical path one boring, verifiable feature at a time.