Live data from Hacker News

Show HN: RagTune – EXPLAIN ANALYZE for your RAG retrieval layer

github.com

1–3 of 3 posts

Show HN: RagTune – EXPLAIN ANALYZE for your RAG retrieval layer

#1
CLI tool to debug and benchmark RAG retrieval without LLM calls.

- `ragtune explain "query"` → see what was retrieved with scores - `ragtune simulate` → batch eval with recall/MRR metrics - `ragtune compare` → compare embedders or chunk sizes - CI/CD mode for quality gates

Works with Qdrant, pgvector, Weaviate, Chroma, Pinecone.

Built because I kept guessing why retrieval was bad. Now I can see exactly what's happening.

Show HN: RagTune – EXPLAIN ANALYZE for your RAG retrieval layer
github.com

Re: Show HN: RagTune – EXPLAIN ANALYZE for your RAG retrieval layer

#3

[dead]

Thanks! To answer your questions:

*Backends:* Currently supports Qdrant, pgvector, Weaviate, Chroma, and Pinecone. Adding more is straightforward since it's just implementing a Store interface. Let me know if I missed some good backend!

*Relevance scoring:* No LLM-as-judge — that's intentional. RagTune focuses on retrieval-layer metrics only:

- Vector similarity scores (what the DB returns) - Recall@K, MRR against your golden set - Score distribution diagnostics

The philosophy is: debug retrieval separately from generation. If your retrieval is broken, no amount of prompt engineering will fix it.

For chunk size/overlap optimization — exactly the use case! `ragtune compare --chunk-sizes 256,512,1024` lets you see the impact directly.

Happy to hear feedback if you try it!