LanceDB vs turbopuffer
Of the 107 makers' products we know the vector database of, 8 chose turbopuffer (7%) and 3 LanceDB (3%). Among the 42 launched in 2025, LanceDB is in 0% and turbopuffer in 0%. They're different kinds of tool, embedded / local-first and managed vector store, so the counts don't measure the same choice.
Two sides of the vector database decision: embedded / local-first and managed vector store. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- An embedded vector database that stores vectors and data as files on local disk or object storage, with no server to run.
Use it whenYou want vectors in your app process or a serverless function, backed by S3-style storage.
Trade-offMany concurrent writers need care, and the managed cloud is a separate paid product.
- You want a hosted index with nothing to operate
Use it whenYou have many separate namespaces, such as one index per customer.
Trade-offNo free tier (paid plans have a monthly minimum), and it's cloud-only.
At a glance
| Used by | 3 makers' products · 47 open-source projects | 8 makers' products · 7 open-source projects |
|---|---|---|
| Cost at default usagevectors stored 1 million vectors, queries 1 million queries, vectors written or updated 500k writes | — | $21/mo Launch |
| Downloads | 1.5M/wk6× vs npm | 863.6k/wk3.5× vs npm |
| Pricing | Free (open source); LanceDB Cloud billed by usage, Enterprise by contract. | Usage-based tiers with a monthly minimum; higher tiers add SSO, audit logs, and enterprise/BYOC deployments. · paid from $16/mo minimum usage |
| Free tier | Yes | No |
| Open source | Yes · self-hostable | No |
| Incidents, 90 daysfrom its status page | no public status feed | 4 (4 major) |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for vector database.
| Framework | |||
|---|---|---|---|
| 3 | 4 | All 38 Next.js products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the vector database decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2024 | 0% 0 | 0% 0 | 28 |
| 2025 | 0% 0 | 0% 0 | 42 |
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- Storing vectors on object storage with a cache in front keeps large-scale search cheap. HNHN 2HN 3turbopuffer.com
- Handles hundreds of millions to billions of documents, a common next step when pgvector runs out. turbopuffer.comturbopuffer.com 2turbopuffer.com 3HN
- Operationally simple, with BM25, attribute filtering, recall tuning and consistency options built in. HNHN 2HN 3HN 4
Who uses each
What makers pair each with
Neither quite right?
See the whole vector database decision →Questions
LanceDB or turbopuffer: which do makers choose?
Of the 107 makers' products we know the vector database of, 8 chose turbopuffer (7%) and 3 LanceDB (3%). Among the 42 launched in 2025, LanceDB is in 0% and turbopuffer in 0%. They're different kinds of tool, embedded / local-first and managed vector store, so the counts don't measure the same choice. Choose LanceDB if an embedded vector database that stores vectors and data as files on local disk or object storage, with no server to run; choose turbopuffer if you want a hosted index with nothing to operate.
When should I pick turbopuffer over LanceDB?
Pick turbopuffer if: You want a hosted index with nothing to operate.

