The deciding difference is operational: Chroma can run on infrastructure you control, turbopuffer cannot. If that constraint is real for you, it settles the choice before anything else is considered.
Embedded vector store that runs in-process. Ideal first index.
Vector and full-text search on object storage — very cheap at rest.
| Chroma | turbopuffer | |
|---|---|---|
| Licence | Open source | Proprietary |
| Pricing | open source | usage based |
| Self-hostable | Yes | No |
| Languages | Python, TypeScript | Python, TypeScript |
| Install | pip install chromadb | — |
| Keys required | None | TURBOPUFFER_API_KEY |
The deciding difference is operational: Chroma can run on infrastructure you control, turbopuffer cannot. If that constraint is real for you, it settles the choice before anything else is considered. Chroma: Embedded vector store that runs in-process. Ideal first index. turbopuffer: Vector and full-text search on object storage — very cheap at rest.
Chroma can run on your own infrastructure. turbopuffer is a hosted service only.
Chroma is open source (open source). turbopuffer is proprietary (usage based).
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/chroma-vs-turbopuffer