Local retrieval,
without the vector tax.
Jev RAG searches local documents through seven selectable paths: BM25 + Jev, agentic lexical search, embedding hybrid retrieval, multi-round Agentic Hybrid, corpus-taxonomy routing, a unified Jev Passage Gate, or hierarchical Jev Line Search. Embeddings remain optional.
git clone https://github.com/aifabrice/jev-rag.gitPublic benchmark
See what each stage adds.
Complete BEIR NFCorpus test split. Select a pipeline to compare its recorded retrieval quality against the BM25 baseline.
A dev-selected zero-call rank fusion improved the Jev-only order; two-round planning still raised cold retrieval latency to 6.99 s median.
Architecture
Start simple. Add semantics only when they earn their keep.
Deliberate trade-offs
No architecture wins every query.
Exact terms, IDs and names
BM25 is fast, local, transparent, and excellent when question language overlaps the source.
Synonyms and paraphrases
The default path can miss semantic matches. Agentic search or hybrid retrieval can widen recall.
Know what leaves the machine
Default retrieval stays local before reranking. Line Search is different: a bounded representation of every indexed passage is sent to Jev in windows, making it the most expensive mode.
Direct answer
What is Jev RAG?
Jev RAG is an open-source, local-first knowledge search application. It indexes files into SQLite FTS5, retrieves passages with BM25, uses the Jev model to rerank evidence, and asks MiniMax to produce a cited answer. Its default path does not require embeddings or a vector database.
Use BM25 for exact terms, Agentic for query reformulation, and hybrid retrieval for semantic recall. Use experimental Line Search when you want to measure Jev-only full-corpus retrieval and accept its larger cost and remote-data boundary.
Try it on your own corpus