Vector-database costs: size the collection before comparing plans
Picture 100 million 1,536-dimensional vectors stored as 32-bit floats. That's 614.4 GB of raw vector values before you add indexes, metadata or copies. Keep two copies and you're at 1,228.8 GB. Think of that number as the starting point for a vendor quote, not the finished database bill.
Side-by-Side Plan & Feature Comparison
| Plan Dimension | Pinecone | Qdrant |
|---|---|---|
| Starting Base Price | $20 / mo | $0 / mo |
| Billing Model | ✓ Fixed Monthly | ✓ Fixed Monthly |
| Free Tier Included | ✓ Starter: 2 GB storage; usage limits | ✓ Single node: 0.5 vCPU, 1 GB RAM, 4 GB disk |
| Quota & Overages | Flat fee; included usage limits | Single-node prototype capacity |
| Official Source | Official Rates ↗ | Official Rates ↗ |
Build a capacity sheet with explicit units
Before you start comparing pricing tiers, do a little back-of-the-napkin physics on your embedding collection: vectors × dimensions × bytes per value. Say you have 100,000,000 vectors at 1,536 dimensions (the size OpenAI text-embedding-3-small uses) stored as standard 4-byte single-precision floats. The raw vector data comes to 100,000,000 × 1,536 × 4 = 614,400,000,000 bytes, or exactly 614.4 decimal GB (about 572.2 GiB). One friendly tip: keep GB and GiB in separate columns when you match numbers against cloud rate cards, because they're different byte counts and the gap adds up fast.
| Raw vector representation | One copy | Two copies |
|---|---|---|
| 1,536 dimensions, four bytes per value | 614.4 GB | 1,228.8 GB |
| 768 dimensions, four bytes per value | 307.2 GB | 614.4 GB |
| 1,536 dimensions, two bytes per value | 307.2 GB | 614.4 GB |
What to keep in mind: this table covers pure, unindexed vector data and nothing else. A real production setup also stores document payloads (metadata, chunks, IDs), index graphs like HNSW, memory buffers, and replicas for high availability. Dropping to 768 dimensions or using scalar quantization (2 bytes per float) cuts the raw footprint in half, which is great. Just test retrieval accuracy and recall on your own data before you assume the smaller footprint searches as well as the bigger one.
Three buying routes, three quote checks
Pinecone builds its serverless billing around storage and read/write units. There's a flat $20/month Builder plan, and a Standard tier with a $50 minimum monthly commitment. The practical catch is that the minimum is a floor, not an extra fee: if your usage comes to $30, you pay $50, and if it's $80, you pay $80. Before you deploy, confirm your project's read units and namespace requirements.
Qdrant's free cloud tier gives you a single cluster node with 1GB RAM and 4GB disk. That's lovely for prototyping and nowhere near enough for a 614.4GB collection. For the real thing, size a managed multi-node cluster or a self-hosted deployment, depending on whether your vectors live in memory or are memory-mapped to disk on fast SSDs.
Weaviate has a sandbox environment limited to 100,000 objects, and production Serverless Flex starts at $45/month. Its pricing calculator sizes clusters from dimensions, object counts, and payload sizes. So plug in your actual parameters and let the calculator do the work, rather than leaning on entry-tier marketing figures.
Reads and ingestion belong beside storage
Storage is just one line on your monthly vector database invoice. You'll also want to budget for initial data ingestion, update frequency, queries per second (QPS), and complex metadata filtering. A static archive handling 10 queries a minute has very different infrastructure needs than a real-time semantic search engine serving 500 concurrent lookups with sub-50ms latency SLAs.
In a full RAG pipeline you'll also pay upstream embedding API fees (OpenAI or Cohere, for example) plus downstream reranking or LLM generation charges. Keep database infrastructure separate from model inference lines in your budget, and watch for double-counting embedding costs if you're on a managed platform bundle.
A pilot should test retrieval, not just insertion
Set up a realistic benchmark with 50 to 100 difficult test queries, golden retrieval targets, and realistic filter conditions. Measure search latency under peak concurrency, and check how often the right document chunk shows up in the top-k results. A cheap setup that can't retrieve relevant context ends up costing you more downstream, in confused LLM answers and human support tickets.
If you're self-hosting Qdrant or Weaviate on AWS or GCP, give yourself credit for the engineering time: cluster patching, index backups, monitoring, and failover all take real hours. With managed cloud databases, check regional availability so network latency stays low between your application servers and your vector storage.
Use the worksheet as a storage component, not a provider invoice
Our interactive worksheet uses an illustrative $0.20 per GB-month baseline for scenario planning. Across two copies of the raw 614.4GB baseline (1,228.8 GB total), that works out to a $245.76 monthly storage allocation. Use it to play with dimension and replication trade-offs, then layer on your read throughput and any vendor minimums to get to a complete production budget.
Explore the storage component
Defaults are a raw-vector capacity calculation and an illustrative storage rate, not a provider quote. Add index/payload capacity before budgeting production. The copy count must match what the selected rate covers. This worksheet does not apply invoice minimums.
Plan and rate reference
Include retrieval in your application margin →