Turbopuffer is a serverless search engine that combines vector and full-text search on top of cloud object storage, aimed at teams building AI products that need to retrieve context from very large corpora without paying to keep every index hot in RAM. It was co-founded by Simon Hørup Eskildsen and Justine Li, who met at Shopify while scaling its infrastructure , and it now sits behind retrieval in products like Cursor, Notion, Linear, and Superhuman . The pitch behind this "search every byte" launch is straightforward: an AI product is only as useful as the data it can actually reach at query time, and most stacks quietly cap that surface because keeping petabytes searchable is either too slow or too expensive.
The architectural bet is to store data durably in object storage (S3, GCS, or Azure Blob) and pull it into NVMe SSD cache or RAM only when queried , which Google Cloud describes as roughly 90% cheaper than traditional approaches . That tradeoff is what makes "search all your data" plausible for workloads that would otherwise be pruned or sharded aggressively. On the Cursor deployment, unlimited namespaces let the infrastructure team stop manually balancing codebase indexes across servers , and Notion warms a namespace cache when a user opens the Q&A dialog so subsequent queries are fast , illustrating the two shapes of workload the system is tuned for.
This launch matters right now because retrieval quality has become the visible ceiling on agent and copilot performance, and infra teams are re-evaluating first-generation vector databases on cost as usage scales into billions of vectors. Turbopuffer is positioning itself as the default retrieval layer for that transition, with production references ( the engine already hosts more than a trillion documents and serves tens of thousands of queries per second ) meant to reassure founders and operators that the object-storage approach holds up under real load.
Comments (9)
Sign in to join the discussion.
N
Nadia KowalczykSep 11, 2026
the cow mascot is doing more marketing lifting than most seed-stage founders. whoever animated that deserves equity.
K
Krish V.Sep 11, 2026
cute tagline but 'search every byte' is a big claim when half the demos I see are pre-indexed toy corpora. what happens at a real customer's messy 40TB blob store?
Y
Yuki FujimotoSep 11, 2026
p99 latency at what recall though. every vector db pitch skips that slide and I've stopped being polite about it.
P
priya shipsSep 11, 2026
landing page loads fast, docs are one click from the fold, cow is unhinged. this is how you launch.
O
Olumide R.Sep 11, 2026
would love to see hybrid search + a native reranker slot in the roadmap. also filters on nested json without me writing a novel.
B
Ben H.Sep 11, 2026
any infra teams here hiring? got a distributed systems eng in Berlin who's been benchmarking every vector store on the market for fun.
M
Marc DelacroixSep 11, 2026
reminds me of what an early portfolio co of mine tried to build in 2022 before pivoting to agents. good to see someone actually shipping the storage layer instead of another wrapper.
A
amaraSep 11, 2026
gross margin on object-storage-backed vector search is the whole question. tell me retention past month 6 before I tell you it's interesting.
T
Tomáš RudaSep 11, 2026
still running postgres full text and it works fine for our 8 users. wake me when the cow does BM25.
Work With Us
Book an intro call to explore our suite of services. We might have a waitlist.
Turbopuffer
search every byte
search every byte
Tags
TLVC Rating
Community Rating
No ratings yet
to rate this launch.
Turbopuffer is a serverless search engine that combines vector and full-text search on top of cloud object storage, aimed at teams building AI products that need to retrieve context from very large corpora without paying to keep every index hot in RAM. It was co-founded by Simon Hørup Eskildsen and Justine Li, who met at Shopify while scaling its infrastructure , and it now sits behind retrieval in products like Cursor, Notion, Linear, and Superhuman . The pitch behind this "search every byte" launch is straightforward: an AI product is only as useful as the data it can actually reach at query time, and most stacks quietly cap that surface because keeping petabytes searchable is either too slow or too expensive. The architectural bet is to store data durably in object storage (S3, GCS, or Azure Blob) and pull it into NVMe SSD cache or RAM only when queried , which Google Cloud describes as roughly 90% cheaper than traditional approaches . That tradeoff is what makes "search all your data" plausible for workloads that would otherwise be pruned or sharded aggressively. On the Cursor deployment, unlimited namespaces let the infrastructure team stop manually balancing codebase indexes across servers , and Notion warms a namespace cache when a user opens the Q&A dialog so subsequent queries are fast , illustrating the two shapes of workload the system is tuned for. This launch matters right now because retrieval quality has become the visible ceiling on agent and copilot performance, and infra teams are re-evaluating first-generation vector databases on cost as usage scales into billions of vectors. Turbopuffer is positioning itself as the default retrieval layer for that transition, with production references ( the engine already hosts more than a trillion documents and serves tens of thousands of queries per second ) meant to reassure founders and operators that the object-storage approach holds up under real load.
Comments (9)
the cow mascot is doing more marketing lifting than most seed-stage founders. whoever animated that deserves equity.
cute tagline but 'search every byte' is a big claim when half the demos I see are pre-indexed toy corpora. what happens at a real customer's messy 40TB blob store?
p99 latency at what recall though. every vector db pitch skips that slide and I've stopped being polite about it.
landing page loads fast, docs are one click from the fold, cow is unhinged. this is how you launch.
would love to see hybrid search + a native reranker slot in the roadmap. also filters on nested json without me writing a novel.
any infra teams here hiring? got a distributed systems eng in Berlin who's been benchmarking every vector store on the market for fun.
reminds me of what an early portfolio co of mine tried to build in 2022 before pivoting to agents. good to see someone actually shipping the storage layer instead of another wrapper.
gross margin on object-storage-backed vector search is the whole question. tell me retention past month 6 before I tell you it's interesting.
still running postgres full text and it works fine for our 8 users. wake me when the cow does BM25.