NEWVectors or files. Pick a path.Start →
    Back to All Lists

    Best Vector Databases in 2026

    What are the best vector databases in 2026? Qdrant for open source you can self-host or rent, Pinecone for fully managed with no servers, pgvector if your data already lives in Postgres, and Milvus or Zilliz Cloud for billions of vectors. For large, rarely queried corpora, storage-first options such as turbopuffer and Amazon S3 Vectors ($0.06 per GB-month) cost far less to keep. Prices checked October 15, 2026.

    Ethan Steininger
    Published · Updated
    Last tested: October 15, 2026
    12 tools evaluated

    Mixpeek Vector Store keeps your vectors in a bucket you own and searches them there, with a hot cache for the part you query often. Bring your own embeddings. The Build plan is $25 a month plus usage, for up to 1M vectors.

    Bring your vectors, start searching

    Key Takeaways

    • Qdrant ranks first. It is open source under Apache 2.0, runs the same engine self-hosted or on Qdrant Cloud, and handles filtering, sparse and multi-vector search well. Version 1.19 (August 2026) added memory tiers, so less of a large index has to sit in RAM.
    • Pinecone is second and the simplest to run: fully managed, with a free Starter tier and a $50 monthly minimum on Standard. Full-text search went GA in September 2026, and a bring-your-own-cloud option followed two weeks later.
    • If you already run Postgres, start with pgvector. It adds HNSW and IVFFlat indexes to the database you have, so vectors, filters and joins live in one place. Version 0.8.7 shipped on October 1, 2026.
    • Storage-first databases changed the cost picture. Amazon S3 Vectors charges $0.06 per GB-month to store vectors, turbopuffer $0.33, and Pinecone's always-on Standard plan also lists $0.33 per GB-month plus read and write units. Storage-first systems trade some query latency for that.
    • We ranked 12 options on fit for common workloads, cost from published prices, operations, maturity and data control. We did not run our own latency benchmark, so this list quotes vendors' figures and labels them as theirs. Every price was read on the vendor's own page on October 15, 2026.

    Skip the comparison? Mixpeek runs vector databases on your own data: extraction, indexing, and search in one platform.

    How We Evaluated

    Evaluated by the Mixpeek engineering team, who build and operate multimodal retrieval infrastructure in production. Last tested October 2026; rankings re-checked when the market shifts, with pricing and claims verified against each vendor's public documentation.

    Workload fit

    25%

    How well it handles the common jobs: filtered nearest-neighbor search, hybrid keyword and vector search, sparse and multi-vector retrieval, and updates and deletes at scale, as documented by the vendor.

    Cost from published prices

    25%

    Entry price, minimums and per-unit rates for storage, writes and queries, read from each vendor's own pricing page on October 15, 2026. Free self-hosting counts, with the hardware you then pay for.

    Operations

    20%

    How much you run yourself: number of moving parts, managed and bring-your-own-cloud options, scaling and backups.

    Maturity and ecosystem

    15%

    Release cadence, client libraries, framework integrations, and whether the open-source project is maintained.

    Data control

    15%

    Open-source license, self-hosting, bring-your-own-cloud, and whether vectors can sit in storage you own.

    Quick answer

    The short version, before the detail:

    • Qdrantbest for teams that want an open-source engine they can self-host or rent, with strong filtering and sparse or multi-vector searchOpen source under Apache 2.0, with filtering inside the graph search and sparse and multi-vector support in one engine.
    • Pineconebest for teams that want production vector search without running any infrastructureFully managed with nothing to provision, now with full-text search and a bring-your-own-cloud option.
    • pgvector (PostgreSQL)best for teams already on postgres who want vector search next to their relational dataVector search inside the Postgres you already run, so there is no second database to keep in sync.
    • Milvus / Zilliz Cloudbest for billion-scale collections where storage and query capacity must scale separatelyA distributed design with object storage underneath and the widest range of index types, including disk and GPU.
    • Weaviatebest for teams that want hybrid search and in-database embedding without a separate pipelineHybrid BM25 and vector search in one query, with embedding at ingestion if you want it.
    • turbopufferbest for large, multi-tenant collections where most data is queried rarely and storage cost dominatesObject-storage pricing for vectors and full-text search, with a cache for what is hot.
    • Mixpeek Vector Store (MVS)best for teams that want vectors in their own bucket, or that search video, images and documents and want extraction and search in one placeSearch over vectors that stay in a bucket you own, with an optional pipeline that creates them from video, images, audio and documents.
    • Amazon S3 Vectorsbest for aws teams with large vector collections that are queried occasionallyVector search as an S3 feature, priced like storage, with no cluster or minimum.

    What a vector database is

    A vector database stores embeddings, the lists of numbers a model produces for a piece of text, an image or a clip, and finds the stored vectors closest to a query vector. That nearest-neighbor search is what lets a search box match meaning instead of keywords, and it is the retrieval step in most RAG systems. Exact search compares the query with every vector, which stops being affordable past a few million, so vector databases build approximate indexes such as HNSW graphs, IVF partitions or disk-resident graphs like DiskANN, and give up a little recall for a large speedup. A library such as FAISS gives you the index. A database adds what production needs around it: durable writes, updates and deletes, metadata filters applied during the search, replication, backups and access control. Many products now also run keyword (BM25) search beside the vector search and fuse the two, because exact terms like product codes and names still matter. The market splits four ways. Dedicated engines (Qdrant, Milvus, Weaviate, Vespa) keep indexes in memory or on local SSD for fast queries. Managed services (Pinecone, Zilliz Cloud, Qdrant Cloud) run those for you. Extensions (pgvector, Elasticsearch) add vectors to a database you already operate. Storage-first systems (turbopuffer, Amazon S3 Vectors, LanceDB, Mixpeek MVS) keep vectors on object storage and cache what is hot, which costs much less to store and is slower on a cold query. Pick the camp from your query rate and latency budget first, then compare products inside it. How the storage-first design works.

    Best Vector Databases: comparison at a glance

    #ToolBest forPricingKey differentiatorMain limit
    1QdrantTeams that want an open-source engine they can self-host or rent, with strong filtering and sparse or multi-vector searchFree self-hosted (Apache 2.0). Qdrant Cloud free tier of 0.5 vCPU, 1 GB RAM and 4 GB disk; Standard is usage-based, billed hourly on vCPU, RAM, disk and backup.Open source under Apache 2.0, with filtering inside the graph search and sparse and multi-vector support in one engine.Indexes live on block storage you provision; Qdrant does not run on NFS or object storage
    2PineconeTeams that want production vector search without running any infrastructureStarter free (up to 2 GB storage, 1M read units and 2M write units a month). Standard has a $50/month minimum, then $16-$18 per million read units, $4-$4.50 per million write units and $0.33/GB-month storage, varying by cloud and region.Fully managed with nothing to provision, now with full-text search and a bring-your-own-cloud option.Closed source and managed only; you cannot run it on your own hardware outside the BYOC option
    3pgvector (PostgreSQL)Teams already on Postgres who want vector search next to their relational dataFree (open-source extension). You pay for the Postgres you run it on.Vector search inside the Postgres you already run, so there is no second database to keep in sync.Index builds and memory use grow with the table, so very large collections need careful tuning or a dedicated engine
    4Milvus / Zilliz CloudBillion-scale collections where storage and query capacity must scale separatelyFree self-hosted. Zilliz Cloud Free: 5 GB storage, up to 5 collections. Standard from $0/month serverless; dedicated clusters priced per million vectors (from $5 to $63 depending on the option). Enterprise dedicated from $197/month. $200 in free credits.A distributed design with object storage underneath and the widest range of index types, including disk and GPU.A self-hosted cluster has many components to run
    5WeaviateTeams that want hybrid search and in-database embedding without a separate pipelineFree self-hosted. Weaviate Cloud Free: 100,000 objects, 1 GB memory, 10 GB disk. Flex starts at $45/month, from $0.00465 per million vector dimensions and $0.12/GiB storage. Premium from $400/month.Hybrid BM25 and vector search in one query, with embedding at ingestion if you want it.Pricing by vector dimensions takes some arithmetic to estimate
    6turbopufferLarge, multi-tenant collections where most data is queried rarely and storage cost dominatesLaunch plan $16/month minimum usage, scale plan $256/month minimum, enterprise from $4,096/month. Storage $0.33/GB, writes $2/GB, returned data $0.05/GB (read from the pricing page's calculator).Object-storage pricing for vectors and full-text search, with a cache for what is hot.A query against data that is not cached is slower than an in-memory engine
    7Mixpeek Vector Store (MVS)Teams that want vectors in their own bucket, or that search video, images and documents and want extraction and search in one placeBuild $25/month for up to 1M vectors; Scale $250/month for up to 25M; Enterprise from $10,000/month. Usage is billed on top of the plan fee: $1.56 per million vectors stored per month plus $0.023/GB-month storage, $2 per million writes and $2 per million queries.Search over vectors that stay in a bucket you own, with an optional pipeline that creates them from video, images, audio and documents.Newer than the other engines here, with fewer framework integrations
    8Amazon S3 VectorsAWS teams with large vector collections that are queried occasionallyus-east-1: storage $0.06/GB-month, PUT $0.20/GB (128 KB minimum per PUT), queries $2.50 per million plus a per-TB data-processed charge, data returned $0.01/GB beyond 500 KB per query.Vector search as an S3 feature, priced like storage, with no cluster or minimum.AWS only
    9LanceDBML teams who want vectors stored with their training and media data, often in notebooks and pipelinesFree (open source). Managed enterprise pricing on request; no public price list.An embedded, columnar store where vectors sit in the same table as the data they describe.No published prices for the managed product
    10ChromaPrototypes, notebooks and small RAG applicationsFree (open source). Chroma Cloud Starter $0/month with $5 credits; Team $250/month plus usage. Usage: $2.50/GiB written, $0.33/GiB-month stored, $0.0075/TiB queried, $0.09/GiB returned.The quickest way to get vector search running inside a Python project.The local client is meant for development, per Chroma's docs
    11VespaTeams building large search or recommendation systems with custom rankingFree self-hosted. Vespa Cloud is billed hourly per vCPU, memory GB and disk GB; Startup from $0.05/vCPU-hour. Enterprise has a $20,000/month minimum.Search, filtering and machine-learned ranking in one engine, at large scale.Steep learning curve and its own configuration model
    12Elasticsearch (vector search)Teams already running Elasticsearch that want semantic search in the same clusterElastic Cloud Serverless: search from $0.09 per VCU-hour, ingest $0.14 per VCU-hour, storage $0.047/GB-month; vector profiles include 50 GB free. Hosted Standard from $99/month.Vector search added to a mature text-search engine you may already operate.More system to run than a vector-only engine if you do not already use it

    The Mental Model That Makes Multimodal Search Click

    1

    Qdrant

    Qdrant is an open-source vector database written in Rust, under Apache 2.0, that you can run yourself or rent as Qdrant Cloud. It filters on payload fields during the graph search, so a filtered query does not lose results the way post-filtering does, and it supports named vectors, sparse vectors and multi-vector (late-interaction) search in the same collection. Qdrant 1.19 in August 2026 added memory tiers for keeping less of a large index in RAM. Qdrant's own installation docs require block storage with a POSIX filesystem and rule out NFS and S3 for its data, so plan for local or block disks when you self-host.

    What Sets It Apart

    Open source under Apache 2.0, with filtering inside the graph search and sparse and multi-vector support in one engine.

    Strengths

    • +Apache 2.0, with the same engine self-hosted or on Qdrant Cloud
    • +Filtering during the search instead of after it
    • +Named, sparse and multi-vector search in one collection
    • +Free cloud tier: 0.5 vCPU, 1 GB RAM and 4 GB disk

    Limitations

    • -Indexes live on block storage you provision; Qdrant does not run on NFS or object storage
    • -Cloud pricing is hourly by vCPU, RAM and disk, so you size a cluster rather than pay per query

    Choose This When

    When you want one engine you can run on your own machines or as a managed cluster, and your queries filter on metadata.

    Skip This If

    When you want to keep vectors on NFS or object storage, or pay only per query with nothing provisioned.

    Free self-hosted (Apache 2.0). Qdrant Cloud free tier of 0.5 vCPU, 1 GB RAM and 4 GB disk; Standard is usage-based, billed hourly on vCPU, RAM, disk and backup.
    Best for: Teams that want an open-source engine they can self-host or rent, with strong filtering and sparse or multi-vector search
    Visit Website
    2

    Pinecone

    Pinecone is a fully managed vector database: you create an index and write vectors, and there are no servers to size. Standard is billed by usage, with read units, write units and storage, over a $50 monthly minimum. In September 2026 Pinecone made full-text search generally available in the same database and launched a bring-your-own-cloud option that runs it in your own cloud account. It is closed source.

    What Sets It Apart

    Fully managed with nothing to provision, now with full-text search and a bring-your-own-cloud option.

    Strengths

    • +No infrastructure to run or size
    • +Free Starter tier: up to 2 GB storage, 1M read units and 2M write units a month
    • +Full-text search GA in September 2026, beside vector search
    • +Bring-your-own-cloud option for data residency

    Limitations

    • -Closed source and managed only; you cannot run it on your own hardware outside the BYOC option
    • -Usage pricing grows with query volume: reads list at $16 to $18 per million read units

    Choose This When

    When nobody on the team should be operating a database, and query volume is moderate enough that per-unit pricing stays predictable.

    Skip This If

    When you need to self-host, or a very high query rate makes read units the largest line on the bill.

    Starter free (up to 2 GB storage, 1M read units and 2M write units a month). Standard has a $50/month minimum, then $16-$18 per million read units, $4-$4.50 per million write units and $0.33/GB-month storage, varying by cloud and region.
    Best for: Teams that want production vector search without running any infrastructure
    Visit Website
    3

    pgvector (PostgreSQL)

    pgvector is an open-source PostgreSQL extension that adds a vector column type and HNSW and IVFFlat indexes. Your vectors sit in the same tables as the rest of your data, so a query can filter, join and search in one SQL statement, inside your existing backups and permissions. Version 0.8.0 added iterative index scans, which keep scanning when a filter removes too many results, and 0.8.7 shipped on October 1, 2026. Most managed Postgres services include it.

    What Sets It Apart

    Vector search inside the Postgres you already run, so there is no second database to keep in sync.

    Strengths

    • +One database: vectors, filters and joins in the same SQL
    • +Available on most managed Postgres services
    • +Iterative index scans for heavily filtered queries since 0.8.0
    • +Free and open source

    Limitations

    • -Index builds and memory use grow with the table, so very large collections need careful tuning or a dedicated engine
    • -No built-in keyword-plus-vector fusion; you write it in SQL yourself

    Choose This When

    When your data already lives in Postgres and the collection is in the millions to low tens of millions of vectors.

    Skip This If

    When you need billions of vectors, or vector traffic heavy enough that it should not share a database with your transactions.

    Free (open-source extension). You pay for the Postgres you run it on.
    Best for: Teams already on Postgres who want vector search next to their relational data
    Visit Website
    4

    Milvus / Zilliz Cloud

    Milvus is an open-source distributed vector database, and Zilliz Cloud is its managed service. It separates storage from compute: index files and logs live in object storage (MinIO, S3 or Azure Blob), and query and data nodes scale apart. It offers the widest choice of index types here, including HNSW, IVF variants, DiskANN and GPU indexes. Milvus 2.6 reached GA on Zilliz Cloud in January 2026.

    What Sets It Apart

    A distributed design with object storage underneath and the widest range of index types, including disk and GPU.

    Strengths

    • +Built for billions of vectors, with storage and compute scaled separately
    • +Many index types, including disk-based and GPU indexes
    • +Zilliz Cloud free tier: 5 GB storage and 5 collections
    • +Open source

    Limitations

    • -A self-hosted cluster has many components to run
    • -More system than a project of a few million vectors needs

    Choose This When

    When the collection is in the hundreds of millions or billions and you have the people to run, or the budget to rent, a cluster.

    Skip This If

    When the collection is small and a single engine or pgvector would do.

    Free self-hosted. Zilliz Cloud Free: 5 GB storage, up to 5 collections. Standard from $0/month serverless; dedicated clusters priced per million vectors (from $5 to $63 depending on the option). Enterprise dedicated from $197/month. $200 in free credits.
    Best for: Billion-scale collections where storage and query capacity must scale separately
    Visit Website
    5

    Weaviate

    Weaviate is an open-source vector database with hybrid search built in: one query combines BM25 keyword scoring, vector similarity and filters. Its vectorizer modules can call an embedding model during ingestion, so you can write objects and let Weaviate create the vectors. Weaviate Cloud has a free tier and a Flex plan that starts at $45 a month, billed by vector dimensions and storage, and its September 2026 price book added RQ-4 compression on HNSW indexes.

    What Sets It Apart

    Hybrid BM25 and vector search in one query, with embedding at ingestion if you want it.

    Strengths

    • +Hybrid keyword and vector search in one query
    • +Vectorizer modules can embed data during ingestion
    • +Free cloud tier: 100,000 objects
    • +Open source

    Limitations

    • -Pricing by vector dimensions takes some arithmetic to estimate
    • -Built-in vectorizers tie ingestion to a model provider's latency and limits

    Choose This When

    When keyword matches matter as much as semantic ones and you would rather not run an embedding pipeline.

    Skip This If

    When you already produce your own vectors and want the simplest per-query pricing.

    Free self-hosted. Weaviate Cloud Free: 100,000 objects, 1 GB memory, 10 GB disk. Flex starts at $45/month, from $0.00465 per million vector dimensions and $0.12/GiB storage. Premium from $400/month.
    Best for: Teams that want hybrid search and in-database embedding without a separate pipeline
    Visit Website
    6

    turbopuffer

    turbopuffer is a managed search engine that stores vectors and documents on object storage and caches what is queried, so storage costs about as much as the bucket underneath. It runs vector, BM25 and filtered search. turbopuffer reports 200 ms p99 query latency over 100 billion vectors for its ANN v3 index (January 2026), a vendor figure we have not reproduced. Plans start at a $16 monthly minimum.

    What Sets It Apart

    Object-storage pricing for vectors and full-text search, with a cache for what is hot.

    Strengths

    • +Object-storage economics: $0.33 per GB-month stored
    • +Vector, BM25 and filters in one service
    • +Low monthly minimum: $16 on the launch plan
    • +Scales to very large namespaces

    Limitations

    • -A query against data that is not cached is slower than an in-memory engine
    • -Managed only; vectors live in turbopuffer's storage

    Choose This When

    When you hold many namespaces or a very large corpus and only a fraction is queried at any time.

    Skip This If

    When every query needs single-digit millisecond latency, or the vectors must stay in your own bucket.

    Launch plan $16/month minimum usage, scale plan $256/month minimum, enterprise from $4,096/month. Storage $0.33/GB, writes $2/GB, returned data $0.05/GB (read from the pricing page's calculator).
    Best for: Large, multi-tenant collections where most data is queried rarely and storage cost dominates
    Visit Website
    7

    Mixpeek Vector Store (MVS)

    Our Pick
    Try MVS

    Mixpeek Vector Store keeps vectors and their payloads in an S3-compatible bucket you own and serves search from it, with a hot cache for the part you query often. You can bring your own embeddings, or let Mixpeek's pipeline extract and embed video, images, audio and documents and write them in. It runs vector search with metadata filters over the vectors in your bucket. It is newer than the rest of this list, so it has fewer integrations and less third-party testing.

    What Sets It Apart

    Search over vectors that stay in a bucket you own, with an optional pipeline that creates them from video, images, audio and documents.

    Strengths

    • +Vectors and payloads stay in your bucket
    • +Pairs with Mixpeek's extraction pipeline for video, images, audio and documents
    • +Published per-unit rates: $1.56 per million vectors a month, $2 per million writes and $2 per million queries
    • +Bring your own embeddings from any model

    Limitations

    • -Newer than the other engines here, with fewer framework integrations
    • -A query on data outside the hot cache is slower than an in-memory engine

    Choose This When

    When the vectors must stay in your own storage account, or when the content is media you also need to extract features from.

    Skip This If

    When you need the most mature ecosystem and integrations today, or an in-memory engine's latency on every query.

    Build $25/month for up to 1M vectors; Scale $250/month for up to 25M; Enterprise from $10,000/month. Usage is billed on top of the plan fee: $1.56 per million vectors stored per month plus $0.023/GB-month storage, $2 per million writes and $2 per million queries.
    Best for: Teams that want vectors in their own bucket, or that search video, images and documents and want extraction and search in one place
    Get started
    8

    Amazon S3 Vectors

    S3 Vectors is a vector index built into Amazon S3, generally available since December 2025. You create a vector bucket and indexes in it and query through the S3 API, paying for storage, uploads and queries with no cluster to run. An index holds up to 2 billion vectors, and a bucket up to 10,000 indexes. It is the cheapest place on this list to keep vectors, and it is built for corpora that are queried less often.

    What Sets It Apart

    Vector search as an S3 feature, priced like storage, with no cluster or minimum.

    Strengths

    • +$0.06 per GB-month storage, the lowest here
    • +No servers or minimums; pay per stored GB, upload and query
    • +Up to 2 billion vectors per index
    • +Lives in your AWS account next to the rest of your data

    Limitations

    • -AWS only
    • -Built for storage cost; a busy, latency-sensitive application is better served by an in-memory engine or a cache in front

    Choose This When

    When your data is on AWS and most vectors are rarely queried, such as archives or long-tail tenants.

    Skip This If

    When you serve high query rates with tight latency, or you are not on AWS.

    us-east-1: storage $0.06/GB-month, PUT $0.20/GB (128 KB minimum per PUT), queries $2.50 per million plus a per-TB data-processed charge, data returned $0.01/GB beyond 500 KB per query.
    Best for: AWS teams with large vector collections that are queried occasionally
    Visit Website
    9

    LanceDB

    LanceDB is an open-source vector database built on the Lance columnar format. It can run inside your application with no server, against a local directory or an object store path (s3://, gs://, az://), and keeps vectors next to the raw data and metadata in one table. Lance commits rely on the storage's atomic put or rename so that exactly one concurrent writer wins. LanceDB sells a managed enterprise product, and its pricing page goes to a sales contact rather than a price list.

    What Sets It Apart

    An embedded, columnar store where vectors sit in the same table as the data they describe.

    Strengths

    • +Embedded: runs in-process against a folder or a bucket
    • +Columnar format that stores vectors beside images, text and metadata
    • +Open source and actively released (0.40.0 on October 7, 2026)
    • +Works on local disks and S3-compatible storage

    Limitations

    • -No published prices for the managed product
    • -Concurrent writers need storage with atomic commits; check yours before sharing a dataset

    Choose This When

    When you work in Python or Rust pipelines and want vector search over a dataset without running a server.

    Skip This If

    When you need a hosted service with a published price list today.

    Free (open source). Managed enterprise pricing on request; no public price list.
    Best for: ML teams who want vectors stored with their training and media data, often in notebooks and pipelines
    Visit Website
    10

    Chroma

    Chroma is an open-source vector database known for the shortest path to a working prototype: it runs in your Python process, persists to a local directory, and has a simple API. Chroma Cloud adds a hosted service with published usage prices, and in 2026 it added an EU region and Chroma Sync for pulling data from S3, GitHub and the web. Chroma's own docs describe the local persistent client as meant for development and testing, and recommend a server for production.

    What Sets It Apart

    The quickest way to get vector search running inside a Python project.

    Strengths

    • +Running in minutes, in-process
    • +Simple API widely used in RAG tutorials
    • +Chroma Cloud with published usage prices
    • +Open source

    Limitations

    • -The local client is meant for development, per Chroma's docs
    • -Fewer tuning options than the dedicated engines

    Choose This When

    When you are building a prototype or a small app and want to be searching in minutes.

    Skip This If

    When you are planning a large production deployment from day one.

    Free (open source). Chroma Cloud Starter $0/month with $5 credits; Team $250/month plus usage. Usage: $2.50/GiB written, $0.33/GiB-month stored, $0.0075/TiB queried, $0.09/GiB returned.
    Best for: Prototypes, notebooks and small RAG applications
    Visit Website
    11

    Vespa

    Vespa is an open-source search and serving engine that combines vector search, BM25 text search, structured filters and machine-learned ranking in a single query, and runs it at very large scale. It is the most capable engine here for ranking logic, and the hardest to learn: applications are defined in Vespa's own schema and configuration. Vespa Cloud prices by vCPU, memory and disk per hour.

    What Sets It Apart

    Search, filtering and machine-learned ranking in one engine, at large scale.

    Strengths

    • +Vector, text, filters and ML ranking in one query
    • +Proven at very large scale
    • +Open source
    • +Ranking expressions run inside the engine

    Limitations

    • -Steep learning curve and its own configuration model
    • -Vespa Cloud Enterprise has a $20,000 monthly minimum

    Choose This When

    When ranking logic is the product, and you have engineers to learn and run Vespa.

    Skip This If

    When you need simple vector search running this week.

    Free self-hosted. Vespa Cloud is billed hourly per vCPU, memory GB and disk GB; Startup from $0.05/vCPU-hour. Enterprise has a $20,000/month minimum.
    Best for: Teams building large search or recommendation systems with custom ranking
    Visit Website
    12

    Elasticsearch (vector search)

    Elasticsearch added dense vector fields and approximate kNN search to its text engine, so teams already running it can add semantic search without a second system. Elastic Cloud Serverless bills search by compute hour and storage per GB-month, and lists a vector-optimized profile that includes 50 GB free. It suits combining a mature text-search setup with vectors more than serving vectors alone.

    What Sets It Apart

    Vector search added to a mature text-search engine you may already operate.

    Strengths

    • +Adds vectors to an Elasticsearch deployment you already run
    • +Mature text search, aggregations and tooling
    • +Vector-optimized serverless profile with 50 GB free
    • +Hybrid text and vector queries

    Limitations

    • -More system to run than a vector-only engine if you do not already use it
    • -Pricing by compute hour needs estimating against your traffic

    Choose This When

    When Elasticsearch already powers your search and you want to add semantic matching to it.

    Skip This If

    When you are starting fresh and only need vector search.

    Elastic Cloud Serverless: search from $0.09 per VCU-hour, ingest $0.14 per VCU-hour, storage $0.047/GB-month; vector profiles include 50 GB free. Hosted Standard from $99/month.
    Best for: Teams already running Elasticsearch that want semantic search in the same cluster
    Visit Website

    Which one fits your use case?

    Find your situation in the first column. The last column says when the pick is the wrong call.

    Choose it whenPickLook elsewhere when
    You want one engine you can run on your own machines or as a managed cluster, and your queries filter on metadata.QdrantYou want to keep vectors on NFS or object storage, or pay only per query with nothing provisioned.
    Nobody on the team should be operating a database, and query volume is moderate enough that per-unit pricing stays predictable.PineconeYou need to self-host, or a very high query rate makes read units the largest line on the bill.
    Your data already lives in Postgres and the collection is in the millions to low tens of millions of vectors.pgvector (PostgreSQL)You need billions of vectors, or vector traffic heavy enough that it should not share a database with your transactions.
    The collection is in the hundreds of millions or billions and you have the people to run, or the budget to rent, a cluster.Milvus / Zilliz CloudThe collection is small and a single engine or pgvector would do.
    Keyword matches matter as much as semantic ones and you would rather not run an embedding pipeline.WeaviateYou already produce your own vectors and want the simplest per-query pricing.
    You hold many namespaces or a very large corpus and only a fraction is queried at any time.turbopufferEvery query needs single-digit millisecond latency, or the vectors must stay in your own bucket.
    The vectors must stay in your own storage account, or when the content is media you also need to extract features from.Mixpeek Vector Store (MVS)You need the most mature ecosystem and integrations today, or an in-memory engine's latency on every query.
    Your data is on AWS and most vectors are rarely queried, such as archives or long-tail tenants.Amazon S3 VectorsYou serve high query rates with tight latency, or you are not on AWS.
    Managed Mixpeek

    Put vector databases to work

    Connect a bucket and Mixpeek runs the whole vector databases pipeline for you: extraction, indexing, and search over your own objects. No models to wire up, nothing to host.

    Start with Managed
    MVS · bring your own

    Already have vectors?

    Keep your embeddings on your own cloud and run dense, sparse, and BM25 search directly on object storage. From $25/mo.

    Start with MVS

    Frequently Asked Questions

    What is the best vector database in 2026?

    For most teams, Qdrant if you want open source you can self-host or rent, Pinecone if you want fully managed, and pgvector if your data already lives in Postgres. Milvus or Zilliz Cloud fit billions of vectors, and storage-first options such as turbopuffer and Amazon S3 Vectors fit large collections that are queried rarely.

    How much does a vector database cost?

    Open-source engines are free to run on your own hardware. Managed entry points as published on October 15, 2026: Pinecone Standard has a $50 monthly minimum, Weaviate Flex starts at $45 a month, turbopuffer at $16, and Qdrant Cloud, Zilliz Cloud and Chroma Cloud have free tiers. Amazon S3 Vectors has no minimum and charges $0.06 per GB-month to store vectors.

    Which vector database is cheapest for a very large collection?

    For storage, the object-storage-based options: Amazon S3 Vectors at $0.06 per GB-month, and turbopuffer and Chroma Cloud at $0.33. They are slower on queries that miss the cache, so they suit collections where most vectors are rarely read. MVS keeps vectors in your own bucket and charges $1.56 per million vectors a month plus $0.023 per GB, so it is not the cheapest place to store vectors; you choose it for keeping them in storage you own.

    Do I need a separate vector database if I already use Postgres?

    Often not. pgvector adds vector columns and HNSW and IVFFlat indexes to Postgres, so vectors, filters and joins share one database. Teams usually move to a dedicated engine when collections reach hundreds of millions of vectors or vector queries start competing with transactional load.

    Can I keep my vectors in my own storage?

    Yes, with a few options. Self-hosted Milvus and LanceDB read and write object storage you control, Amazon S3 Vectors keeps them in your AWS account, and Mixpeek MVS serves search from an S3-compatible bucket you own. Qdrant self-hosted keeps them on disks you provision; its docs rule out NFS and S3 for its data. Which engines run on NFS, Lustre or local NVMe.

    Which vector database is best for RAG?

    Any of the top five works for most RAG systems, and retrieval quality depends more on chunking, embeddings and reranking than on the database. Prefer one with hybrid keyword and vector search and filtering, since RAG questions often hinge on exact names and dates. How to tell whether a retrieval change helped.

    Why is Marqo not on this list anymore?

    Marqo's GitHub README says its open-source project is deprecated and will no longer receive updates, and the company now sells ecommerce search. We removed it in October 2026.

    How did you rank these vector databases?

    On workload fit, cost from published prices, operations, maturity and data control, weighted as shown above. We read every price on the vendor's own page on October 15, 2026. We did not run our own latency benchmark, so any latency figure here is the vendor's and is labeled that way.

    See how Mixpeek handles this

    Purpose-built for vector databases, not bolted on.

    MVS: Mixpeek Vector Store

    Mixpeek's dedicated page for this capability: architecture, benchmarks, and how it works.

    Explore MVS: Mixpeek Vector Store

    Talk to a Mixpeek engineer: free

    30 minutes. Bring your use case and we'll tell you exactly what would work and what wouldn't.

    Schedule a Free Call

    Explore Other Curated Lists

    infrastructure

    Best Embedding Visualization Tools

    How do you actually look at millions of embeddings? We compared the leading tools for visualizing and exploring embedding spaces on scale, interactivity, projection quality (UMAP/t-SNE/PCA), and how well they connect points back to the underlying content.

    7 tools rankedView List
    infrastructure

    Best Vector Databases for Images

    A practical guide to vector databases optimized for image similarity search. We benchmarked query latency, indexing speed, and recall across millions of image embeddings.

    10 tools rankedView List
    infrastructure

    Best RAG Frameworks & Platforms

    A practical comparison of frameworks and platforms for building Retrieval-Augmented Generation applications. We tested each on multi-document QA, citation accuracy, and multimodal RAG scenarios.

    10 tools rankedView List