Weaviate

Weaviate is an open-source vector database that stores both data objects and their vector embeddings, enabling a combination of vector similarity search with structured filtering, keyword retrieval, and integrated generative search. Written in Go and licensed under BSD-3-Clause, the system is designed for speed and reliability in artificial intelligence applications. The project began as an open-source initiative by Bob van Luijt in March 2016 and was later commercialized by SeMI Technologies, the Amsterdam-based company that he co-founded with Etienne Dilocker in 2019, after entering a startup accelerator at the end of 2018. SeMI Technologies rebranded to Weaviate B.V. in January 2023 ^[1][2][3]. As of November 2026, the open-source project had close to 17,000 GitHub stars, and the company reported more than 20 million open-source downloads and thousands of customers; in early 2026 its website also cited a community of over 50,000 AI builders ^[4][5].

Who created Weaviate and when?

The Weaviate project began in March 2016, when Dutch technology entrepreneur Bob van Luijt started experimenting with the idea of a database where semantic relationships were a first-class citizen. He was working through a strategic design consultancy called Kubrickology, and his early thinking was shaped by two influences: the GloVe paper on word embeddings, which he encountered in 2015, and Google's Weave and Brillo "things" framework, which he first saw at the Ubiquity Conference in San Francisco in January 2016 ^[3][6].

In September 2017, van Luijt published a blog post connecting Internet of Things concepts with the semantic web, sketching the framework that would later become Weaviate. By the end of 2018, he had entered a startup accelerator in the Netherlands and assembled the founding team that would become SeMI Technologies. The company name stood for Semantic Machine Insights. The original Weaviate codebase had been more of a traditional knowledge graph, but during the accelerator phase the team pivoted toward semantic search powered by vector embeddings, what they called the "Weaviate Search Graph" ^[3][6].

Etienne Dilocker joined as co-founder and Chief Technology Officer. Dilocker is a German engineer whose public profile describes his focus as Go, database development, cloud-native technology, and performance programming, with an emphasis on site reliability engineering ^[8].

The 2022 Series A announcement named Micha Verhagen as a third founder, serving as chief operating officer. The same announcement said SeMI Technologies was originally spun out of ING Labs, the innovation arm of Dutch bank ING Group, whose venture arm ING Ventures invested in the seed round ^[12].

Version 1.0.0 of Weaviate was released on 14 January 2021. This release introduced the modular API that allows the database to plug into different embedding providers and other extensions. By that point the project had already moved away from being a niche knowledge graph and was positioning itself as a dedicated vector database for the emerging generative-AI era ^[9].

In January 2023, the company changed its legal name from SeMI Technologies to Weaviate B.V. According to a press release at the time, the open-source product had become significantly better known than the corporate entity, so the team decided to consolidate under the Weaviate brand ^[2].

How much funding has Weaviate raised?

Weaviate has raised approximately $67.6 million across three publicly disclosed funding rounds. The company has remained at the Series B stage as of early 2026 and has not announced any subsequent priced rounds ^[10][11].

The $1.6 million seed round in August 2020 was led by Zetta Venture Partners with ING Ventures participating, and was not announced until the Series A in 2022 ^[12]. The $16 million Series A in February 2022 was co-led by Cortical Ventures and New Enterprise Associates (NEA), with Zetta and ING Ventures continuing as participants. The Series A press release was headlined as highlighting "a new wave of AI-first database tech" ^[12][13].

The Series B closed on 21 April 2023 at $50 million, led by Index Ventures and joined by Battery Ventures alongside the prior investors. The round was driven by demand from teams building retrieval-augmented generation systems on top of large language models. Announcing the round, co-founder and CEO Bob van Luijt framed the product's positioning directly: "The Weaviate vector database is used as core infrastructure in the emerging AI-native ecosystem" ^[11]. Index Ventures partner Erin Price-Wright, who led the investment, added that "Weaviate's vector database and search engine provides a critical piece of infrastructure that's helping to drive a massive AI platform shift" ^[11]. Capital from the Series B has been used to expand the engineering team, build out Weaviate Cloud, and grow commercial operations across North America and Europe ^[11][14].

Third-party estimates compiled by GetLatka put Weaviate's annual revenue at around $12.3 million in October 2024, with about 104 employees in December 2024, suggesting strong commercial traction without an immediate need for additional priced rounds ^[15].

headquarters and team

Weaviate is headquartered at Prinsengracht 769A in Amsterdam, Netherlands, the same canal-side district where the founding team began. The company is structured as remote-first, with engineers, researchers, and commercial staff distributed across Europe, North America, and other regions. Public estimates put headcount at roughly 90 to 105 people through 2024 and 2025 ^[15][16].

Key leadership disclosed publicly includes:

The company describes its values as Be Kind, Work Together as One, Strive for Excellence, Encourage Transparency, and Inspire Trust ^[16].

How does Weaviate's architecture work?

Weaviate's architecture is designed to handle multiple search paradigms (vector, keyword, and hybrid) within a single system. The database is written in Go, which the team chose for its concurrency model, low memory overhead, and strong tooling around binary builds. Roughly 97 percent of the codebase is Go, with a small amount of Python tooling for tests and developer scripts ^[4].

A Weaviate node combines several subsystems: a storage engine based on a custom log-structured merge-tree (LSM-tree), an inverted index for keyword search, one or more vector indexes per collection, a schema and metadata service, and a multi-protocol API surface (REST, gRPC, and GraphQL). Cluster coordination uses the Raft consensus algorithm, while object data is replicated using a leaderless eventually consistent model ^[17][18].

HNSW index

Weaviate uses HNSW (Hierarchical Navigable Small World) as its primary vector index algorithm. HNSW is a graph-based approach that searches vectors by navigating through multiple layers, moving from coarse approximations to fine ones. Its complexity grows logarithmically rather than linearly with the dataset size, which makes it effective even at billions of vectors ^[19].

Each named vector in Weaviate maintains its own vector index, which can be either an HNSW graph or a flat index. The HNSW graph is held in memory for fast access, with commit logs and snapshots used to restore the structure after a restart. From version 1.31, Weaviate added HNSW snapshotting, which produces periodic on-disk snapshots that can be loaded directly at startup. According to the release notes, this can reduce startup time for large indexes by approximately 10 to 15 times compared with replaying the write-ahead log ^[9][20].

In single-instance mode, Weaviate's in-memory HNSW index handles millions of vectors with sub-second response times. For larger datasets, cluster mode distributes data across nodes with sharding and replication, enabling horizontal scaling to billions of data points ^[19].

Weaviate exposes several HNSW tuning parameters that allow developers to optimize the tradeoff between recall, speed, and memory:

The flat index option is useful for small collections or multi-tenant environments where each tenant has a relatively small dataset. Instead of building and maintaining an HNSW graph, flat indexing stores vectors in a simple array and performs brute-force search, which is faster for small collections due to lower overhead ^[19].

vector quantization

Weaviate supports several quantization techniques for compressing vectors and reducing memory consumption. Quantization is configured per HNSW (or flat) index and can be combined with rescoring, where the database re-ranks the top candidates using their full-precision vectors to recover most of the lost recall ^[21].

Rotational quantization (RQ) was introduced in version 1.32 (July 2025), and from version 1.33 8-bit RQ became the default compression for new collections. A 1-bit RQ variant, providing extreme compression rates while preserving most of the search quality, became a preview feature in version 1.33 (October 2025). Each quantization mode preserves a copy of the uncompressed vectors so that rescoring can refine the final top-k results ^[22][23].

GPU-accelerated indexing

Through a partnership with NVIDIA, Weaviate supports GPU-accelerated index building using the cuVS library. The CAGRA algorithm builds indexes on the GPU, then converts them to HNSW format for cost-effective CPU-based query serving. This approach speeds up index construction while keeping query costs low ^[24].

inverted index for keyword search

In addition to the HNSW vector index, Weaviate maintains an inverted index based on BM25F scoring for keyword search. The BM25F algorithm extends the standard BM25 scoring function with field-level weighting, so different properties of an object (such as title versus body text) can contribute differently to keyword relevance scores. This inverted index powers Weaviate's keyword search and is also used as one component of hybrid search ^[25][26].

From version 1.30, Weaviate replaced the previous BM25 implementation with BlockMax WAND, an algorithm that allows the database to skip large blocks of postings during scoring. In Weaviate's internal benchmarks, BlockMax WAND reduced BM25 query latency by an order of magnitude on large corpora compared with the previous traversal strategy ^[27].

What is Weaviate hybrid search?

Weaviate's hybrid search combines dense vector similarity with BM25 keyword matching in a single native API call. Combining the two signals is particularly relevant for retrieval-augmented generation workloads, where recall directly affects the quality of generated answers ^[25][26].

The system fuses dense vector embeddings with sparse BM25 lexical matching, and developers can control the weighting between the two methods.

Weaviate offers two fusion algorithms for combining vector and keyword results:

The alpha parameter controls the balance between vector search (alpha = 1.0) and keyword search (alpha = 0.0). Setting alpha to 0.5 weights both methods equally. The default value is 0.75, which favors vector search slightly ^[26].

multi-vector embeddings and MUVERA

From version 1.31 (June 2025), Weaviate added support for multi-vector embeddings using MUVERA encoding. Multi-vector models such as ColBERT represent each document as a set of token-level vectors rather than one pooled vector, which can improve retrieval accuracy at the cost of storage. MUVERA provides a fixed-dimension single-vector representation that approximates the late-interaction scoring used by ColBERT, allowing Weaviate to plug multi-vector models into its standard HNSW pipeline without exotic data structures ^[20].

replication and consistency

From version 1.25 onward, Weaviate uses the Raft consensus algorithm for cluster metadata, including schema operations, role-based access control changes, and tenant lifecycle events. Raft is implemented using the HashiCorp Raft library; one node is elected leader, and metadata changes are committed once a quorum of nodes acknowledges them. This was a significant change from earlier versions, which had used a simpler gossip-style protocol that could not safely support concurrent schema operations ^[17].

Object data replication uses a leaderless, eventually consistent model with tunable consistency levels (ONE, QUORUM, ALL) at read and write time. Async replication, asynchronous shard replica movement between nodes, and rebalancing capabilities have all been added across the 1.25 through 1.32 release series, gradually maturing Weaviate into a distributed system suitable for production workloads at scale ^[17][22].

module system

Weaviate's module system is one of its defining architectural features. Modules extend the database with additional capabilities at various stages of the data pipeline: vectorization (generating embeddings from raw data), generative AI (producing text from search results), reranking (refining result order), and reference resolution (loading data from external sources).

Modules are loaded at server startup via configuration. In Docker deployments, modules are specified as environment variables. In Kubernetes, they are configured in the Helm chart values. Weaviate Cloud instances come with a default set of modules pre-configured ^[29].

vectorizer modules

Vectorizer modules automatically generate embeddings when objects are inserted into Weaviate. Instead of computing embeddings externally and uploading them, users configure a vectorizer module on a collection and Weaviate handles embedding generation transparently.

Users can also import pre-computed vector embeddings directly, bypassing the module system entirely. This is the recommended path for users who already maintain a centralized embedding pipeline outside the database ^[29].

generative modules

Generative modules connect Weaviate to large language models for retrieval-augmented generation (RAG) directly within the database.

A generative search query in Weaviate consists of two parts: a search query (vector, keyword, or hybrid) and a prompt for the language model. Weaviate first retrieves relevant objects, then passes both the search results and the prompt to the configured generative model, returning the generated response alongside the original search results ^[30].

reranker modules

Reranker modules apply a second-pass ranking model after the initial retrieval step. Cross-encoder reranking models score each retrieved result against the original query, which typically produces more accurate relevance judgments than the initial bi-encoder similarity search. Available reranker modules include reranker-cohere, reranker-voyageai, reranker-jinaai, reranker-contextual, and reranker-transformers ^[29].

schema and collection definition

Weaviate organizes data into collections (previously called "classes"). Each collection defines a schema that specifies the properties of its objects, the vectorizer to use, the generative module (if any), and index configuration.

A collection definition includes:

• Properties: Named fields with data types (text, int, number, boolean, date, object, geoCoordinates, phoneNumber, blob, uuid, and arrays of these types).
• Vectorizer configuration: Which vectorizer module to use and which properties to vectorize.
• Generative module configuration: Which LLM module to use for RAG queries.
• Vector index configuration: HNSW or flat index, with tuning parameters and quantization options.
• Inverted index configuration: Settings for keyword search, including BM25 parameters and stopword configuration.
• Replication configuration: Number of replicas for the collection.
• Multi-tenancy configuration: Whether to enable tenant isolation.

Weaviate also supports auto-schema, which is enabled by default. When auto-schema is active, Weaviate infers collection definitions from the data being inserted, automatically detecting property names and types. This is convenient for prototyping but should be disabled in production for predictable behavior ^[31].

Cross-references allow linking objects across collections. For example, an Article collection might reference objects in an Author collection, enabling graph-like traversals in queries.

From version 1.32, Weaviate added collection aliases, which let operators point an alias name at different underlying collections. This makes zero-downtime migrations practical: a new collection is built behind a fresh name, the alias is swapped to it once the data is ready, and the old collection can be dropped without changing client code ^[22].

key features

multi-tenancy

Weaviate implements native multi-tenancy with one shard per tenant, dynamic resource management, and true data isolation. This design means each tenant's data is physically separated, not just logically filtered. Recent updates introduced tenant offloading to S3 cloud storage and renamed the tenant activity statuses from HOT/COLD to ACTIVE/INACTIVE for clarity ^[32].

Multi-tenancy is useful for SaaS applications where each customer needs their own isolated dataset but the application operator does not want to manage separate database instances for each customer.

Weaviate's multi-tenancy implementation supports three tenant states:

This tiered approach allows operators to manage costs by offloading inactive tenants to cheaper storage while keeping frequently accessed tenants in memory for low-latency queries. Reference customers such as Instabase operate clusters with more than 50,000 tenants, illustrating that the design holds up at significant scale ^[32][33].

GraphQL, REST, and gRPC APIs

Weaviate exposes three APIs: REST, GraphQL, and gRPC. The GraphQL API was long distinctive among vector databases, since most competitors offer only REST or gRPC interfaces, but Weaviate has since deprecated it: as of November 2026 its documentation says the GraphQL API will be switched off on Weaviate Cloud on May 1, 2027, and the official client libraries use gRPC instead ^[34]. GraphQL allows clients to specify exactly which fields they need, reducing over-fetching and making it easier to build flexible query interfaces ^[34].

A typical Weaviate GraphQL query can combine vector search, keyword filters, and property selection in a single request:

{
  Get {
    Article(
      hybrid: {
        query: "machine learning applications"
        alpha: 0.75
      }
      limit: 5
    ) {
      title
      content
      _additional {
        score
        distance
      }
    }
  }
}

The alpha parameter controls the balance between vector search (1.0) and keyword search (0.0).

The gRPC interface, introduced incrementally between version 1.19 and version 1.23.7, is the preferred protocol for high-throughput workloads. Internal benchmarks comparing the gRPC and REST/GraphQL paths on identical hardware showed query latency reductions of 40 to 70 percent and import-time reductions of close to 50 percent on the DBPedia benchmark dataset ^[35]. The gRPC API uses HTTP/2 and Protocol Buffers, which produce smaller, faster-to-parse payloads than JSON over HTTP/1.1.

A short example using the v4 Python client illustrates a hybrid query:

import weaviate
from weaviate.classes.query import HybridFusion

client = weaviate.connect_to_local()
articles = client.collections.get("Article")

results = articles.query.hybrid(
    query="vector databases for RAG",
    alpha=0.75,
    fusion_type=HybridFusion.RELATIVE_SCORE,
    limit=5,
)

for obj in results.objects:
    print(obj.properties["title"], obj.metadata.score)

client.close()

generative search (RAG)

Weaviate includes built-in generative search capabilities, allowing users to perform retrieval-augmented generation directly within the database. After retrieving relevant objects through vector or hybrid search, Weaviate can pass those results to a configured language model (such as OpenAI's GPT-4, Anthropic's Claude, or Cohere's models) to generate answers, summaries, or transformations. This eliminates the need for a separate orchestration layer for basic RAG use cases ^[30].

Generative search supports two modes:

• Single-prompt: A prompt is applied to each individual search result. For example, summarizing each retrieved document.
• Grouped-task: All search results are passed together to the model in a single prompt. For example, generating a comprehensive answer that synthesizes information from multiple retrieved documents.

reranking

Integrated reranking modules let users apply a second-pass ranking model after the initial retrieval step. Reranking models score each retrieved result against the original query using a cross-encoder, which typically produces more accurate relevance judgments than the initial bi-encoder similarity search.

named vectors

Weaviate supports multiple named vectors per object, allowing a single object to have separate embeddings for different properties or different embedding models. For example, a product listing might have one vector for its title (embedded with a lightweight model) and another for its description (embedded with a more powerful model). Queries can target specific named vectors, enabling flexible multi-modal and multi-representation search strategies.

authentication, RBAC, and security

Weaviate supports API-key, OIDC, and anonymous authentication modes, configured via environment variables on each node. From the 1.29/1.30 release series, the database includes a built-in role-based access control (RBAC) system, with predefined roles for root and viewer plus user-defined roles that pin down permissions at the level of individual collections, tenants, and operations ^[36].

From version 1.34, observability capabilities expanded with more than 30 new monitoring metrics, covering LSM bucket reads and writes, write-ahead log recovery, memtable flushing, and asynchronous replication. These metrics are exposed in Prometheus format and feed into Weaviate Cloud's standard monitoring dashboards ^[37].

How can you deploy Weaviate?

Weaviate offers several ways to run the database, from fully self-managed to fully hosted. The core engine is identical across deployment modes ^[38][39].

Weaviate restructured its pricing in October 2025, replacing earlier per-dimension billing with three usage-based dimensions (data, performance, and AI features) plus a $45/month minimum to cover baseline cluster costs. As of November 2026, Weaviate Cloud's published plans are Free, Flex, and Premium ^[60].

As described on Weaviate's former BYOC page, the BYOC offering was targeted at enterprises with data-residency, regulatory, or networking constraints. The cluster runs inside the customer's AWS, GCP, or Azure VPC on managed Kubernetes, while Weaviate handles application-level security, configuration, upgrades, patches, and 24/7 monitoring. This design separates the control plane (Weaviate's responsibility) from the data plane (customer's environment) ^[38].

Weaviate Cloud also runs HIPAA-eligible Enterprise Cloud workloads on AWS, with parallel work in progress for Azure and GCP. The same engine powers integrations with the AWS Marketplace, where users can deploy Weaviate as a containerized cluster inside their AWS tenant.

Weaviate Embeddings

Weaviate Embeddings, launched in December 2024, is a managed embedding service that runs inside Weaviate Cloud. The service offers GPU-backed inference for both open-source and proprietary models, removing the need for users to call external APIs or operate their own embedding infrastructure ^[41][42].

The service launched in preview with Snowflake's open-source Arctic-Embed model. As of November 2026 it offers two Snowflake Arctic text models, snowflake-arctic-embed-m-v1.5 (English, best for texts under 512 tokens) and snowflake-arctic-embed-l-v2.0 (multilingual, up to 8192 tokens), plus the multimodal ModernVBERT/colmodernvbert model for document-image retrieval ^[42][61]. Pricing is consumption-based, and the service has no hard cap on embeddings per second, making it suitable for production-scale ingestion. Additional models and modalities have been added on a rolling basis since 2025 ^[41][42].

Weaviate Agents

In March 2025, Weaviate introduced a new product line called Weaviate Agents: pre-built agentic services that ship with Weaviate Cloud. Three agents were released, but only the Query Agent reached general availability; by mid-2026 Weaviate had sunset the Transformation and Personalization agents in favor of the Query Agent and its Engram memory service ^{[43][44][62][63]}.

The Query Agent reads a Weaviate cluster's schema, decides which collections to query, generates the appropriate vector or aggregation query, and returns a natural-language answer with citations to the underlying objects. It became generally available in September 2025 ^[45].

In February 2026, Weaviate also announced Agent Skills, a developer toolkit that helps coding agents (such as those built on the Model Context Protocol) understand Weaviate APIs and write correct queries against them ^[46].

Verba

Verba was Weaviate's open-source RAG reference application. The repository, hosted on GitHub at weaviate/Verba, provides a modular chatbot interface that ingests documents from sources such as PDFs (via UnstructuredIO), GitHub repositories, and Markdown files, then answers questions using Weaviate as the retrieval back-end and a configurable LLM as the generation step. The project accumulated about 7,700 GitHub stars and was used as a starting point for self-hosted RAG demos, but Weaviate discontinued it and archived the repository on 8 June 2026; it no longer receives updates, bug fixes, or security patches ^[47][48].

Verba supports four deployment modes: a fully embedded mode using Weaviate Embedded, a Docker mode, a connection to an existing Weaviate Cloud cluster, and a custom URL mode pointing at any reachable Weaviate instance. The default model stack is intentionally swappable: SentenceTransformers for embeddings, OpenAI or Ollama for generation, and either Weaviate Cloud or local Weaviate for storage.

release history

Weaviate ships approximately one minor release every one to two months. The table below highlights selected releases that introduced major capabilities. Weaviate's stated support policy is to maintain bug fixes and security patches for the latest three minor versions ^{[9][20][22][23][37][64]}.

performance benchmarks

Weaviate publishes benchmark results for its search modes. In September 2025, the team benchmarked the Query Agent's Search Mode against standard hybrid search across 12 information retrieval datasets from BEIR, LoTTe, and BRIGHT, as well as WixQA and EnronQA.

Key findings from these benchmarks include:

Throughput and latency depend heavily on dataset size, dimensionality, and hardware configuration. For ingestion, the move from REST to gRPC roughly halved the time to insert the 1 million records of the DBPedia benchmark dataset, from over 42 minutes to about 23 minutes on the same hardware ^[35].

How does Weaviate differ from other vector databases?

Weaviate is most often compared with Pinecone, Qdrant, Chroma, and Milvus. The competitive picture is shaped by license model (open source versus proprietary), deployment options, hybrid search capabilities, and the level of integration with embedding and generative providers ^[50][51].

versus Pinecone

Pinecone tends to win on setup simplicity and consistent low-latency performance for pure vector search workloads. Weaviate tends to win on flexibility, hybrid search quality, and cost control through self-hosting options. For workloads where hybrid search is central to the application, Weaviate's native BM25 + vector fusion in a single API call is more efficient than Pinecone's approach of maintaining separate sparse and dense indexes ^[50].

A published Pinecone customer benchmark on Dedicated Read Nodes reported 5,700 QPS at a P99 latency of 60ms on 1.4 billion vectors; the cited comparison gives no equivalent Weaviate throughput figure. Direct comparisons are difficult since the hardware, dataset sizes, and query patterns differ across benchmarks ^[50].

versus Qdrant

Qdrant emphasizes raw performance, especially around payload-heavy filtered search, and is often praised for its memory footprint due to its Rust implementation. Weaviate emphasizes a richer feature surface (modules, agents, Weaviate Embeddings, generative search). Both are viable open-source options at production scale, and many teams pick between them based on whether they prefer Go or Rust on their infrastructure team ^[50][51].

versus Milvus

Milvus, maintained by Zilliz under the Apache 2.0 license, is another open-source vector database focused on raw performance and a broad menu of index types (HNSW, IVF, DiskANN, GPU indexes). Compared with Milvus, Weaviate ships with a thinner index menu (HNSW, flat, dynamic, and the disk-based HFresh index added in 2026) but a richer module catalog and integrated generative search. Milvus tends to perform better on extremely large pure-vector workloads with custom index choices, while Weaviate tends to be easier to integrate with embedding and LLM providers out of the box ^[51].

versus Chroma and pgvector

Chroma is a developer-friendly embedding database aimed mostly at prototyping; it does not target the same scale or feature set as Weaviate. pgvector is a PostgreSQL extension that adds vector indexing to an existing relational database; it is a strong choice when an application already uses PostgreSQL and needs only modest vector-search functionality. Weaviate occupies a middle ground: more capable than Chroma, more specialized than pgvector, and open-source unlike Pinecone ^[51].

Who uses Weaviate?

Weaviate publishes case studies on its website covering production deployments. Notable users include ^{[5][33][52][53]}:

In December 2025, AWS named Weaviate its Rising Star Technology Partner of the Year for the Benelux region in its regional 2025 EMEA Partners of the Year awards, citing its use of Amazon Bedrock and SageMaker for generative AI infrastructure and search ^[54].

ecosystem and community

The Weaviate open-source project had close to 17,000 GitHub stars as of November 2026, and the company reports more than 20 million open-source downloads and thousands of customers; in early 2026 it also cited a community of more than 50,000 AI builders ^[4][5].

Weaviate provides official client libraries for Python, JavaScript/TypeScript, Go, Java, and C#/.NET. The Python client is the most popular, with active development tracked in its changelog ^[55].

Integrations exist with LangChain, LlamaIndex, Semantic Kernel, Haystack, Dify, Embedchain, and other AI orchestration frameworks. These integrations allow developers to use Weaviate as the vector store component in larger machine learning pipelines.

The Weaviate community includes an active forum, a Slack workspace with thousands of members, and regular community calls. Engagement levels are high, with the company reporting more than 200 messages per week across its open Discourse forum and GitHub repositories. The Weaviate Hero program recognizes members who contribute through speaking, blogging, code, and community moderation ^[56][57].

The company also runs Weaviate Academy, a free educational platform with structured courses on using the database, from zero-to-MVP guides to advanced performance optimization tutorials, and the Weaviate World Tour series of in-person workshops, conferences, and hackathons across Europe and North America ^[29][57].

current state (2025-2026)

By May 2026, Weaviate continues to develop as both an open-source project and a commercial cloud service. The company has focused on several areas: improving multi-tenancy efficiency with features like tenant offloading to S3, GPU-accelerated index building through the NVIDIA partnership, native multi-vector embeddings with MUVERA, more efficient quantization through RQ, and agentic services centered on the Query Agent (the Transformation and Personalization agents were later sunset) ^{[22][24][32][43][62][63]}.

The vector database market has become increasingly competitive, with Weaviate, Qdrant, Milvus, Chroma, and Pinecone all vying for developer adoption, and incumbents such as Oracle, Microsoft Azure (with Azure AI Search), MongoDB, and PostgreSQL (via pgvector) adding vector capabilities to their existing databases. Weaviate differentiates itself through its combination of open-source availability, native hybrid search, automatic vectorization modules, and its multi-protocol API (although its GraphQL API is now deprecated) ^[34]. The open-core business model (free self-hosted, paid cloud) gives it flexibility that purely managed competitors like Pinecone cannot match, while the managed cloud option reduces friction for teams that do not want to operate their own infrastructure ^[50][51].

Weaviate's stated direction for 2026 emphasizes deeper agentic capabilities, including reasoning workflows, broader multimodal support, model evaluation tools, and shared memory across agents. CEO Bob van Luijt has singled out "generative feedback loops", in which applications prompt the database rather than the model, as one of the developments he is most excited about in AI-native databases ^[58].

Weaviate's focus on developer experience, with features like built-in generative search, automatic vectorization, integrated agents, and BYOC deployments, reflects a broader trend in the vector database space toward reducing the amount of glue code required to build AI applications. Rather than forcing developers to stitch together separate embedding services, vector stores, and LLM orchestration layers, Weaviate aims to handle much of this within the database itself.

references

1. ^SeMI Technologies - Crunchbase Company Profile and Funding - Crunchbase
2. ^1 ^2SeMI Technologies becomes Weaviate - PR Newswire, 18 January 2023
3. ^1 ^2 ^3The History of Weaviate - Weaviate Blog, January 2021
4. ^1 ^2 ^3weaviate/weaviate on GitHub - GitHub
5. ^1 ^2 ^3The AI database developers love - Weaviate
6. ^1 ^2The History of the Weaviate Vector Search Engine - Medium / SeMI Technologies
7. Etienne Dilocker - Co-founder and CTO - Weaviate Careers
8. ^Etienne Dilocker on GitHub - GitHub
9. ^1 ^2 ^3Release Notes - Weaviate Documentation
10. ^Weaviate - Crunchbase Company Profile and Funding - Crunchbase
11. ^1 ^2 ^3 ^4Weaviate Raises $50 Million Series B Funding - PR Newswire, 21 April 2023
12. ^1 ^2 ^3SeMI Technologies $16M Series A Round Highlights a New Wave of AI-first Database Tech - PR Newswire, February 2022
13. ^SeMI Technologies' search engine opens up new ways to query your data - TechCrunch, 22 February 2022
14. ^Index Ventures Leads $50 Million Investment in AI Startup Weaviate - The Information, April 2023
15. ^1 ^2How Weaviate hit $12.3M revenue with a 104 person team in 2024 - GetLatka
16. ^1 ^2About Us - Weaviate
17. ^1 ^2 ^3Replication Architecture - Weaviate Documentation
18. ^Weaviate 1.25 Release - Weaviate Blog
19. ^1 ^2 ^3Weaviate Vector Index documentation - Weaviate Documentation
20. ^1 ^2 ^3Weaviate 1.31 Release - Weaviate Blog
21. ^Compression (Vector Quantization) - Weaviate Documentation
22. ^1 ^2 ^3 ^4 ^5Weaviate 1.32 Release - Weaviate Blog
23. ^1 ^2Weaviate 1.33 Release - Weaviate Blog
24. ^1 ^2Unleashing AI Factories: Weaviate and NVIDIA Turbocharge Vector Search - Weaviate Blog
25. ^1 ^2Hybrid Search - Weaviate Documentation
26. ^1 ^2 ^3Hybrid Search Explained - Weaviate Blog
27. ^Weaviate 1.30 Release: Runtime config, BlockMax WAND BM25 - GitHub Releases
28. Weaviate GraphQL: Python Hybrid Search Implementations 2026 - Johal.in
29. ^1 ^2 ^3 ^4Weaviate Modules documentation - Weaviate Documentation
30. ^1 ^2Generative Search documentation - Weaviate Documentation
31. ^How to define a schema - Weaviate Academy
32. ^1 ^2 ^3Rethinking Vector Search at Scale: Weaviate's Multi-Tenancy - Weaviate Blog
33. ^1 ^2Case Study - Instabase - Weaviate
34. ^1 ^2 ^3GraphQL API documentation - Weaviate Documentation
35. ^1 ^2gRPC-Driven Performance Improvements in Weaviate - Weaviate Blog
36. ^Setting up RBAC in Weaviate - Weaviate Documentation
37. ^1 ^2Weaviate 1.34 Release - Weaviate Blog
38. ^1 ^2BYOC - Bring Your Own Cloud - Weaviate
39. ^Weaviate Cloud documentation - Weaviate Documentation
40. Weaviate Pricing in 2026 - Particula Tech
41. ^1 ^2Introducing Weaviate Embeddings - Weaviate Blog
42. ^1 ^2 ^3Weaviate Launches Flexible Embedding Service for AI Development - GlobeNewswire, 3 December 2024
43. ^1 ^2Welcome to the Next Era of Data and AI: Meet Weaviate Agents - Weaviate Blog
44. ^Weaviate Goes Full Stack With Launch of Weaviate Agents for AI Development - GlobeNewswire, 4 March 2025
45. ^Accelerating Data Workflows with Query Agent, now GA - Weaviate Blog
46. ^Weaviate Launches Agent Skills to Empower AI Coding Agents - GlobeNewswire, 21 February 2026
47. ^weaviate/Verba on GitHub - GitHub
48. ^Verba: Building an Open Source, Modular RAG Application - Weaviate Blog
49. ^Search Mode Benchmarking - Weaviate Blog
50. ^1 ^2 ^3 ^4 ^5Pinecone vs Weaviate 2026: Engineered Decision Guide - RankSquire
51. ^1 ^2 ^3 ^4 ^5Best Vector Databases in 2026: A Complete Comparison Guide - Firecrawl
52. ^From prototype to production: Vector databases in generative AI applications - Stack Overflow Blog
53. ^Case Studies - Weaviate
54. ^Announcing the Regional 2025 AWS Partners of the Year for Europe, Middle East, and Africa - AWS Partner Network Blog
55. ^Weaviate Python Client Changelog - Read the Docs
56. ^Weaviate Hero - Weaviate Blog
57. ^1 ^2Weaviate community - Weaviate
58. ^Bob van Luijt on AI-Native Apps, Open Source, and Innovation - Analytics Vidhya
59. Weaviate in 2025: Reliable Foundations for Agentic Systems - Weaviate Blog
60. ^Weaviate Pricing - Weaviate
61. ^Weaviate Embeddings: model choice - Weaviate Documentation
62. ^1 ^2Weaviate Transformation Agent (sunset) - Weaviate, updated 26 June 2026
63. ^1 ^2Weaviate Personalization Agent (sunset) - Weaviate, updated 26 June 2026
64. ^Release posts - Weaviate Blog
65. ^Inside the Pinecone - Pinecone Blog