2 ms·
The other open source option for this that I'm familiar with is Nango[0]. How are you different? Also, a big challenge in this space is pricing. How are you th
by tayloramurphy 2y ago
The other open source option for this that I'm familiar with is Nango[0]. How are you different?
Also, a big challenge in this space is pricing. How are you thinking about tackling that?
[0] https://github.com/nangoHQ/nango https://github.com/nangoHQ/nango
- nael_ob 2y agoYes they built a cool product! Actually, we aim to focus on companies feeding their LLMs by providing embeddings and chunkings out of the box on top of all the data we sync. We don't only help you connect with 3rd parties but also receive data that can be interpreted for AI use cases (e.g: RAG).
- thenaturalist 2y agoThe optimal chunking strategy is often highly, highly dependent on the data used and questions to be answered. The net is plastered with blog posts about optimal strategies, of which there seem to be more than 10 and new approaches popping up often. It seems consensus that trial and error is the way to go to optimize cost and performance. How do you plan to tackle this when providing it out of the box?
- nael_ob 2y agoThat's why we wanted to try the OSS approach where contributors can help keep up with the optimal strategy. We also plan to build an engine to test each strategy and compare retrieval perf before choosing one at runtime.
- rflih96 2y agoHey - for pricing, we're going usage based on two metrics : amount of third-party connections and volume of data transformed (for chunking / embedding). Ps: This will evolve in the next months probably!