You mentioned that spRAG uses OpenAI for embeddings, Claude 3 Haiku for AutoContext, and Cohere for reranking. Can you explain why & how did you make those choices?
Those are just the defaults, and spRAG is designed to be flexible in terms of the models you can use with it. For AutoContext (which is just a summarization task) Haiku offers a great balance of price and performance. Llama 3-8B would also be a great choice there, especially if you want something you can run locally. For reranking, the Cohere v3 reranker is by far the best performer on the market right now. And for e…
Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
11–20 of 24 posts
Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
#12Does this mean you're winding down your business? Just curious what the motivation to open source this was given this seems like your guy's core value add? Congrats on the launch.
For the larger companies and venture-backed startups we've talked to, they almost universally want to own their RAG stack in-house or build on open-source frameworks, rather than outsource it to an end-to-end solution provider. So open-sourcing our core retrieval tech is our bid to appeal to these developers.
Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
#13https://github.com/profintegra/raptor-rag https://github.com/langchain-ai/langchain/blob/master/cookbo...
Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
#14Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
#15How much do you expect auto-context and clustering+re-ranking to help for cases in which documents already have high-quality summaries? For context, I parse astrophysics research papers from arXiv and simply embed by paper abstracts (which must be of a certain size), and then append (parts of) the rest of the paper for RAG.
Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
#16Earlier quoted context omitted.
Those are just the defaults, and spRAG is designed to be flexible in terms of the models you can use with it. For AutoContext (which is just a summarization task) Haiku offers a great balance of price and performance. Llama 3-8B would also be a great choice there, especially if you want something you can run locally. For reranking, the Cohere v3 reranker is by far the best performer on the market right now. And for e…
I bet you'll get a lot more adoption if you put info about using it with local self-hosted LLMs there. I'll never trust a cloud service with the documents I want to RAG.
Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
#17How much do you expect auto-context and clustering+re-ranking to help for cases in which documents already have high-quality summaries? For context, I parse astrophysics research papers from arXiv and simply embed by paper abstracts (which must be of a certain size), and then append (parts of) the rest of the paper for RAG.
So the point of AutoContext is so you don't have to do that two-step process of first finding the right document, and then finding the right section of that document. I think it's cleaner to do it this way, but it's not necessarily going to perform any better or worse. But then spRAG also has the RSE part which is what identifies the right section(s) of the document. Whether or not that helps in your case is going to…
Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
#18I'd replace the "challenging real-world tasks" in the title with "dense text, like financial reports and legal documents". It sounds less general but that's a good thing. The repo is only two weeks old, and looks it, so how do you think spRAG distinguishes itself? This is a crowded space with more established players. The "vanilla RAG" benchmark figure you cite is not convincing because it can not be verified. Please…
That's great feedback. I actually went back and forth between those two descriptions. I agree that "dense text, like financial reports and legal documents" is more precise. Those are the kinds of use cases this project is built for. I want to keep this project tightly scoped to just retrieval over dense unstructured text, rather than trying to build a fully-featured RAG framework.
Maybe it's the same on the Python side, but it feels like nobody has nailed the perfect LLM wrapper library yet. I would focus on dev experience - make it dead simple to load in files and use it from 0-1.
Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
#19Does this mean you're winding down your business? Just curious what the motivation to open source this was given this seems like your guy's core value add? Congrats on the launch.
That's a great question. I'll start with a little context: most of the users of our existing hosted platform are no-code/low-code developers who choose us because we're the simplest solution for building what they want to build (primarily because we have end-to-end workflows like Chat built-in). The improved retrieval performance is a nice-to-have for this group, but usually not the primary reason they choose us. For…
Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks
#20are you automating the end to end RAG pipeline?