emilianoc

6 ms·

1. 1.▲
   by emilianoc 1mo ago

   In traditional RAG (Retrieval-Augmented Generation), you use an LLM at runtime to read those retrieved documents and synthesize a direct, conversational answer for the user. That generative step is what incurs an API cost and adds latency p
2. 2.▲
   by emilianoc 1mo ago

   thanks :)
3. 3.▲
   by emilianoc 1mo ago

   Hi HN, I built RAGless to remove the LLM from the critical query path. Traditional RAG is powerful, but introduces non-deterministic behavior (hallucinations) and recurring API costs at runtime. RAGless shifts the LLM entirely to build&#x2F
4. 4.▲
   Show HN: RAGless – similar to RAG, but $0 LLM API costs at runtime(github.com)

   6 points by emilianoc 1mo ago|8 comments