Which of these 2026 vector databases are credible at billion-vector scale? Select all that apply.

Vendor selection at billion-vector scale is a different question from vendor selection at million-vector scale. Most of the products in this list were designed for a specific scale band; pushing them past that band breaks the operational story. **The three that scale to billions in 2026.** *Milvus and its managed twin Zilliz Cloud.* The canonical open source choice for billion-scale vector search. Multi-shard architecture, multiple index types (IVF-PQ, HNSW, DiskANN), and public deployments at LinkedIn and Salesforce. This is the default reach for serious billion-scale work. *Vespa.* A horizontally scaled IR engine used at Yahoo and Spotify for over a decade. Hybrid sparse + dense retrieval in a single index. Operationally heavy but designed from day one for billions of documents and high QPS. *Pinecone enterprise.* Either pod based (the legacy enterprise tier) or serverless P2 (the newer offering). Managed, with compressed indexes designed for billions. The managed shape means you do not run the infrastructure yourself, in exchange for a per vector cost. **The three that do not scale to billions.** *Chroma.* Designed for embedded local use, RAG prototyping, and single machine workflows. Excellent at that job, completely wrong shape for billions. *pgvector default config.* Postgres extension. Comfortable through about 10M vectors on a single Postgres instance; query latency drifts past interactive thresholds beyond that. Sharding Postgres for billion-vector workloads is possible but is no longer in pgvector's design intent. *LanceDB.* Columnar on disk format aimed at analytical workflows. Strong for batch retrieval and analytical use cases at moderate scale, not optimized for billion-vector high QPS production retrieval.

**Billion-vector scale is an architectural property, not a marketing claim.** A vector DB credible at that scale needs multi-shard horizontal scaling, ANN index types that work in compressed form (PQ, BQ, or DiskANN), and a real operational track record. Three vendors clear that bar in 2026; three do not. **Milvus / Zilliz Cloud (credible).** Multi-shard architecture with segment based storage, supports IVF-PQ, HNSW, and DiskANN. Open source Milvus is widely deployed at billion-scale; Zilliz Cloud is the managed offering from the same team. Public reference deployments at LinkedIn and Salesforce. Default reach for billion-scale work where the team can operate Kubernetes or pay for managed. **Vespa (credible).** Yahoo originated, now open source, horizontally scaled retrieval engine that handles hybrid sparse + dense in a single index. Multi-tenant deployments at Yahoo serve billions of documents; Spotify, OkCupid, and several large media platforms run on it. Operationally heavyweight (more like Elasticsearch than like a managed vector DB) but the architecture is right for billion-vector workloads with hybrid retrieval requirements. **Pinecone enterprise (credible).** The pod based enterprise tier and the newer serverless P2 are both designed for billion-scale managed workloads, with compressed indexes (Pinecone uses proprietary compression) and multi-region replication. The managed shape means no Kubernetes operations on the customer's side, in exchange for a per vector per month fee that becomes substantial at billions. **Chroma (not credible at billions).** Designed for embedded use inside a single application process, optimized for RAG prototyping and small to medium workloads. Excellent at that job. Pushing Chroma to billions is a category error. **pgvector default config (not credible at billions).** Postgres extension that runs ANN search inside the database.