Workflows
How to Choose a Vector Database for RAG
For small RAG projects, the best vector database is often the one your team can operate and evaluate correctly.
Editorial review
AI tools, model releases, pricing, licenses, and platform terms can change quickly. Verify the official source before production or commercial use.
Who this is for
Builders adding document retrieval to a local or internal AI app.
Recommended stack
- Chroma for learning
- pgvector for Postgres teams
- Qdrant for filtered retrieval
- Weaviate or Milvus for larger platforms
Prototype path
Chroma is a fast local starting point. pgvector is convenient if Postgres is already in your stack.
Production path
Qdrant, Weaviate, and Milvus are worth testing when retrieval features and operations matter.
Practical recommendations
- Keep source document IDs
- Store metadata cleanly
- Add reranking when retrieval quality matters
Tradeoffs
Vector databases do not fix weak embeddings, bad chunking, or missing rerankers.
Related links
FAQ
Do I need a vector database for every chatbot?
No. Simple chat over no documents does not need vector search.
Sources
Next steps
Use the model and tool directories to choose the concrete pieces for your local AI stack, then move into stack recipes or related guides when you are ready to build.