As a novice only a few short months ago, I needed a way to implement embeddings which was easy and relatively inexpensive. WCS came through on both of those for me. In addition, as I began to gain more experience, I was able to appreciate more the vast array of embed and retrieval options WCS had to offer. Now, as a grizzled veteran now deploying my 3rd RAG system, I am extremely happy with the decision I made early on to go with WCS. Integrating into my code was very easy. Their support is great and timely, and they appear to spend a good amount of effort continuously improving an already superior system. In RAG, your answers are only ever going to be as good as the documents your model is given to analyze, and I have to say that WCS cosine similarity searches have consistently given me back the best documents for the best answers. Review collected by and hosted on G2.com.
I find it necessary to do queries in the WCS dashboard to both design processing code as well as troubleshoot -- and just to see what's in my vector store. The query syntax, while not terribly difficult, isn't the most intuitive. It sometimes takes a few minutes to go back and research how to construct the specific queries you need. It would be helpful if the queries you create are stored in the dashboard. Unfortunately, WCS has a bad habit of deleting them, forcing you to have to go back and re-create them every time you need them. That's actually my biggest pet peeve. Review collected by and hosted on G2.com.



