# Qdrant vs turbopuffer

The deciding difference is operational: Qdrant can run on infrastructure you control, turbopuffer cannot. If that constraint is real for you, it settles the choice before anything else is considered.

| | Qdrant | turbopuffer |
| --- | --- | --- |
| Licence | Open source | Proprietary |
| Pricing | freemium | usage based |
| Self-hostable | Yes | No |
| Languages | Python, TypeScript | Python, TypeScript |
| Install | — | — |
| Keys required | None | TURBOPUFFER_API_KEY |

## Full pages

- https://newagent.build/c/qdrant
- https://newagent.build/c/turbopuffer

## Machine interfaces

- `GET https://newagent.build/api/registry` — every component as JSON
- `GET https://newagent.build/api/vendors` — vendors, with the repo and releases feed to watch
- `GET https://newagent.build/api/advise?q=<plain english>` — recommended stack for a description
- `GET https://newagent.build/api/stack?<layer>=<id>&format=sh|json|md|yml|agents|env` — a stack as files
- `GET https://newagent.build/llms.txt` — the whole registry in one fetch

Any page here also returns markdown if you send `Accept: text/markdown`.