HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
KruxAI
ragbuilder
Python2024–2024
KruxAI / ragbuilder

ragbuilder

A toolkit to create optimal Production-readyRetrieval Augmented Generation(RAG) setup for your data

2Distinct people
3Mentions
0Explicit recommenders
1.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A toolkit to create optimal Production-readyRetrieval Augmented Generation(RAG) setup for your data

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2024-08-03 07:01:25 UTC to 2024-10-03 04:04:32 UTC. Weeks start Monday, UTC.

012024-07-29 00:00:00 UTC to 2024-08-05 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJul 292024-08-05 00:00:00 UTC to 2024-08-12 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2024-08-12 00:00:00 UTC to 2024-08-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-19 00:00:00 UTC to 2024-08-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-26 00:00:00 UTC to 2024-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 262024-09-02 00:00:00 UTC to 2024-09-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-09 00:00:00 UTC to 2024-09-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-16 00:00:00 UTC to 2024-09-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-23 00:00:00 UTC to 2024-09-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-30 00:00:00 UTC to 2024-10-07 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsSep 30

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jul 292024-07-29 00:00:00 UTC2024-08-05 00:00:00 UTC110
Aug 52024-08-05 00:00:00 UTC2024-08-12 00:00:00 UTC110
Aug 122024-08-12 00:00:00 UTC2024-08-19 00:00:00 UTC000
Aug 192024-08-19 00:00:00 UTC2024-08-26 00:00:00 UTC000
Aug 262024-08-26 00:00:00 UTC2024-09-02 00:00:00 UTC000
Sep 22024-09-02 00:00:00 UTC2024-09-09 00:00:00 UTC000
Sep 92024-09-09 00:00:00 UTC2024-09-16 00:00:00 UTC000
Sep 162024-09-16 00:00:00 UTC2024-09-23 00:00:00 UTC000
Sep 232024-09-23 00:00:00 UTC2024-09-30 00:00:00 UTC000
Sep 302024-09-30 00:00:00 UTC2024-10-07 00:00:00 UTC110

What Hacker News says

3 sources
imaravind·Oct 3, 2024Submission

Ask HN: How are you extracting the best performance out of your RAG pipeline?

I've been working on various RAG (Retrieval Augmented Generation) projects, and I'm curious if you all are seeing any generalizeable patterns in building the most performant RAG for any given dataset? For eg: is it even possible to say that in “most” cases, the best retriever setup is going to be a combination of semantic search (embeddings) + keyword search (BM25) + some xyz technique? My hypothesis is that there’s no one-size-fits-all RAG design - every dataset is unique, every use-case is nuanced - and therefore, requires a uniquely optimized RAG pipeline. And it’s practically impossible to find the most optimal RAG setup for your dataset with a manual-trial-and-error approach - because the combinations of the different parameters of a RAG grow exponentially with each parameter (For eg: if you could choose from 5 different chunking str
Read the rest
ategies, 5 different chunk sizes, 5 different embedding models, 5 different retrievers, 5 different re-rankers, 5 different prompts, 5 different LLM settings - that’s 5^7 = 78125 different RAG configurations - which is practically impossible to try out exhaustively). I’d love to hear from people that are working extensively on RAG based use-cases, if my hypothesis above is flawed, and if so, what’s been your approach to building an optimal RAG pipeline, and how much time & effort has it been taking you? The reason I’m asking is because I’m working on a project [0] that performs automatic hyperparameter optimization on the various RAG parameters - so you basically just bring your dataset, and RAGBuilder will evaluate multiple configurations and help you identify what’s the best chunking strategy, what’s the best combination of retrievers to use, etc. for your dataset. [0]: https://github.com/KruxAI/ragbuilder
5 points · Open discussion

RAG(Retrieval Augmented Generation) Pipeline Tuning Tool

Looking for feedback on our Open source tool for building RAG and iterating through different combinations of RAG components(chunking, embedding model, retrievers, rankers) and creating optimal RAG. Currently there seems to be no scientific way apart from trial and error. Our tool aims to reduce time spent on iterating and evaluating RAG. Link: https://news.ycombinator.com/item?id=41145093 Link: https://github.com/kruxai/ragbuilder
2 points · Open discussion

Show HN: RAGBuilder – Hyperparameter tuning on various RAG parameters

A RAG has several moving parts: data ingestion, retrieval, re-ranking, generation etc.. Each part comes with numerous options. If we consider a toy example, where you could choose from: 5 different chunking methods, 5 different chunk sizes, 5 different embedding models, 5 different retrievers, 5 different re-rankers/ compressors 5 different prompts 5 different LLMs That’s 78,125 distinct RAG configurations! If you could try evaluating each one in just 5 mins, that’d still take 271 days of non-stop trial-and-error effort! In short, it’s kinda impossible to find your optimal RAG setup manually. So, how do you determine the most optimal RAG configuration for your data and use-case? Meet RagBuilder, a tool designed to help you create optimal, production-ready Retrieval-Augmented-Generation (RAG) setup for your data automatically. RagBuilder
Read the rest
performs hyperparameter tuning on various RAG parameters, such as chunking strategy (semantic, character, etc.) and chunk size (1000, 2000, etc.), to evaluate these configurations against a test dataset. This process identifies the best-performing setup tailored to your data. Check it out and let us know what you think! https://github.com/kruxai/ragbuilder
17 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.