Weaviate is an open-source vector database, Apache-2.0 at its core, that stores embeddings and retrieves them through native hybrid search: BM25 keyword matching fused with vector similarity in one query, a design that has helped its GitHub repository cross 16.7k stars. Atlan’s context layer sits upstream of Weaviate the same way it sits upstream of any vector database, governing what gets embedded before Weaviate ever indexes it.
Founded in Amsterdam in 2019, Weaviate’s real distinction from most vector database vendors is a deployment philosophy: run it yourself, or let Weaviate run it for you, on the same underlying code.
- Native hybrid search, tuned by an alpha parameter that weighs keyword matching against vector similarity
- Collections, cross-references, and vectorizer modules, closer to structured data than a flat vector index
- Deployment choice: self-hosted, Weaviate Cloud, or an experimental embedded mode
- A 2025-2026 agentic push, led by the Query Agent, routing natural-language questions across collections
| Fact | Detail |
|---|---|
| What it is | Open-source vector database with native hybrid search, plus a managed cloud option |
| Founder/company | Bob van Luijt and Etienne Dilocker, Amsterdam, 2019 |
| Deployment | Self-hosted (Docker/Kubernetes, free) or Weaviate Cloud (Free/Flex/Premium tiers) |
| Pricing model | Free and open-source self-hosted; usage-tiered subscription on Weaviate Cloud |
| Core differentiator | Native hybrid search (BM25 + vector fusion) and deployment flexibility |
| Governance gap | No native source certification, sensitivity classification, or lineage |
What is Weaviate?
Permalink to “What is Weaviate?”Weaviate is a company and an open-source project, not a single product SKU: an engine anyone can run for free, and a business that sells a managed version of the same code. Bob van Luijt and Etienne Dilocker incorporated the company in Amsterdam in 2019, building on an open-source project the two had already been developing since 2016. In an interview with Microsoft’s Agent Framework team, CEO van Luijt described the category plainly: “A vector database like Weaviate is stateful and directly integrates with generative machine learning models.”
Funding has scaled with that thesis: a $50M Series B in 2023 led by Index Ventures, joined by Battery Ventures and Zetta Venture Partners. Gartner forecasts a 75.3% CAGR for the vector database segment of the DBMS market, and Fortune Business Insights projects it growing from $2.58 billion in 2025 to $17.91 billion by 2034.
A vector database exists because LLMs are stateless between calls: a model has no memory of what it retrieved a moment ago unless something outside it stores and re-serves it. Pinecone, Qdrant, Milvus, and Weaviate all answer that problem, but Weaviate’s answer to “who operates this” is structurally different from a managed-only competitor: an Apache-2.0 core you can run yourself is the default identity.
How does Weaviate’s architecture work?
Permalink to “How does Weaviate’s architecture work?”Three structural pieces separate Weaviate’s data model from a flat vector index: collections, vectorizer modules, and cross-references.
Collections and schema
Permalink to “Collections and schema”Weaviate organizes data into collections (formerly “classes”), each defining properties, a configured vectorizer, and optional cross-references, graph-style links between objects in different collections, per Weaviate’s documentation. A support-ticket collection can cross-reference the customer it belongs to, and a query can traverse that link at retrieval time, closer to structured data than Pinecone’s flat namespace model. Still, cross-references are pointers, not the reasoning layer of a knowledge graph; Weaviate doesn’t claim otherwise. See vector database vs. knowledge graph for agent memory for that tradeoff.
Vectorizer modules
Permalink to “Vectorizer modules”Each collection’s vectorizer is set once, at creation, and can’t be swapped without re-indexing. It connects to an external embedding service, OpenAI, Cohere, Google, or HuggingFace among them, converting text or other modalities into the embeddings Weaviate stores, the same step every transformer-based vector database depends on. Generative modules extend this further, letting a query call an LLM directly against retrieved objects, sometimes called RAG inside the database rather than around it.
Underneath, Weaviate indexes with HNSW, the same approximate-nearest-neighbor algorithm Qdrant and Pinecone use. HNSW isn’t what makes Weaviate different; what differs is what sits around the index, the schema and the modules, and how a query searches it.
What is hybrid search in Weaviate?
Permalink to “What is hybrid search in Weaviate?”Hybrid search is the mechanism Weaviate leans on hardest. A query runs BM25 keyword search and vector similarity search in parallel, then fuses both into one ranked list, per Weaviate’s hybrid search documentation. An alpha parameter controls the blend, pure keyword (0) to pure vector (1), the same tradeoff covered generally in semantic search vs. keyword search.
| Algorithm | How it ranks | Status |
|---|---|---|
| Ranked Fusion | Combines results by ranking position, not score | Legacy |
| Relative Score Fusion | Combines results by normalized score, required for autocut |
Default since v1.24 |
Pinecone’s own FAQ calls its hybrid support less central than at some peers; Weaviate treats the same mechanism as its headline feature, distinct from hybrid RAG, which fuses dense and sparse retrieval across a broader pipeline, not one query. A 2026 comparison of nine vector databases by MarkTechPost singles Weaviate out as the field’s hybrid search champion, a reputation earned by making the fusion native rather than bolted on.
Whether what got retrieved deserves to be there is a separate question, and one this page comes back to.
Is your data estate actually AI-ready?
Run the Context Gap Calculator to see how much of what feeds your retrieval pipeline, hybrid search included, is certified, current, and actually safe to index.
Run the Context Gap CalculatorWhat deployment options does Weaviate offer?
Permalink to “What deployment options does Weaviate offer?”Deployment is where Weaviate’s identity diverges most from a managed-only vector database. Three paths exist, per Weaviate’s deployment documentation:
| Option | What it is | Tradeoff |
|---|---|---|
| Self-hosted | Docker or Kubernetes, on your own infrastructure | Free and open-source; you own sharding, scaling, and upgrades |
| Weaviate Cloud | Managed, across Free, Flex, and Premium tiers | No infrastructure to run; you pay for that |
| Embedded | Experimental, runs inside a client process | Convenient for prototyping, not recommended for production |
That table is the direct structural answer to a question Pinecone’s own honest-limitations section leads with: there is no self-hosted or on-premises option. Weaviate’s answer to the same question is the opposite, a genuinely different starting point for a team deciding what it wants to own.
Weaviate Cloud’s current tiers, per Weaviate’s own pricing page, replaced older Serverless/Enterprise naming: a Free tier that’s always free up to 100,000 objects, Flex starting at a $45 monthly minimum, and Premium starting at $400 monthly on a prepaid contract with dedicated infrastructure.
Whichever path a team picks, the decision is reversible in a way a closed system’s isn’t: the same open-source core runs underneath both, so migrating between them means changing operators, not re-architecting.
Where does Weaviate fit in the AI stack?
Permalink to “Where does Weaviate fit in the AI stack?”Most vector-database explainers skip half of this question: not just what Weaviate does, but where it sits relative to everything else an AI system needs.
| Position | What sits there | Relationship to Weaviate |
|---|---|---|
| Upstream | Embedding models (OpenAI, Cohere, HuggingFace) | Produce the vectors Weaviate stores |
| Weaviate’s layer | Storage, hybrid search, increasingly, agentic routing | Stores and retrieves; Query Agent routes across it |
| Alongside | Orchestration frameworks (LangChain, LangGraph, LlamaIndex) | Call Weaviate as a retriever or vector-store tool |
| Above | A governed context layer | Decides what should have been embedded in the first place |
Weaviate is a standard partner integration in both major orchestration ecosystems: langchain-weaviate wraps it as a retriever inside LangChain, the same retrieval-layer role it plays in the broader retrieval orchestration agentic AI depends on: orchestration decides what an agent does next, not what it’s allowed to retrieve.
More recently, Weaviate has pushed further up that stack. Its Query Agent reached general availability in September 2025, routing natural-language questions across collections, decomposing complex queries and reranking results before answering. A companion Transformation Agent augments existing objects with generative models. As memory needs grow past one collection, this overlaps with what agentic AI memory and multi-agent scaling already require: consistency across many concurrent readers and writers.
Routing intelligence isn’t certification, and the closing sections come back to that gap.
How much does Weaviate cost?
Permalink to “How much does Weaviate cost?”Two cost models mirror the two main deployment paths. Self-hosting is free and open-source; the cost shows up as infrastructure and engineering time, work Weaviate Cloud otherwise absorbs. Weaviate Cloud’s pricing follows the same Free, Flex, and Premium tiers covered in the deployment section above.
A headline number ages fast; Weaviate’s own pricing page is the source to check before committing budget. The real comparison is total cost of ownership over 12 to 18 months, not today’s Free-versus-Flex math. A team with existing Kubernetes expertise may find self-hosted materially cheaper; a team without it usually finds the ops time costs more than the subscription would have. Neither path answers whether the content indexed under either model was worth indexing, a context window problem that sits above pricing entirely.
Know where your data stands
Take the Context Maturity Assessment to see how ready your data estate is before budgeting for either deployment path.
Take the Maturity AssessmentWhat are Weaviate’s honest limitations?
Permalink to “What are Weaviate’s honest limitations?”Weaviate’s flexibility comes with real tradeoffs.
Operationally, self-hosting means owning sharding, scaling, and schema design decisions Weaviate Cloud abstracts away, and practitioners consistently report a real learning curve here. Aggregated review signal from G2 and AWS Marketplace also points to occasional SDK feature lag behind Weaviate’s core Go engine and latency concerns at scale under some configurations, a directional pattern. Retrieval quality also depends on decisions Weaviate has no opinion on, like chunking strategy, upstream of the index entirely. Cost at scale is a tradeoff every managed vector database shares, not unique to Weaviate.
The deeper limitation is tied to Weaviate’s own newest feature. The Query Agent routes a question to the right collection with real sophistication; nothing checks whether that collection’s contents were ever certified for AI use, whether a document has gone stale, or whether a business term means what the business thinks it means. Multi-tenancy isolates tenants into dedicated shards since v1.20; it doesn’t certify what’s inside them. This is the same upstream cause behind why AI agents fail in production and the broader RAG accuracy problems that have little to do with which vector database sits underneath.
None of this is a knock on Weaviate as a retrieval engine; it’s a different, upstream problem no vector database sets out to solve.
How does Weaviate compare to other vector databases?
Permalink to “How does Weaviate compare to other vector databases?”The right vector database depends on deployment control, existing infrastructure, and how much operational work a team wants to own. Weaviate’s open-source, self-hostable identity sets it apart from Pinecone’s managed-only model; Milvus, Qdrant, and ChromaDB occupy similar open-source territory, each with its own tradeoffs this page won’t relitigate. A team facing a knowledge-graph-shaped problem, not a retrieval one, should look at context graphs instead of stretching Weaviate’s cross-references to do that job.
Atlan covers the full landscape in Top vector databases for enterprise AI, an eight-way comparison; readers starting from fundamentals should begin with What is a vector database? instead. This page’s job was narrower: what Weaviate is, how its architecture and hybrid search work, and where its real limits sit, with semantic search implementation, knowledge base construction, and advanced RAG techniques covered elsewhere.
See what governed retrieval looks like
Walk through how the Context Layer ROI Calculator estimates the cost of ungoverned retrieval versus a certified, lineage-tracked pipeline, whichever vector database sits underneath.
Try the ROI CalculatorWhat a governed context layer adds that Weaviate doesn’t
Permalink to “What a governed context layer adds that Weaviate doesn’t”Weaviate answers a narrow question well: given this query, what’s closest in what’s already indexed, increasingly with the Query Agent adding intelligence about which collection to ask. It has no mechanism for the question underneath: was this data ever certified for AI use, or safe for a model to see at all.
Stack AI chose Weaviate over Pinecone for cost and deployment flexibility; its CEO, Antoni Rosinol, put it in people terms: “The biggest benefit of using Weaviate isn’t just the technology – it’s the team behind it.” Morningstar built its “Mo” research assistant on Weaviate. Both are proof of retrieval quality; neither describes a mechanism for certification, classification, or lineage.
Atlan sits upstream of that gap, drawing on the same data catalog and systems of semantics discipline: certification so only owner-approved data enters the embedding pipeline, sensitivity classification blocking PII before it becomes a vector, freshness triggers tying a source update to a re-embed signal, and lineage tracing every vector back to its source table. Atlan’s MCP Server, through the Model Context Protocol, lets an agent querying Weaviate check whether what it retrieved was ever supposed to be there. A semantic layer closes the gap between “semantically similar” and “means what the business thinks it means.”
The enterprise context layer, built on Atlan’s Enterprise Data Graph, sits above deployment flexibility and hybrid search entirely, answering a question neither touches: not how fast retrieval runs, but whether it was retrieval of something trustworthy to begin with. Context engineering means building that check in from the start, not finding its absence after an agent already acted on something it shouldn’t have. Teams that treat implementing an enterprise context layer as a parallel track don’t rebuild the pipeline six months in.
Weaviate is honest about retrieval and silent about trust
Permalink to “Weaviate is honest about retrieval and silent about trust”Weaviate’s genuine strengths, open-source flexibility, native hybrid search, and an increasingly agentic layer on top, don’t answer whether what gets retrieved deserves to be trusted. That’s a context problem, not a retrieval one: certifying, classifying, and tracing data was never the job any vector database signed up for. Solving deployment flexibility and hybrid search precision is a real achievement. It isn’t this one.
FAQs about Weaviate
Permalink to “FAQs about Weaviate”1. What is Weaviate used for?
Permalink to “1. What is Weaviate used for?”Weaviate is used to store and retrieve embeddings for AI applications, most commonly retrieval-augmented generation, AI agent memory, and semantic search. Its native hybrid search suits teams wanting both keyword precision and semantic recall from a single query, self-hosted or through Weaviate Cloud.
2. Is Weaviate open source?
Permalink to “2. Is Weaviate open source?”Yes. Weaviate’s core is open-source under the Apache 2.0 license, free to self-host on Docker or Kubernetes. Weaviate Cloud is the company’s managed alternative, priced across free, entry, and enterprise tiers, but the same code powers both.
3. How does Weaviate differ from Pinecone?
Permalink to “3. How does Weaviate differ from Pinecone?”Weaviate is open-source and deployment-flexible, self-hosted or managed; Pinecone is closed-source and managed-only, with no self-hosting option. Weaviate treats hybrid search, fusing keyword and vector matching, as a core feature, while Pinecone’s own docs describe its hybrid support as less central than at some peers.
4. What is hybrid search in Weaviate?
Permalink to “4. What is hybrid search in Weaviate?”Hybrid search in Weaviate runs a BM25 keyword search and a vector similarity search in parallel, then fuses the results into one ranked list. An alpha parameter, from 0 (pure keyword) to 1 (pure vector), controls the blend. Relative Score Fusion has been the default algorithm since Weaviate v1.24.
5. Can I self-host Weaviate?
Permalink to “5. Can I self-host Weaviate?”Yes. Weaviate’s Apache-2.0 core runs anywhere Docker or Kubernetes runs, on your own infrastructure or any cloud provider, at no licensing cost. Self-hosting means taking on sharding, scaling, and schema design decisions that Weaviate Cloud otherwise manages, a real operational tradeoff worth budgeting for.
6. Does Weaviate support multi-tenancy?
Permalink to “6. Does Weaviate support multi-tenancy?”Yes. Since v1.20, Weaviate’s multi-tenancy assigns each tenant a dedicated shard within a collection, giving logical and physical isolation rather than a metadata-filter-based separation. That distinction matters for workloads needing hard isolation between customers or business units, not just a filtered view of shared data.
7. What is the Weaviate Query Agent?
Permalink to “7. What is the Weaviate Query Agent?”The Query Agent is Weaviate’s own agentic feature, reaching general availability in September 2025. It routes a natural-language question across multiple collections, decomposing complex queries and reranking results automatically. It improves retrieval routing, but has no concept of whether a collection’s contents were ever certified for AI use.
Sources
Permalink to “Sources”- Weaviate Raises $50 Million Series B Funding, PR Newswire
- weaviate/weaviate repository, GitHub
- Revolutionizing AI Search with Weaviate: An Interview with CEO Bob van Luijt, Microsoft Agent Framework Devblog
- Managing Collections, Weaviate Documentation
- Hybrid Search, Weaviate Documentation
- Best Vector Databases in 2026: Pricing, Scale Limits, and Architecture Tradeoffs Across Nine Leading Systems, MarkTechPost
- Deploying Weaviate, Weaviate Documentation
- Weaviate Pricing, Weaviate
- Query Agent, Now Generally Available, Weaviate Blog
- Weaviate Multi-Tenancy Architecture Explained, Weaviate Blog
- Case Study: Stack AI, Weaviate
- Case Study: Morningstar, Weaviate
- Forecast: Database Management Systems, Worldwide, Gartner
- Vector Database Market Size, Share & Industry Analysis, Fortune Business Insights
