Weaviate Cloud Premium

What do you like best about the product?

I really loved Weaviate's native hybrid search feature. It's perfect for handling complex queries in our insurance claim documents, where adjusters often need to use alphanumeric policy codes with natural language questions. This feature combines BM25 keyword scoring with HNSW vector similarity out of the box, which is fantastic. Another aspect I like is the recent upgrade to the Python client (V4 API), especially the type hinting, which integrates seamlessly with our Python codebase. This has made development much smoother and easier for us. I also appreciate Weaviate's ability to manage both data residency and security constraints effectively and the option to tune infrastructure to control storage costs.

What do you dislike about the product?

In our project, dialing in the hybrid search requires quite a bit of effort and manual tuning, particularly when adjusting the alpha parameter (keyword vs vector) and going through trial and error to get the fusion ranking correct. Additionally, while Weaviate Cloud offers ease of use, managing the open-source version locally via Docker presents noticeable operational complexity compared to a fully managed serverless database.

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

In our insurance claims project, Weaviate solves our need for precise document retrieval by using native hybrid search, combining semantic vector and keyword searches, particularly useful in handling specific insurance terms. This improves retrieval accuracy for our claims adjusters.

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

What do you like best about the product?

What I like most about Weaviate is how easy it is to build semantic search and RAG applications around it. The vector search is fast and flexible, and I like that it supports structured metadata along with embeddings, so I can narrow down results without making the retrieval logic overly complicated.

What do you dislike about the product?

The main thing I find challenging with Weaviate is that there can be a learning curve when setting up more advanced configurations, especially around schemas, indexing, and tuning retrieval. It also takes some time to understand how to get the best results from the vector search instead of relying on the default setup. For smaller projects, it can sometimes feel like more infrastructure than I actually need.

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

Weaviate mainly helps with the search and retrieval side of AI applications. I use it to store and search vectorized data based on semantic similarity, which is much more useful than relying only on keyword matching. It makes things like RAG and knowledge-base search easier to build, and helps return more relevant context to the application without having to manually manage the retrieval layer.

What do you like best about the product?

As the Email Marketing & Design Coordinator at Creative Edge Design Studio, the best part about Weaviate for my daily workflow is its powerful natural language semantic search, which completely fixed my biggest workflow headache with our old Pinecone vector database. Before switching, I could only search by exact keywords, which meant I could never quickly find tailored email templates for niche client projects. Last quarter, I needed to make a warm, minimalist re-engagement newsletter for a local boutique skincare brand, and I knew we had similar past drafts, but I couldn’t recall the exact file names or keywords. I wasted almost two hours manually digging through cloud folders and old Pinecone search results with no luck. With Weaviate, I can type plain descriptive sentences about tone, design style and client industry, and it pulls perfectly matched archived newsletters and marketing snippets instantly. I also love that I can build separate asset collections for retail, hospitality and creative clients, which keeps my campaign research hyper-targeted. It pairs extremely well with LlamaIndex, letting me generate brand-consistent email drafts only from our studio’s approved content, no generic AI copy. Since we’re a 32-person small design team with no data engineers, I’m grateful I can tweak basic metadata schemas and organize new campaign assets on my own. This tool has cut my email pre-production research time in half, letting me focus more on custom email layout design for Figma and polishing Mailchimp campaign content instead of hunting for reference materials.

What do you dislike about the product?

My biggest frustrations with Weaviate all stem from it being built for technical engineers, not marketing/design staff like me, and it creates constant avoidable work delays. The lack of a visual GUI for bulk content uploads is my top issue. A month ago, I tried archiving 60+ finished client newsletter CSV files to update our asset library. All the natural line breaks and soft paragraph spacing in my email copy broke the scripted batch uploads repeatedly. With no drag-and-drop tool to auto-fix formatting errors, I spent an entire afternoon manually editing every single file just to finish the import. On top of that, its hybrid metadata filtering is super unreliable in real work scenarios. When I was building a seasonal holiday email campaign for a local café client recently, I filtered my search strictly for hospitality industry assets. Even with precise tagging, Weaviate kept pulling unrelated retail brand promotion emails into my results. I had to manually sift through dozens of mismatched drafts, killing time I reserved for email layout design. To make it worse, there’s no auto incremental indexing for my LlamaIndex workflow. After I uploaded new hospitality email templates, I forgot to manually reindex, and LlamaIndex generated outdated, mismatched email copy for my client campaign. There’s also no native link to Mailchimp, forcing me to manually copy all finalized content over. These small but frequent flaws make Weaviate’s great core functionality unnecessarily cumbersome for non-technical creative teams.

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

Weaviate completely solved the slow, inefficient asset search problem I struggled with heavily when we used Pinecone for our email marketing workflows. Previously, every time I built new Mailchimp newsletter campaigns or designed custom email layouts on Figma, I had to rely on rigid keyword searches or manual folder browsing to find past client templates. Last spring, I spent nearly half a workday looking for soft-toned brand update emails for creative studio clients, with no accurate search results to work with. Now, Weaviate’s semantic search lets me describe my campaign needs in plain language and pull precise, industry-specific email archives instantly. It works seamlessly with LlamaIndex to generate customized, on-brand email drafts, eliminating generic AI content and keeping all our client campaign messaging consistent. It also lets me categorize assets by client vertical, which standardizes my entire content reuse workflow. That said, the tool still creates new operational problems for our engineer-less small team. Bulk content imports require coding work that I’m not familiar with, leading to frequent upload failures and manual file cleanup. Unstable metadata filtering still forces me to sort irrelevant search results for every new campaign. Plus, missing auto-indexing and native Mailchimp integrations create last-minute content errors and repetitive manual work. Overall, it massively upgrades our asset retrieval efficiency but still lacks user-friendly adjustments for marketing and design day-to-day use.

What do you like best about the product?

Its seamless hybrid search combining BM25 and vector search and native module integrations. It makes setting up, scaling, and retrieving data for production-grade RAG applications remarkably fast and easy.

What do you dislike about the product?

The initial setup and GraphQL/API query structure have a steep learning curve for new teams. While the documentation is improving, debugging complex filter queries and schema errors can still be time-consuming.

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

Traditional SQL and keyword-based databases often fall short when queries include synonyms, misspellings, or more conceptual matches. Weaviate, on the other hand, focuses on intent and context instead of relying on exact string matching.

What do you like best about the product?

What I like most about Weaviate is how straightforward it makes working with vector search and embeddings. The setup feels intuitive, and it’s easy to store, search, and retrieve relevant data for AI applications without adding unnecessary complexity to my workflow.

What do you dislike about the product?

What I dislike about Weaviate is that some of its advanced features and configuration options can feel a bit overwhelming at first. It can take a while to understand the different settings and to get everything configured exactly the way you want.

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

Weaviate simplifies how we store and search vector data for AI applications. It makes it easier to retrieve relevant information quickly, which cuts down on manual searching and keeps our AI workflows more efficient, organized, and easier to manage.

What do you like best about the product?

It natively supports hybrid search, allowing developers to combine dense vector search (for semantic meaning) with traditional keyword search (BM25). This is widely considered the gold standard for retrieving highly accurate context in RAG applications.

What do you dislike about the product?

Instead of using standard SQL, Weaviate's primary query language is a custom implementation of GraphQL. While powerful for complex graph relationships, developers accustomed to traditional relational databases often report a steep learning curve.

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

Beyond just storing isolated vectors, Weaviate allows you to define cross-references and relationships between data objects (similar to a graph database), making it easier to represent highly complex, interconnected enterprise data.