Weaviate Cloud Premium

What do you like best about the product?

The best part of this product is that it’s an open-source project, so it’s flexible to deploy on my own server. It doesn’t depend on their servers, which basically means I’m not tied to their infrastructure. Another thing I like is the hybrid search: I can use vector search or traditional keyword search, and it gives me good flexibility in how I search. It also has a production-ready setup that supports Kubernetes, so it can handle millions of search words. Overall, I like its flexible and adaptable nature. As it supports Kubernetes deployment so that search is very fast.

What do you dislike about the product?

I dislike is that it can be hard to set up at the beginning. I’ve also found that debugging vector search issues isn’t always straightforward, because it can be difficult to understand why a particular query returns the results it does. There are many configuration options, which is powerful, but it also makes the learning curve steeper for developers who are new to vector databases. Clearer error messages and simpler debugging guidance would make the developer experience much easier.

What problems is the product solving and how is that benefiting you?

The other software problem is that was not opensource that why I have depends on there server. It search quality so fast and I have option I can choose traditional key search or else I go for vector search. It also search fast according to key word and give to my ai agent so that I can get accurate data. For me as a developer, the main benefit is that I can quickly store embeddings and retrieve relevant information based on meaning rather than relying only on keyword matching. This is particularly useful when working with large amounts of documents or unstructured data. It also simplifies the integration of AI-powered search into backend applications. It ui looks cool than other.

What do you like best about the product?

I like that Weaviate makes it fairly straightforward to work with vector data and search through it. The documentation is useful when setting things up, and the dashboard makes it easy to keep track of the projects and collections. It also works well for experimenting with AI and search-related use cases.

What do you dislike about the product?

It can take some time to understand the different concepts if you're new to vector databases. Some of the configuration options can also feel a little overwhelming at first.

What problems is the product solving and how is that benefiting you?

Weaviate helps with storing and searching vector data, which is useful for AI-based search and retrieval use cases. It gives a convenient way to experiment with semantic search without having to build the whole infrastructure from scratch.

What do you like best about the product?

Weaviate is an all-in-one platform for building vector search, RAG, and agent memory management for us. With it, we design, build, and ship the entire AI stack, from local development through to our AWS production environment. Above all, it’s open source, which helps eliminate vendor lock-in concerns for our organization and also provides the flexibility to customize, improving overall performance.

With its vector database, we store, index, and retrieve different types of media information for our products, which supports scaling AI agentic systems. It also includes an Explorer that runs semantic, keyword, and hybrid search with aggregation, without needing to write GraphQL that saves time for our engineers.

Weaviate embeddings also help deliver efficient, faster models like Snowflake designed for enterprise-level retrieval operations.

What do you dislike about the product?

Although it has decent features, the UI feels slightly outdated based on my experience. When it comes to integrations with third-party platforms outside of the machine learning ecosystem, it’s not quite there yet. That said, because of the open-source community on GitHub, I expect the number of integrations to grow over time for other tech stacks that we use daily.

It does offer a 7-day free trial, but after that, calculating the overall monthly cost is complicated. It charges different services at different rates, which makes it hard to understand the final price per month. We have to use a calculator to add up all the final costs.

What problems is the product solving and how is that benefiting you?

Its native data query agent turns natural language–based questions into database queries and operations, which eliminates the time we used to spend writing SQL. This AI-based query agent delivers good results with dynamic filters, cross-collection routing, and source citation for our conversational AI apps, including customer-support chatbots. We can upload or add new databases from our knowledge base into collections, where we’re able to review detailed metadata and properties to evaluate the dataset.

It also includes a fully managed memory for AI agents called Engram, which remembers personalized preferences and decisions across all of our agent sessions. This helps shrink the context window and sends relevant, structured memories to our production agents during customer interactions.

We noticed our database costs dropped by 11% thanks to more efficient resource consumption and an optimized memory footprint. On top of that, it offloads tenant details to cold storage, which further reduces storage usage and cost.

It also secures and isolates our customer data, which is an important safety net for us. The open-source community has created support documentation that’s handy when we need to troubleshoot and fix issues.

What do you like best about the product?

I use Weaviate for efficiently storing vector data, which is crucial for embeddings and the retrieval phase of a RAG implementation. I appreciate its open-source nature and the efficient vector retrieval, which is necessary for ensuring the retrieval phase is accurate and fast. Additionally, AWS support is great, and the initial setup was straightforward.

What do you dislike about the product?

I think finetuning the self-hosting option is a bit complex. The RAM usage can be high depending on the dataset, so if self-hosting, several decisions regarding this have to be made. You have to scale horizontally in some cases if you want to keep it running smoothly. The initial setup was great, but finetuning is not as easy.

What problems is the product solving and how is that benefiting you?

I use Weaviate for efficient vector data storage in a RAG pipeline. It enhances the retrieval phase by being fast and accurate, which is essential as the pipeline is large and can't afford extra latency.

What do you like best about the product?

Using weaviate, it makes it straightforward to build semantic search and retrieve relevant information without having to manage vector search logic from scratch

What do you dislike about the product?

I felt like there was higher memory consumption in the case of weaviate

What problems is the product solving and how is that benefiting you?

it mainly solves the problem of storing and searching vector data for semantic retrieval