Vector Database for Next.js: what 38 makers' products chose
Among 38 makers' products built with Next.js that we know the vector database of, Pinecone leads: 19 of them (50%). Next come Chroma (6) and Qdrant (5).
Inside the database you already run, or a separate vector store. pgvector keeps vectors next to your rows, with one backup and one query language, but tuning large indexes is on you. A dedicated vector store handles scale, filtering and hybrid search for you, at the cost of another service to sync data into.
What makers on Next.js chose
| Option | Next.js products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 19 (50%) | 50% | ~3,300 users | $113/moStandard | |
| 6 (16%) | 11% | ~760 users | $51/moStarter | |
| 5 (13%) | 17% | ~1,000 users | $103/moStandard (3 nodes, 0.5 vCPU / 4 GiB each) | |
| 4 (11%) | 7% | None | $21/moLaunch | |
| 3 (8%) | 3% | — | — | |
| 2 (5%) | 15% | ~1,000 users | $253/moFlex | |
| 1 (3%) | 1% | — | — |
Live makers' products with a source for both: that they're built with Next.js, and what they use for vector database. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You already use Postgres and have up to a few million vectors
pgvector 1 here
- You're prototyping retrieval on your laptop, or want vectors in files with no server
Chroma 6 here - You want a hosted index with nothing to operate
Pinecone 19 here
turbopuffer 4 here - You need an open-source store with heavy filtering or hybrid search, self-hosted or managed
Qdrant 5 here
Weaviate 2 here
Pinecone
Managed vector store19 Next.js products here (50%). Free up to about 3,300 users. About $113 a month at 10,000 users (Standard).
llms.txtBest forA fully hosted index with nothing to operate, sized by usage.
Trade-offClosed source and cloud-only, so leaving means re-indexing somewhere else.
“Vector database for semantic search and RAG pipelines. 200K+ vectors for CDC documents, account context memory, and knowledge retrieval in milliseconds.”
- Getting started is quick, with clear documentation and a generous free tier. 4 sources
- Handles large vector volumes with low latency as usage grows. 2 sources
- It is one more database to run and sync, when Postgres or plain search often covers the need. 4 sources
- Its core features have become a commodity, and it was late to integrated embeddings compared with rivals. 4 sources
Status page: 8 incidents in the last 90 days, 6 major (its own page, 2026-10-19).
“Vector search over UI snapshots pulled from replays”
Vector DatabaseMaker says so +1 · source ↗“The ability to query and rerank in one api call did it for me.”
Vector DatabaseMaker says so +1 · source ↗“One of the best vector databases and easy to work with.”
Vector DatabaseMaker says so · source ↗“Our context engineering infrastructure is built with Pinecone. They made it super easy to scale high-performance vector search applications.”
Vector DatabaseMaker says so · source ↗“A huge shout out to the Pinecone Engineering, Data Science, and Partner teams. We are so excited to be working with you and cleaning up the world's data mess with Fleak & Pinecone! Join us on 8/22 for Pinecone&Fleak workshop for reranking: https://www.pinecone.io/communit...”
Vector DatabaseMaker says so · source ↗“Super simple to get started, documentation was amazing.”
Vector DatabaseMaker says so · source ↗“Pinecone has made it super easily to store massive amounts of vectors and their new serverless tier is very cost effective.”
Vector DatabaseMaker says so · source ↗“Used for vectorization and vector database, which helps in maintaining the meta properties efficiently.”
Vector DatabaseMaker says so · source ↗“Helps us build a scalable and agentic AI infrastructure.”
Vector DatabaseMaker says so · source ↗“We rely on Pinecone to enhance Lambda's AI-driven data insights and semantic search capabilities. Its scalable and efficient vector database allows us to manage and query large datasets with precision, enabling intelligent search and personalized recommendations.”
Vector DatabaseMaker says so · source ↗
Chroma
Embedded / local-first6 Next.js products here (16%). Free up to about 760 users. About $51 a month at 10,000 users (Starter).
llms.txtBest forPrototyping RAG on your laptop with a pip or npm install and no server to run.
Trade-offFor production you either run its server yourself or move to Chroma Cloud.
“Jeff (the founder) is incredible - super knowledgeable and I'm super bullish on the direction of the product. Let's go!”
- Open source and easy to self-host, with a simple API that gets embeddings stored quickly. 2 sources
- Full-text and regex search sit alongside vector search, and collection forking suits changing code. 4 sources
- Its feature set is narrower than Milvus or Weaviate, lacking vector quantization and some index options. 2 sources
“One of the best vectorDB out there. Easy and opensource”
Vector DatabaseMaker says so · source ↗“Easy to use, fast, customizable”
Vector DatabaseMaker says so · source ↗“Jeff (the founder) is incredible - super knowledgeable and I'm super bullish on the direction of the product. Let's go!”
Vector DatabaseMaker says so · source ↗“Fast, simple and open source”
Vector DatabaseMaker says so · source ↗
Qdrant
Open-source vector store5 Next.js products here (13%). Free up to about 1,000 users. About $103 a month at 10,000 users (Standard (3 nodes, 0.5 vCPU / 4 GiB each)).
llms.txtBest forHeavy metadata filtering alongside vector search, self-hosted from one binary or on its managed cloud.
Trade-offOne more service to deploy and keep in sync with your main database.
“Thanks to Qdrant, we utilize it as a vector database to store our knowledge base and uploaded file data. Our RAG would not be possible without it.”
- It is fast and scales with strong price-performance, helped by its Rust core. 1 source
- Payload filtering and hybrid semantic plus boolean search work together. 1 source
- As a separate server it is slower than in-process stores for small local datasets. 1 source
- Setting up and operating a vector database is overkill for teams that just need working search. 2 sources
“We evaluated a bunch of vector DBs—and Qdrant stood out for its blazing speed, filtering, and hybrid search. It's the unsung hero that lets our AI agents recall and reason across docs, CRMs, and conversations in milliseconds.”
Vector DatabaseMaker says so · source ↗“Thanks to Qdrant, we utilize it as a vector database to store our knowledge base and uploaded file data. Our RAG would not be possible without it.”
Vector DatabaseMaker says so · source ↗“Vector database enabling fast semantic search and retrieval of coding memories.”
Vector DatabaseMaker says so · source ↗“Amazing infrastructure for creating complex RAG system. Thank you”
Vector DatabaseMaker says so · source ↗“Qdrant is easy to use, fastembed is our favorite tool and developer documentation is no match.”
Vector DatabaseMaker says so · source ↗
turbopuffer
Managed vector store4 Next.js products here (11%). About $21 a month at 10,000 users (Launch).
llms.txtBest forVery large or many-tenant indexes where storing everything on object storage keeps cost down.
Trade-offNo free tier (paid plans have a monthly minimum), and it's cloud-only.
- Storing vectors on object storage with a cache in front keeps large-scale search cheap. 4 sources
- Handles hundreds of millions to billions of documents, a common next step when pgvector runs out. 4 sources
- There is no offline local emulator, so development and CI must hit the hosted service. 3 sources
- Its paid-only pricing floor is steep for small projects, which often stay on pgvector instead. 2 sources
Status page: 4 incidents in the last 90 days, 4 major (its own page, 2026-10-19).
LanceDB
Embedded / local-first3 Next.js products here (8%).
llms.txtBest forAn embedded vector database that stores vectors and data as files on local disk or object storage, with no server to run.
Trade-offMany concurrent writers need care, and the managed cloud is a separate paid product.
Weaviate
Open-source vector store2 Next.js products here (5%). Free up to about 1,000 users. About $253 a month at 10,000 users (Flex).
llms.txtBest forHybrid search that mixes keyword and vector results, with built-in modules that can create embeddings for you.
Trade-offMore concepts and configuration to learn than simpler stores; some advanced features need a license key.
“Lightning fast and personalised support for every query. They've helped us brainstorm some architecture level things.”
- Open source and free to run, with good docs and an active, friendly community. 4 sources
- Scales to production workloads, including multi-tenant setups on its managed cloud. 4 sources
- Search can be slow, with metadata filtering hurting vector query performance and hosted retrieval latency complaints. 2 sources
“Lightning fast and personalised support for every query. They've helped us brainstorm some architecture level things.”
Vector DatabaseMaker says so · source ↗“Weaviate is amazing! It lets us manage the data at scale when we need and how we need it.”
Vector DatabaseMaker says so · source ↗Also chosen, and not seen yet
Fewer Next.js products here: pgvector (1).
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Next.js.
- Qdrant → pgvector 9 pull requests
- Chroma → pgvector 7 pull requests
- Chroma → Pinecone 6 pull requests
- Chroma → Qdrant 4 pull requests
- pgvector → Pinecone 3 pull requests
- Pinecone → Qdrant 3 pull requests
Getting vector database right
If you already use Postgres, start with pgvector; most solo apps never outgrow it. Store the source text and metadata next to each vector so you can filter and re-embed later. Move to a dedicated store only when you hit a real limit — millions of vectors, slow filtered queries, or hybrid search you can't build yourself.
- Storing only vectors and IDs, then having to re-fetch and re-embed everything when you want to filter by date, user or source.
- Forgetting to delete or update vectors when the source record changes, so search keeps returning content users already removed.
- Adding a separate vector service to sync before trying the vector search in the database you already run.
The rest of the Next.js stack
What makers' Next.js products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 1,078 of 1,312
- Transactional Email: Resend 493 of 830
- Database: Supabase 171 of 382
- Payments: Stripe 288 of 359
- LLM API: OpenAI API 222 of 301
- Authentication: Clerk 176 of 211
- Web Analytics: Google Analytics 105 of 197
- Product Analytics: PostHog 123 of 168
Questions
What do most Next.js apps use for vector database?
Among 38 makers' products built with Next.js that we know the vector database of, Pinecone leads: 19 of them (50%). Next come Chroma (6) and Qdrant (5).
What does vector database cost for a Next.js app with 10,000 users?
On our usage model at 10,000 users, Pinecone comes to about $113 a month (Standard); Chroma comes to about $51 a month (Starter); Qdrant comes to about $103 a month (Standard (3 nodes, 0.5 vCPU / 4 GiB each)); turbopuffer comes to about $21 a month (Launch). Prices are from each vendor's pricing page.
Which vector database option stays free longest for a Next.js app?
Pinecone: on our usage model its cheapest plan stays free up to about 3,300 users.
How this is counted: a product is on Next.js when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its vector database. How evidence is collected.