{"@context":"https://schema.org","@type":"Article","headline":"Vector DB Pricing Compare","description":"Compare vector database pricing across Pinecone, Qdrant, Weaviate, Zilliz/Milvus, Chroma, Astra DB, Cloudflare Vectorize, Supabase, Neon, and self-hosted pgvector on Hetzner VPS. Sizing calculator with embedding dimensions, FP32/INT8 quantization, HNSW index overhead, and query RUs.","mainEntityOfPage":{"@type":"WebPage","@id":"https://dracon.uk/tools//vector-db-compare"},"url":"https://dracon.uk/tools//vector-db-compare","datePublished":"2026-08-20","dateModified":"2026-08-20","author":{"@id":"https://dracon.uk/tools/#person","name":"Dracon"},"reviewedBy":{"@id":"https://dracon.uk/tools/#person","name":"Dracon"},"publisher":{"@id":"https://dracon.uk/tools/#organization"},"inLanguage":"en-GB","keywords":[],"image":"https://dracon.uk/tools/favicon.svg"} {"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How do vector embedding dimensions impact monthly database cost?","acceptedAnswer":{"@type":"Answer","text":"Vector dimensions directly dictate memory and disk consumption. A 1,536-dimensional vector (OpenAI text-embedding-3-small) uses 6,144 bytes in standard 32-bit float (FP32), whereas a 768-dimensional vector (Nomic / BGE) uses 3,072 bytes. When stored in-memory with HNSW graph indexes, every doubling of dimension doubles RAM footprint, which can push dedicated clusters into significantly higher pricing tiers."}},{"@type":"Question","name":"What is the cost difference between Serverless and Dedicated Pods/Clusters?","acceptedAnswer":{"@type":"Answer","text":"Serverless vector databases (e.g. Pinecone Serverless, Cloudflare Vectorize, Astra DB) charge strictly per-gigabyte of storage and per-million Read Units (RUs). They scale to zero at minimal idle cost. Dedicated clusters (e.g. Qdrant Cloud, Pinecone Pods, Weaviate Dedicated) have fixed hourly floor costs ($9 to $70+/mo minimum) but provide unlimited queries within node RAM capacity, making them substantially cheaper under sustained high-QPS production traffic."}},{"@type":"Question","name":"How does INT8 Scalar and Binary Quantization reduce vector search TCO?","acceptedAnswer":{"@type":"Answer","text":"Scalar Quantization (INT8) compresses 32-bit floats into 8-bit integers, reducing memory requirements by 75% with negligible accuracy drop (\u003c1% recall loss). 1-Bit Binary Quantization compresses vectors up to 32x, allowing millions of embeddings to reside in minimal RAM on affordable VPS instances (e.g. Hetzner Cloud) rather than expensive multi-gigabyte managed clusters."}},{"@type":"Question","name":"When should I choose pgvector over a specialized vector database?","acceptedAnswer":{"@type":"Answer","text":"pgvector (on PostgreSQL, Supabase, Neon, or self-hosted) is ideal when your vector count is under 10-20 million and vectors reside alongside existing relational business data (users, auth, metadata). It eliminates dual-database sync lag and allows single ACID transactions. Dedicated vector engines (Qdrant, Milvus/Zilliz, Pinecone) become advantageous above 20M+ vectors where specialized distributed indexing (HNSW, DiskANN) outpaces Postgres vacuuming and shared memory."}},{"@type":"Question","name":"What is the memory overhead of HNSW indexing?","acceptedAnswer":{"@type":"Answer","text":"Hierarchical Navigable Small World (HNSW) builds multi-layer proximity graphs to achieve sub-10ms nearest neighbor search. The graph edges and adjacency lists typically add 1.4x to 2.0x storage overhead on top of the raw vector arrays. For 1M 1536-dim vectors (6.14GB raw), an HNSW index typically requires ~9.2GB to 12GB of combined RAM and high-speed NVMe."}},{"@type":"Question","name":"Why is self-hosting on a VPS (e.g., Hetzner) often 10x cheaper?","acceptedAnswer":{"@type":"Answer","text":"Managed cloud providers bundle multi-tenant compute markup, automated failover, and high gross margins into their storage and RU rates. Running open-source Qdrant, Weaviate, or pgvector on a modern NVMe VPS (e.g. Hetzner CPX31 with 4 vCPU, 8GB RAM, 160GB NVMe for €14.60/mo) provides dedicated raw hardware capable of serving millions of vectors at a fraction of hyperscaler rates."}}],"url":"https://dracon.uk/tools//vector-db-compare"}Vector DB Pricing Compare · Interactive TCO Calculator | Dracon
Skip to main content
Dracon Platform · AI Infrastructure Utilities

Vector DB Pricing Compare

Select your vector count, embedding dimensions, and quantization; get ranked monthly TCO across 12 vector databases — including Serverless (Pinecone, Cloudflare, Astra DB), Managed Dedicated Clusters (Qdrant, Weaviate, Zilliz), PostgreSQL pgvector extensions, and self-hosted VPS baselines.

Catalog verified · 12 Providers Verified · production ready

Workload Presets

Click to load common production scenarios

Workload Parameters

1,000,000 vectors
1536 dimensions
FP32 (32-bit)
1.00M queries/mo
Raw Vectors 6.14 GB
HNSW Index 3.07 GB
Metadata Payload 0.50 GB
Total Footprint 9.72 GB

Ranked Monthly Cost (12 eligible)

Sorted lowest to highest total estimated monthly infrastructure cost
#1
pgvector on Hetzner VPS (Self-Hosted) OSS EU
Hetzner Online GmbH · self_hosted
Storage: €0.00 Queries: €0.00 Base: €7.85
€7.85 /mo
Save $212 (96%) vs Pinecone
Visit →
#2
Neon Serverless Postgres (pgvector) OSS
Neon Inc. · relational_extension
Storage: $0.00 Queries: $0.00 Base: $19.00
$19.00 /mo
Save $201 (91%) vs Pinecone
Visit →
#3
DataStax Astra DB Vector Serverless
DataStax Inc. · serverless
Storage: $0.00 Queries: $0.00 Base: $20.00
$20.00 /mo
Save $200 (91%) vs Pinecone
Visit →
#4
AWS RDS PostgreSQL (pgvector) OSS
Amazon Web Services · relational_extension
Storage: $0.00 Queries: $0.00 Base: $28.00
$28.00 /mo
Save $192 (87%) vs Pinecone
Visit →
#5
Cloudflare Vectorize Serverless
Cloudflare Inc. · serverless
Storage: $0.00 Queries: $0.00 Base: $30.00
$30.00 /mo
Save $190 (86%) vs Pinecone
Visit →
#6
Qdrant Cloud Managed OSS EU
Qdrant GmbH · dedicated
Storage: $0.00 Queries: $0.00 Base: $36.00
$36.00 /mo
Save $184 (84%) vs Pinecone
Visit →
#7
Weaviate Cloud (WCS) OSS EU Serverless
Weaviate B.V. · serverless
Storage: $0.00 Queries: $0.00 Base: $110.00
$110.00 /mo
Save $110 (50%) vs Pinecone
Visit →
#8
Pinecone Pod-Based (Dedicated)
Pinecone Systems · dedicated
Storage: $0.00 Queries: $0.00 Base: $140.00
$140.00 /mo
Save $80 (36%) vs Pinecone
Visit →
#9
Zilliz Cloud (Managed Milvus) OSS Serverless
Zilliz Inc. · serverless
Storage: $0.00 Queries: $0.00 Base: $150.00
$150.00 /mo
Save $70 (32%) vs Pinecone
Visit →
#10
Supabase Vector (pgvector) OSS
Supabase Inc. · relational_extension
Storage: $0.00 Queries: $0.00 Base: $160.00
$160.00 /mo
Save $60 (27%) vs Pinecone
Visit →
#11
Chroma Cloud Managed OSS Serverless
Chroma Inc. · serverless
Storage: $0.00 Queries: $0.00 Base: $199.00
$199.00 /mo
Save $21 (10%) vs Pinecone
Visit →
#12
Pinecone Serverless Serverless
Pinecone Systems · serverless
Storage: $0.00 Queries: $0.00 Base: $220.00
$220.18 /mo
Visit →

Architecture & Cost Comparison Insights

Serverless vs Dedicated Clusters

Serverless models (Pinecone, Cloudflare Vectorize, Astra DB) excel for unpredictable traffic or prototype workloads, scaling to zero with no maintenance. However, under high sustained search throughput (10M+ queries/month), dedicated in-memory clusters (Qdrant, Milvus) are substantially cheaper since query RUs are bundled into node RAM.

pgvector vs Specialized Vector DBs

pgvector is unbeatable when vectors live alongside operational SQL data (Supabase, Neon, RDS), eliminating cross-database synchronization. Specialized engines (Qdrant, Pinecone, Weaviate) pull ahead above 10M+ vectors where multi-stage filtering, native quantization, and isolated HNSW indexing memory matter.

Quantization Impact on Infrastructure

Enabling Scalar (INT8) quantization reduces in-memory footprint by 75% while retaining >99% search recall. This turns what would be a $500+/mo dedicated cluster requirement into an affordable $36/mo node or a low-tier self-hosted VPS instance.

Vector Database Pricing & TCO FAQ

How do vector embedding dimensions impact monthly database cost?

Vector dimensions directly dictate memory and disk consumption. A 1,536-dimensional vector (OpenAI text-embedding-3-small) uses 6,144 bytes in standard 32-bit float (FP32), whereas a 768-dimensional vector (Nomic / BGE) uses 3,072 bytes. When stored in-memory with HNSW graph indexes, every doubling of dimension doubles RAM footprint, which can push dedicated clusters into significantly higher pricing tiers.

What is the cost difference between Serverless and Dedicated Pods/Clusters?

Serverless vector databases (e.g. Pinecone Serverless, Cloudflare Vectorize, Astra DB) charge strictly per-gigabyte of storage and per-million Read Units (RUs). They scale to zero at minimal idle cost. Dedicated clusters (e.g. Qdrant Cloud, Pinecone Pods, Weaviate Dedicated) have fixed hourly floor costs ($9 to $70+/mo minimum) but provide unlimited queries within node RAM capacity, making them substantially cheaper under sustained high-QPS production traffic.

How does INT8 Scalar and Binary Quantization reduce vector search TCO?

Scalar Quantization (INT8) compresses 32-bit floats into 8-bit integers, reducing memory requirements by 75% with negligible accuracy drop (<1% recall loss). 1-Bit Binary Quantization compresses vectors up to 32x, allowing millions of embeddings to reside in minimal RAM on affordable VPS instances (e.g. Hetzner Cloud) rather than expensive multi-gigabyte managed clusters.

When should I choose pgvector over a specialized vector database?

pgvector (on PostgreSQL, Supabase, Neon, or self-hosted) is ideal when your vector count is under 10-20 million and vectors reside alongside existing relational business data (users, auth, metadata). It eliminates dual-database sync lag and allows single ACID transactions. Dedicated vector engines (Qdrant, Milvus/Zilliz, Pinecone) become advantageous above 20M+ vectors where specialized distributed indexing (HNSW, DiskANN) outpaces Postgres vacuuming and shared memory.

What is the memory overhead of HNSW indexing?

Hierarchical Navigable Small World (HNSW) builds multi-layer proximity graphs to achieve sub-10ms nearest neighbor search. The graph edges and adjacency lists typically add 1.4x to 2.0x storage overhead on top of the raw vector arrays. For 1M 1536-dim vectors (6.14GB raw), an HNSW index typically requires ~9.2GB to 12GB of combined RAM and high-speed NVMe.

Why is self-hosting on a VPS (e.g., Hetzner) often 10x cheaper?

Managed cloud providers bundle multi-tenant compute markup, automated failover, and high gross margins into their storage and RU rates. Running open-source Qdrant, Weaviate, or pgvector on a modern NVMe VPS (e.g. Hetzner CPX31 with 4 vCPU, 8GB RAM, 160GB NVMe for €14.60/mo) provides dedicated raw hardware capable of serving millions of vectors at a fraction of hyperscaler rates.