picohen

In fact, we will be releasing a blog post in the next few days of how we do real-time syncing for a RAG application with postgres hosted on supabase

Postgres is already available :)

Well, of course I'm biased on the answer :). But to give a not-so-biased answer, I would first try to understand what the project is about and whether RAG is a priority in it. If the project is leveraging agents and LLMs without worrying too much on context/up-to-date data then Haystack could be a good option. If the focus is to eventually use RAG then our framework could help.

Additionally, there might be a potential route where both are used, depending on the use case.

Feel free to dm if you want to chat further on this!

Relevance calculations are handled by the vector db but we try to improve such relevance with the use of metadata (you will see how our components have "selectors" so that metadata can flow all the way to the vector database at the vector level and have an influence when results/scores get retrieved at search time)

our server was overloaded yesterday but we fixed it! let me know if you still have issues.