The framework built specifically for RAG pipelines
RAGAS (Retrieval-Augmented Generation Assessment) provides metrics designed for the four-stage failure space of a RAG system: retrieval quality, context relevance, answer faithfulness, and answer relevance. If you ship RAG, you want it.
The four core RAGAS metrics
- Faithfulness — Does the answer make claims supported by the retrieved context? (catches hallucination)
- Answer Relevancy — Does the answer address the question? (catches off-topic responses)
- Context Precision — Of the retrieved chunks, how many are actually relevant? (catches retriever pulling junk)
- Context Recall — Did the retriever find all the chunks needed to answer? (catches retriever missing crucial info)
Together they decompose "is this RAG output good?" into the four sub-questions that tell you which part failed.
Why this decomposition matters
A vague "answer is bad" tells the team nothing. RAGAS scores tell you: high faithfulness + low recall = retriever missing docs. Low faithfulness + high recall = generator hallucinating despite having the right context. Each diagnosis points to a different fix.
Implementation reality
RAGAS uses LLM-as-Judge under the hood for most of its metrics, so it inherits judge costs and biases. Calibrate against humans on your specific RAG corpus before trusting absolute numbers. Use the metrics as relative signals (this version vs that version) more than as absolute quality measurements.