Select all dimensions that meaningfully drive cost on a managed vector database bill in 2026.

Attempt it

Quick reference

TL;DR

Four real cost axes: storage (vectors × dim), reads (QPS), writes (upserts), and replication tier. Distance metric and naming convention are distractors.

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Think of a managed vector database the way you would think of renting warehouse space plus paying for the trucks that load and unload it. The space charge depends on how many boxes you store and how big each box is: that is the vectors × dimension axis. The truck charges depend on how often you ship things out (queries) and how often you ship things in (upserts). And if you ask for a second warehouse in another city as backup, that doubles the bill. Which color you paint the warehouse, or what specific way the trucks weigh the boxes, does not change the rent. Those are the distractors in the question.

Key concepts

Cost modeling

Quick scan · 2–4 min

Everything important, quickly.

4 min: the four cost axes (storage, reads, writes, replication), why dimension dominates storage, why upserts cost more than reads, and why distance metric is not a billing axis.

Side-by-side

Cost axis	What drives it	Typical knob
Storage	vectors × dimension × bytes_per_dim	Compress vectors via PQ or BQ
Reads (QPS)	Per-query candidate count × distance compute	Lower ef_search / nprobe
Writes (upserts)	Per-upsert index maintenance cost	Bulk-load offline, avoid bursty inserts
Replication	Replica multiplier across all other axes	Match tier to RPO/RTO requirements

Real-world examples

Real products, models, and research that use this idea.

Pinecone Serverless prices storage per vector-month with a dimension multiplier, plus separate read and write unit charges, plus multi-AZ tier multiplier.
Turbopuffer publishes a gigabyte-month storage price plus a per-query price plus a per-vector-write price; the four axes are explicit in the pricing page.
Qdrant Cloud sizes clusters by RAM, which is dominated by `vectors × dim × bytes`; the cluster size determines both storage capacity and read throughput.
Weaviate Cloud bills by serverless capacity units that bundle storage and throughput, with the same four underlying drivers.
pgvector on a managed Postgres instance bills by Postgres compute and storage, which still resolves to the same four axes once you size the database.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QHow would you estimate the read-unit cost of a query on HNSW versus IVF at the same recall target?

Sign in or go Pro to see the approach for this follow-up.

QWhen would a multi-region replication tier be worth the 3x cost premium?

Sign in or go Pro to see the approach for this follow-up.

QHow does PQ compression interact with the read-unit cost?

Sign in or go Pro to see the approach for this follow-up.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.