Both are open source retrieval options with comparable terms, so the choice comes down to which model of the problem you prefer — compare the descriptions below rather than the licence.
Vector search inside the Postgres you already run.
Correct default under roughly ten million vectors. Reach for a dedicated store when it stops being.
Embedded vector store that runs in-process. Ideal first index.
| pgvector | Chroma | |
|---|---|---|
| Licence | Open source | Open source |
| Pricing | open source | open source |
| Self-hostable | Yes | Yes |
| Languages | Any language | Python, TypeScript |
| Install | — | pip install chromadb |
| Keys required | None | None |
Both are open source retrieval options with comparable terms, so the choice comes down to which model of the problem you prefer — compare the descriptions below rather than the licence. pgvector: Vector search inside the Postgres you already run. Chroma: Embedded vector store that runs in-process. Ideal first index.
pgvector can run on your own infrastructure. Chroma can run on your own infrastructure.
pgvector is open source (open source). Chroma is open source (open source).
Every page here answers to Accept: text/markdown and returns the same content at roughly a tenth the tokens. No separate site, no toggle — same URL.
curl -s -H "Accept: text/markdown" https://newagent.build/compare/pgvector-vs-chroma