United States verdict (TL;DR)
Verified 2026-05-23The US is the heaviest vector DB market and the home of every major commercial vendor in the category. Pinecone (New York) leads on developer mindshare. Weaviate (Amsterdam but US-strong) and Qdrant (Berlin) are the credible OSS-plus-managed challengers, with Qdrant gaining share on US cost-sensitive engineering teams in 2025-2026. Chroma (San Francisco) owns the developer-prototype wedge. Milvus / Zilliz (San Francisco) wins billion-vector workloads. pgvector is the honest default for the under-10M-vector workloads that describe most US RAG production deployments. Elasticsearch and MongoDB Atlas Vector are the "you already pay for it" answers. CCPA, expanding state privacy laws (CO, CT, VA, TX, MT), and SOC 2 plus HIPAA expectations shape vendor selection at US regulated buyers.
Picks for United States
- Managed vector DB for US net-new RAG: pinecone Largest US developer mindshare. Serverless tier reset economics. Watch Standard and Enterprise pod cost at cardinality-heavy multi-tenant scale.
- US OSS-plus-managed with hybrid search: weaviate BSD-3 license, built-in vectorizer modules, hybrid search. Strong US adoption alongside EU presence.
- US cost-sensitive engineering teams: qdrant Apache 2.0, Rust performance, strong recall-vs-cost. Gaining share at US scale-ups that audited Pinecone bills.
How the vector database software market looks in United States
The US vector database market is the largest and most mature globally. Every major commercial vendor in the category is either US-headquartered (Pinecone, Chroma, LanceDB, Zilliz Inc., MongoDB) or US-strong (Weaviate from Amsterdam with major US presence, Qdrant from Berlin, Elastic from Amsterdam/Mountain View). The US developer-experience and ecosystem investment defines the category: LangChain and LlamaIndex tutorial defaults, Vercel AI SDK integration, and the AWS Bedrock / Azure AI / GCP Vertex AI integration patterns are US-built.
The 2024-2025 procurement story in the US was Pinecone bill scrutiny: cardinality-heavy multi-tenant RAG workloads at Standard and Enterprise pod tiers produced verified bill shock, which drove documented evaluations of Qdrant, Weaviate, and pgvector at several mid-market and enterprise US accounts. Pinecone Serverless materially improved the economics for net-new workloads, and as of 2026 the procurement question is more nuanced than "is Pinecone too expensive" and closer to "model your specific workload before signing an Enterprise commit." pgvector adoption grew sharply in US engineering teams who realized their RAG workloads fit comfortably in their existing Postgres.
CCPA/CPRA (California) plus expanding state privacy laws in CT, CO, VA, TX, MT require deletion-on-request, portability, and opt-out for consumer personal data; for vector DBs storing embeddings of PII or PII-adjacent content this requires deletion orchestration across the vector index plus source data. HIPAA-covered entities can execute BAAs with Pinecone, MongoDB Atlas Vector, Elastic Cloud, and select Zilliz Cloud configurations. SOC 2 Type II is widely available across managed vendors (Pinecone, Weaviate Cloud, Qdrant Cloud, Zilliz Cloud, MongoDB Atlas, Elastic Cloud). For US federal use, FedRAMP authorization is available for Elastic Cloud and MongoDB Atlas; Pinecone, Weaviate, and Qdrant FedRAMP status varies and should be confirmed contractually.
Quick comparison, ranked for United States
| Product | Best for | Starts at | 10-emp/mo* | Pricing | G2 | Geo |
|---|---|---|---|---|---|---|
| 1 Pinecone | Startup through mid-enterprise product teams building RAG and semantic search | $0 | $0 | 4.6 | North America +2 | |
| 2 Weaviate | Mid-market through enterprise product and AI teams | $0 | $0 | 4.6 | Global +1 | |
| 3 Qdrant | Startup through mid-enterprise product and AI teams | $0 | $0 | 4.7 | Global +1 | |
| 4 Chroma | Solo developers, startups, and small-to-mid product teams | $0 | $0 | 4.6 | Global | |
| 5 Milvus / Zilliz Cloud | Engineering-led teams targeting large-scale vector workloads | $0 | $0 | 4.5 | Global | |
| 6 pgvector + Postgres | Any team already on Postgres with RAG or semantic-search workloads | $0 | $0 | 4.5 | Global | |
| 7 Elasticsearch (dense_vector) | Mid-market through global enterprise already on Elasticsearch | $0 | $0 | 4.4 | Global | |
| 8 MongoDB Atlas Vector Search | Teams already on MongoDB Atlas adding RAG or semantic search | $0 | $0 | 4.5 | Global | |
| 9 Vespa | Search and retrieval engineering teams at large scale | $0 | $0 | 4.5 | Global +1 | |
| 10 LanceDB | Developer teams building multimodal AI products | $0 | $0 | 4.5 | Global |
*10-employee monthly cost = base fee + (per-employee × 10) using the lowest published tier. For opaque-pricing vendors, no value is shown.
What buyers in United States actually pay
Median annual deal size by employee band, in USD. Crowdsourced from anonymized buyer disclosures.
| Product | Employee band | Median annual (USD) | Sample | Notes |
|---|---|---|---|---|
| Pinecone | Small-mid product team RAG | $12,000 | 60 | Serverless tier; net-new RAG workloads |
| Pinecone | Cardinality-heavy multi-tenant | $120,000 | 30 | Standard or Enterprise pods; verified bill scrutiny common |
| Qdrant | OSS-plus-managed mid-market | $18,000 | 40 | Qdrant Cloud paid tier; US region |
| Weaviate | OSS-plus-managed mid-market | $24,000 | 35 | Weaviate Cloud Services; US region |
United States-built or United States-strong vendors worth knowing
Not yet ranked in our global top 10, but credible options for United States buyers and worth a shortlist.
Pinecone (New York)
Visit ↗US-headquartered managed vector DB share leader. The default in US RAG tutorials.
Chroma (San Francisco)
Visit ↗Developer-first OSS vector DB owning the US prototype-and-early-RAG wedge.
Zilliz / Milvus (San Francisco / Shanghai)
Visit ↗US-headquartered commercial entity behind Milvus open-source. Billion-vector scale workloads.
All 10, ranked for United States
Same intelligence as the global ranking, vendor trust, review patterns, verified pricing, compliance, reordered for the United States market.
Pinecone
Managed vector DB share leader with the strongest RAG developer ecosystem.
Pinecone is the most widely adopted managed vector database for RAG and semantic search, the default choice in LangChain and LlamaIndex tutorials and the brand most developers reach for first. The August 2023 Serverless launch reset pricing economics for many net-new workloads by separating storage from query compute. Trade-offs: enterprise tiers (Standard and Enterprise pods, plus dedicated deployments) still produce sticker shock at high write volumes and cardinality-heavy multi-tenant RAG, and the proprietary control plane means migration cost is real once you are committed to namespace and metadata-filter patterns. Pinecone is closed-source, so the OSS comparison framing always applies.
Product engineering teams (5-500 employees) building RAG features who want the lowest-friction managed path and are willing to accept closed-source vendor lock-in in exchange for ecosystem maturity.
Cost-sensitive teams at high write volume (OSS Qdrant or Weaviate self-hosted typically wins), strict-OSS organizations, or teams whose workload fits comfortably in pgvector on existing Postgres.
Strengths
- Largest developer mindshare and ecosystem coverage in vector DBs
- Serverless tier (launched Aug 2023) decoupled storage and query billing
- Strong managed-service operational maturity and uptime track record
- Native integration in LangChain, LlamaIndex, Vercel AI SDK, and most RAG frameworks
- Metadata filtering and namespace-based multi-tenancy genuinely production-ready
Weaknesses
- Closed-source; no self-host option creates vendor lock-in concern
- Enterprise pod pricing still triggers verified bill shock at cardinality-heavy scale
- Limited to a small set of AWS, GCP, and Azure regions vs OSS self-host flexibility
Pricing tiers
partial- Starter (free)Free tier; one project; capped storage and reads$0 /mo
- Serverless (Standard)Pay-per-use; storage plus read/write units; published rates per unit$0 /mo
- EnterpriseDedicated capacity, advanced security, SLA, private networkingQuote
- · Read and write units priced separately; cardinality-heavy filtering inflates read units
- · Cross-region or private networking adds material cost on Enterprise
- · Backups, larger namespaces, and dedicated support gated to higher tiers
Key features
- +Serverless and pod-based deployment options
- +Metadata filtering with strong index support
- +Namespace-based multi-tenancy
- +Hybrid search (sparse plus dense)
- +Pinecone Inference (managed embedding generation)
- +Pinecone Assistant (managed RAG endpoint)
- +SOC 2 Type II and GDPR-aligned configurations
Weaviate
OSS vector DB with built-in vectorizer modules and a strong hybrid-search story.
Weaviate is the open-source vector database with one of the most developed module ecosystems in the category, vectorizer modules that call out to OpenAI, Cohere, Hugging Face, and others remove the need for a separate embedding pipeline, and hybrid search combining BM25 with dense vector retrieval is first-class. The commercial entity Weaviate B.V. is headquartered in Amsterdam and offers Weaviate Cloud Services (WCS) plus enterprise self-managed contracts. Strengths: BSD-3 license, GraphQL plus REST surface, EU-origin engineering team helps EU-buyer comfort. Trade-offs: GraphQL surface adds a learning curve for teams expecting REST or SQL, and managed Cloud Services pricing for serious workloads tracks closely with Pinecone rather than being dramatically cheaper.
Mid-market product engineering teams (20-1,000 employees) wanting an OSS-licensed vector DB with built-in vectorizer modules, hybrid search, and the option to self-host or buy the managed cloud.
Teams requiring SQL or simple REST-only patterns (Qdrant or Pinecone simpler), or workloads that fit pgvector and would not benefit from a dedicated vector DB.
Strengths
- BSD-3 open-source license; transparent project governance
- Built-in vectorizer modules (OpenAI, Cohere, HuggingFace, Voyage) remove embedding-pipeline glue
- First-class hybrid search (BM25 plus dense) with tunable alpha weighting
- EU-headquartered (Amsterdam); EU data residency and RGPD/DSGVO posture natural
- GraphQL plus REST API surface; strong schema and class model
Weaknesses
- GraphQL surface unfamiliar to many backend teams; learning curve real
- Weaviate Cloud Services pricing at scale tracks Pinecone rather than undercutting it
- Smaller ecosystem of third-party tooling than Pinecone
Pricing tiers
partial- Open SourceBSD-3; self-hosted; unlimited use$0 /mo
- Sandbox / FreeFree cloud sandbox for evaluation; capped$0 /mo
- Standard CloudPay-as-you-go managed cluster; published per-unit rates$0 /mo
- EnterpriseDedicated, BYOC, enterprise support, advanced securityQuote
- · Self-host requires meaningful Kubernetes and operational capacity
- · BYOC (bring-your-own-cloud) and dedicated cluster pricing custom-quote
- · Module usage may incur upstream API costs (OpenAI, Cohere) outside Weaviate billing
Key features
- +BSD-3 open-source core
- +Vectorizer modules (text2vec-openai, text2vec-cohere, multi2vec, others)
- +Hybrid search (BM25 plus dense)
- +Generative modules for RAG (generative-openai, generative-cohere)
- +Multi-tenancy with tenant-level data isolation
- +GraphQL and REST API
- +HNSW plus flat index options
Qdrant
Rust-built OSS vector DB with strong recall-vs-cost numbers and an EU origin.
Qdrant is the Rust-built open-source vector database that has gained share rapidly on the strength of independent benchmark numbers, the Apache 2.0 license, and a Berlin engineering footprint that natively suits EU data residency requirements. Strengths: tight performance per dollar, strong filtering ergonomics with payload indexes, and a clean REST plus gRPC API. The commercial entity Qdrant Solutions GmbH offers Qdrant Cloud as the managed service with regions across AWS, GCP, and Azure. Trade-offs: smaller ecosystem and partner network than Pinecone, and the rapid feature velocity has occasionally produced rough edges in client libraries that have since stabilized.
EU-headquartered product teams (any size) wanting OSS-licensed vector DB with strong performance per dollar, or global teams who prioritize recall-vs-cost benchmarks and Apache 2.0 licensing.
Teams whose decision is driven primarily by ecosystem breadth or LangChain-cookbook prevalence (Pinecone still ahead there), or workloads suited to pgvector.
Strengths
- Apache 2.0 license; permissive open-source
- Rust implementation; strong recall-vs-cost in independent benchmarks
- Berlin-headquartered; EU data residency posture natural for DSGVO and RGPD
- Payload indexes give fast filtering on metadata fields
- Clean REST plus gRPC API; strong client library coverage
Weaknesses
- Smaller third-party ecosystem than Pinecone
- Rapid feature velocity has produced occasional client-library rough edges
- Brand recognition still trails Pinecone and Weaviate in North America
Pricing tiers
partial- Open SourceApache 2.0; self-hosted; unlimited use$0 /mo
- Qdrant Cloud Free1 GB free cluster for evaluation$0 /mo
- Qdrant Cloud (paid)Pay-as-you-go cluster; published per-unit rates$0 /mo
- Hybrid Cloud / Private CloudBYOC or private deployment; enterprise termsQuote
- · Self-host operational capacity (Kubernetes recommended)
- · Hybrid Cloud (control plane in Qdrant, data plane in customer VPC) custom-quote
- · Cross-region replication on paid tiers
Key features
- +Apache 2.0 open-source core (Rust)
- +Payload indexes for fast metadata filtering
- +HNSW with quantization (scalar, product, binary)
- +Sparse vectors and hybrid search
- +Multi-tenant collections with shard-level isolation
- +REST and gRPC API
- +Cluster mode and replication
Chroma
Developer-first OSS vector DB; the default for early RAG prototypes.
Chroma is the open-source vector database that owns the "first vector DB I ever installed" wedge, "pip install chromadb" launches a working in-process embedded vector store in under a minute, which has made it the default choice in LangChain and LlamaIndex tutorials for prototypes and small-to-medium RAG workloads. Apache 2.0 licensed. Chroma Cloud is the managed service entering broader availability in 2025-2026. Trade-offs: production scale, advanced multi-tenancy, and very-large-collection performance have historically trailed dedicated competitors like Pinecone, Qdrant, and Weaviate, with the gap narrowing as the project matures.
Solo developers and small product teams (1-50 employees) building RAG prototypes and small-to-medium production workloads where developer friction matters more than peak ANN performance.
Billion-vector enterprise workloads (Milvus, Vespa, or managed Pinecone Serverless better), or teams requiring mature multi-tenancy and enterprise governance today.
Strengths
- Apache 2.0 open-source; trivial onboarding via "pip install chromadb"
- In-process embedded mode plus client-server mode
- Default in many LangChain and LlamaIndex tutorial paths
- Strong Python-first developer experience
- Chroma Cloud managed offering broadening in 2025-2026
Weaknesses
- Production-scale performance historically trails Pinecone, Qdrant, Weaviate
- Advanced multi-tenancy and enterprise governance still maturing
- Cloud offering newer; reference customers at scale fewer than competitors
Pricing tiers
partial- Open SourceApache 2.0; embedded or self-hosted; unlimited use$0 /mo
- Chroma Cloud FreeFree tier on managed cloud during broader rollout$0 /mo
- Chroma Cloud (paid)Usage-based managed pricing; published per-unit rates$0 /mo
- EnterpriseDedicated deployment and enterprise supportQuote
- · Self-host operational capacity once beyond embedded mode
- · Cloud pricing model still iterating; verify before long-term commitments
Key features
- +Apache 2.0 open-source core
- +Embedded in-process mode (sqlite-backed)
- +Client-server mode for production
- +Metadata filtering
- +Python-first SDK plus JS/TS client
- +Chroma Cloud managed service
- +Built-in embedding function adapters (OpenAI, Cohere, HuggingFace)
Milvus / Zilliz Cloud
Open-source billion-scale vector DB; Zilliz Cloud is the managed offering.
Milvus is the open-source vector database that has been production-targeted at billion-scale workloads from inception, an LF AI and Data Foundation graduated project that supports multiple ANN index types (HNSW, IVF, DiskANN, GPU-accelerated) and is one of the few credible choices for billion-vector deployments. Zilliz Inc. is the commercial company behind Milvus and offers Zilliz Cloud as the fully managed service across AWS, GCP, and Azure. Trade-offs: operational complexity self-hosted is real, and the multiple-index-type flexibility is also a multiple-index-type decision burden for teams new to ANN tuning.
Engineering-led teams (any size) targeting billion-scale or near-billion-scale vector workloads, or organizations that need GPU-accelerated ANN and Apache 2.0 licensing.
Small RAG prototypes (Chroma simpler), teams without engineering capacity for index tuning, or workloads suited to pgvector.
Strengths
- Apache 2.0 open-source; LF AI and Data graduated project
- Multiple ANN indexes (HNSW, IVF variants, DiskANN, GPU-accelerated)
- Production deployments at billion-vector scale documented
- Zilliz Cloud managed service across AWS, GCP, Azure
- Strong hybrid search and sparse-dense fusion
Weaknesses
- Self-hosted operational complexity meaningful (multiple components)
- Index choice and tuning surface area can overwhelm newer teams
- Smaller Western ecosystem mindshare than Pinecone or Weaviate despite scale credentials
Pricing tiers
partial- Milvus Open SourceApache 2.0; self-hosted; unlimited use$0 /mo
- Zilliz Cloud FreeFree serverless cluster for evaluation$0 /mo
- Zilliz Cloud ServerlessPay-as-you-go; per-unit storage and query rates$0 /mo
- Zilliz Cloud Dedicated / EnterpriseDedicated clusters and enterprise termsQuote
- · Self-host needs etcd, object storage, message queue; full stack non-trivial
- · GPU-accelerated indexes require GPU compute (separate billing on Cloud)
- · Cross-region replication and private networking on Dedicated/Enterprise
Key features
- +Apache 2.0 open-source (Milvus)
- +Multiple ANN indexes (HNSW, IVF, DiskANN, GPU)
- +Scalar plus product quantization
- +Sparse-dense hybrid search
- +Multi-tenancy via partitions
- +GPU acceleration option
- +Zilliz Cloud managed service
pgvector + Postgres
You might not need a dedicated vector DB. pgvector handles most RAG under 10M vectors.
pgvector is the open-source Postgres extension that adds vector types, distance operators, and approximate-nearest-neighbor indexes (IVF and HNSW) to any Postgres instance. The honest framing: for most production RAG workloads under 5-10M vectors, pgvector on a well-tuned Postgres with HNSW indexing is the most cost-effective answer, particularly because most buyers already pay for a managed Postgres (RDS, Aurora, Cloud SQL, Azure Database for PostgreSQL, Supabase, Neon, Crunchbridge). The decision to add a dedicated vector DB should be driven by scale, latency at very high concurrency, or multi-tenancy requirements, not by vendor pitch. Trade-offs: at very large scale (tens to hundreds of millions of vectors) dedicated DBs still win on latency and operational ergonomics.
Teams already on Postgres (any size) with RAG or semantic-search workloads in the under-5-to-10M-vector range who want to avoid adding a new vendor and a new datastore.
Billion-vector workloads (Milvus, Vespa, or managed Pinecone better), multi-tenant SaaS with many thousands of tenants per cluster, or teams requiring sub-10ms p99 at high QPS.
Strengths
- PostgreSQL License (permissive) open-source extension
- Runs on any Postgres including managed services (RDS, Aurora, Cloud SQL, Supabase, Neon)
- No new vendor to procure or new query language to learn
- HNSW index (since pgvector 0.5) gives competitive ANN performance for sub-10M-vector workloads
- Transactional consistency with operational data in the same Postgres
- Hybrid search via combination with Postgres full-text or pg_trgm
Weaknesses
- At very large scale (50M+ vectors) dedicated DBs win on latency and operations
- Index build time on large datasets can be long; tuning is a real skill
- Multi-tenancy at thousands of tenants strains a single Postgres without careful schema design
Pricing tiers
public- pgvector extensionOpen-source; PostgreSQL License; free$0 /mo
- Hosted Postgres (managed)Cost is your managed Postgres bill; AWS RDS, Aurora, Supabase, Neon, etc.$0 /mo
- · Storage and IO on your Postgres scale with vector volume
- · HNSW index build can require temporary memory and CPU spikes
- · Operational cost of tuning ANN parameters (m, ef_construction, ef_search)
Key features
- +Vector data type and distance operators (L2, inner product, cosine)
- +IVFFlat and HNSW approximate-nearest-neighbor indexes
- +Works on any Postgres 11+ (managed or self-hosted)
- +SQL JOINs across vectors and operational data
- +Transactional ACID semantics
- +Combined with Postgres full-text and pg_trgm for hybrid search
Elasticsearch (dense_vector)
Vector search inside the Elasticsearch you already run.
Elasticsearch added dense_vector field types and approximate kNN search powered by HNSW in 8.x, plus the ELSER sparse-vector model for learned sparse retrieval. The pitch is direct: if you already pay for Elasticsearch for log search, application search, or observability, adding vector retrieval avoids a new vendor, a new datastore, and the data-movement plumbing. Trade-offs: peak ANN performance and pure-vector developer ergonomics still trail dedicated vector DBs, and the SSPL plus Elastic License v2 dual-licensing situation (after the 2021 Elastic-AWS split) is something buyers should understand. ELSER is a meaningful sparse-retrieval differentiator for hybrid search.
Organizations already running Elasticsearch (any size) who want to add RAG, semantic search, or hybrid retrieval without adding a new datastore or vendor.
Teams not already on Elasticsearch (dedicated vector DBs simpler), workloads where peak ANN performance per dollar matters above all (Qdrant, Pinecone Serverless win), or strict-OSS organizations.
Strengths
- Vector search alongside existing inverted-index, log, and observability data
- ELSER (Elastic Learned Sparse Encoder) for sparse-vector hybrid retrieval
- Hybrid (BM25 plus dense plus ELSER) ranking is first-class
- Existing Elastic operational tooling, security, and access control apply
- Native integration in LangChain and LlamaIndex
Weaknesses
- Peak ANN latency and recall-vs-cost trail dedicated vector DBs at scale
- SSPL plus Elastic License v2 licensing requires legal review for some buyers
- Cluster sizing and shard tuning for vector workloads has its own learning curve
Pricing tiers
partial- Elastic Stack (self-managed)SSPL plus Elastic License v2; self-host on your infra$0 /mo
- Elastic Cloud StandardManaged cluster pricing per node-hour$0 /mo
- Elastic Cloud Gold / Platinum / EnterpriseAdds ML, security tiering, dedicated supportQuote
- Elastic Cloud ServerlessNewer serverless tier; usage-based$0 /mo
- · Vector indexes increase storage and memory footprint on existing clusters
- · ML node tier required for ELSER inference in production
- · Cross-region replication and HA on enterprise tiers
Key features
- +dense_vector field type with HNSW approximate kNN
- +ELSER sparse-vector model for learned sparse retrieval
- +Hybrid ranking (BM25 plus dense plus ELSER)
- +Existing Elasticsearch query DSL and aggregations
- +Role-based access control and field-level security
- +Cross-cluster replication and search
- +Native LangChain and LlamaIndex integrations
MongoDB Atlas Vector Search
Vector index next to operational documents in the Atlas cluster you already pay for.
MongoDB Atlas Vector Search adds an approximate-nearest-neighbor index to Atlas clusters, letting teams store embeddings alongside operational JSON documents and run vector queries via the existing MongoDB aggregation pipeline. The strategic pitch matches Elastic: if you already pay for Atlas, adding vector search removes the data-movement overhead of synchronizing embeddings to a separate dedicated DB. Trade-offs: peak ANN performance trails dedicated vector DBs, and the Atlas cluster sizing model means vector workloads share resources with operational queries, which can require careful capacity planning. MongoDB is the primary positioning for many JSON-shaped RAG use cases.
Teams already on MongoDB Atlas (any size) building RAG or semantic search over JSON-shaped operational data who want to avoid adding a separate vector DB.
Teams not on MongoDB (dedicated vector DBs simpler), petabyte vector workloads, or strict-OSS organizations bothered by SSPL on Community Server.
Strengths
- Vector index sits alongside operational JSON documents in same Atlas cluster
- No data movement or separate sync pipeline required
- Aggregation pipeline supports vector plus structured plus text in one query
- Existing Atlas RBAC, encryption, backups, and HA apply
- Native LangChain and LlamaIndex integration
Weaknesses
- Peak ANN performance and recall-vs-cost trail dedicated vector DBs
- Atlas cluster sizing shares resources between operational and vector workloads
- Server-Side Public License (SSPL) on MongoDB Community requires legal review
Pricing tiers
public- Atlas Shared (M0/M2/M5)Free M0; shared clusters; limited vector capacity$0 /mo
- Atlas Dedicated (M10+)Dedicated clusters; Vector Search available$0 /mo
- Atlas Search NodesOptional dedicated Search/Vector nodes to isolate workload$0 /mo
- Enterprise AdvancedSelf-managed Enterprise with vector capabilitiesQuote
- · Search Nodes are billed separately from operational cluster
- · Backups, BI Connector, Atlas Data Federation billed separately
- · Cross-region clusters and dedicated VPC peering add cost
Key features
- +Vector index on Atlas (HNSW)
- +Hybrid query in aggregation pipeline (vector plus text plus structured)
- +Atlas Search Nodes for workload isolation
- +Existing Atlas RBAC and encryption
- +Multi-region and multi-cloud clusters
- +Native LangChain and LlamaIndex integration
- +Atlas Stream Processing for ingestion
Vespa
Open-source serious-scale hybrid retrieval engine; consumer-internet pedigree.
Vespa is the open-source serving engine originally built at Yahoo to power consumer-internet-scale retrieval (Yahoo Search, Mail, Finance, Sports). It combines keyword search, vector search, structured filters, and ranking into a single engine designed for very large scale and low latency. Apache 2.0 licensed. Vespa.ai was spun out as an independent company in 2023 and offers Vespa Cloud as the managed service. Trade-offs: the configuration model (XML-based application packages, ranking expressions) is genuinely powerful but has a steep learning curve, and the project assumes a level of search-systems sophistication that most RAG-builder teams have not yet developed.
Search and retrieval engineers (50-100,000+ employees) at consumer-internet, marketplace, or large-corpus search scale who need hybrid retrieval with learned ranking at low latency.
Small RAG prototypes (Chroma or pgvector vastly simpler), teams without dedicated search infrastructure engineers, or any team that just wants to call.upsert() and.query().
Strengths
- Apache 2.0 open-source with consumer-internet-scale heritage
- Combined keyword, vector, structured, and ranking in one engine
- Production deployments at very large scale (Yahoo, Spotify-tier)
- First-class hybrid retrieval and learned ranking
- Vespa Cloud managed service for teams without ops capacity
Weaknesses
- Steep learning curve; XML-based application packages and ranking expressions
- Smaller ecosystem of RAG tutorials than Pinecone or Weaviate
- Overkill for most under-100M-vector RAG workloads
Pricing tiers
partial- Vespa Open SourceApache 2.0; self-hosted; unlimited use$0 /mo
- Vespa Cloud TrialFree trial credits on managed cloud$0 /mo
- Vespa Cloud (paid)Usage-based per-node pricing on managed cloud$0 /mo
- Vespa Cloud EnterpriseDedicated, BYOC, and enterprise supportQuote
- · Self-host operational complexity at scale is real
- · Cross-region and dedicated networking on enterprise tier
- · Ranking model serving may require additional compute
Key features
- +Apache 2.0 open-source core
- +Combined vector, keyword, structured, ranking
- +Multiple ANN indexes (HNSW, others)
- +Learned ranking via ONNX or TensorFlow models
- +Application packages for declarative deployment
- +Tensor framework for ranking expressions
- +Vespa Cloud managed service
LanceDB
Embedded-first OSS vector DB on the Lance columnar format; multimodal-ready.
LanceDB is the open-source vector database built on Lance, a modern columnar format optimized for multimodal AI data (text, image, video, audio embeddings plus their source assets). Apache 2.0 licensed. The architecture is embedded-first and serverless-friendly, with data stored on object storage (S3, GCS, Azure Blob) and zero-cost-when-idle economics. LanceDB Cloud is the managed service for teams who want fully managed. Trade-offs: newer project, smaller ecosystem than Pinecone or Weaviate, and the embedded-first design philosophy means it competes more with Chroma than with billion-vector dedicated DBs.
Developer teams (1-500 employees) building multimodal AI products or wanting embedded vector storage on object storage with serverless economics.
Billion-vector enterprise workloads (Milvus or Vespa better), buyers requiring the largest managed-vector-DB ecosystem, or teams whose workload fits pgvector.
Strengths
- Apache 2.0 open-source; built on the Lance columnar format
- Embedded-first design; "pip install lancedb" works in-process
- Object-storage-backed (S3, GCS, Azure Blob); zero-cost-when-idle economics
- Multimodal-friendly (text, image, video, audio embeddings)
- Strong filtering and versioning via Lance format
Weaknesses
- Newer project; smaller ecosystem than Pinecone, Weaviate, Qdrant
- Embedded-first architecture means competes with Chroma rather than billion-vector DBs
- Cloud offering still maturing in 2026
Pricing tiers
partial- LanceDB OSSApache 2.0; embedded or self-hosted; unlimited use$0 /mo
- LanceDB Cloud FreeFree tier on managed cloud$0 /mo
- LanceDB Cloud (paid)Usage-based managed; per-unit storage and query$0 /mo
- EnterpriseDedicated, BYOC, enterprise supportQuote
- · Object storage and request costs on self-host (S3, GCS, Azure Blob)
- · Cloud pricing model still iterating
- · Embedded mode operational responsibility on customer
Key features
- +Apache 2.0 open-source
- +Lance columnar format (versioned, multimodal-friendly)
- +Embedded in-process mode
- +Object-storage backend (S3, GCS, Azure Blob)
- +IVF_PQ and HNSW indexes
- +Strong filtering and predicate pushdown
- +Multimodal embedding storage (text, image, video, audio)
Frequently asked questions
The questions buyers actually ask before they sign.
Why did Pinecone procurement come under scrutiny at some US accounts in 2024-2025?
When should a US team default to pgvector instead of a dedicated vector DB?
What is the difference between a dedicated vector database and a general-purpose database with a vector extension?
Is Pinecone too expensive in 2026?
Should we use an open-source vector DB (Weaviate, Qdrant, Chroma, Milvus) instead of Pinecone?
Do we actually need a dedicated vector database?
What is the trade-off between recall and latency at scale?
Should we keep the embedding model decision separate from the vector storage decision?
How does multi-tenancy actually work at SaaS scale in a vector DB?
What does cost-per-query really look like across managed vector DBs?
Final word
Looking at a different market? See the global Vector Database Software ranking, or pick another country at the top of this page.
Last updated 2026-05-23. Local pricing reverified quarterly. Found something inaccurate? Tell us.