t

turbopuffer

by turbopuffer Inc.

Data & AnalyticsInfrastructure & CloudEnterprise Search & KnowledgeDeveloper Tools

Vector and full-text search built object-storage-first, at roughly a tenth the cost of RAM-resident vector databases

Usage-based · Subscription·Added Aug 20, 2026·Updated Aug 20, 2026
Share:
THE DAILY BRIEF
turbopuffer

by turbopuffer Inc.

Data & AnalyticsInfrastructure & CloudEnterprise Search & KnowledgeDeveloper Tools

Vector and full-text search built object-storage-first, at roughly a tenth the cost of RAM-resident vector databases

Usage-based · Subscription

turbopuffer is a vector and full-text search database built object-storage-first, aimed at engineering teams running retrieval for AI products at very large scale. It keeps S3 or Google Cloud Storage as the single source of truth and uses memory and NVMe SSD only as a cache tier, which removes the cost of holding an entire index in provisioned RAM and makes enormous multi-tenant corpora economically viable.

At a Glance

Category
Data & Analytics
Pricing
Usage-based, Subscription
Target Market
CTOs, Enterprise Developers, Platform Engineers, Data Scientists, ML Engineers
Deployment
Cloud-first, API-based, Hybrid
Founded
2023
Headquarters
Ottawa, Canada
Team Size
11-50

Key Features

  • Object-storage-native architecture
  • Hybrid vector, BM25 and regex search
  • Namespace-per-tenant multi-tenancy
  • Copy-on-write branching
  • Consumption-metered pricing with no platform fee
  • Customer-managed encryption and private networking
  • Five official SDKs generated from one API spec

Capabilities

text generation
image generation
video generation
code generation
workflow automation
api access
audio generation
fine tuning
agent orchestration

Use Cases

  • AI coding assistant code retrieval
  • In-product AI search over customer workspaces
  • Enterprise RAG over large document corpora
  • Email and communication search
  • Cost-driven migration off provisioned vector databases

Ideal For

Best For

  • Multi-tenant RAG and semantic search where each customer needs an isolated namespace and the tenant count runs into the millions
  • Codebase and document indexing for AI coding assistants and knowledge products with unevenly accessed corpora
  • Hybrid retrieval that needs vector similarity, BM25 keyword ranking and regex filtering from one engine
  • Archival or long-tail corpora where most data is queried rarely and paying to keep it in RAM is uneconomic
  • Teams replacing a provisioned-node vector database whose bill has outgrown the value of the workload

Not Ideal For

  • Applications that need guaranteed sub-10ms latency on every query regardless of access pattern — a cold query against uncached data measures p90 of about 1,214ms on 1M documents, and cold-start latency averages roughly 444ms
  • Write-then-read-immediately workflows: writes go straight to object storage at 100-250ms (p90 248ms for a 512KB upsert), so sub-second read-your-writes consistency is not on offer
  • High-transaction OLTP paths such as checkout or ledger systems, which the object-storage design is explicitly not built for
  • Highly personalised ranking with heavy fan-out, where cold fetches degrade p90 and p95 tail latency
  • Teams wanting a free tier or a self-hosted open-source deployment — the entry plan starts at a $16/month minimum and the engine is proprietary

Market Analysis

Developer-firstEnterprise-gradeCost-optimized at scale

Pros

  • Dramatically lower cost at large scale than RAM-resident vector databases, with a February 2026 rate cut taking queries from $5/PB to $1/PB
  • Marquee production references at genuinely extreme scale (Cursor, Anthropic, Notion, Linear, Atlassian) rather than pilot logos
  • Hybrid vector, keyword and regex retrieval in one system reduces the operational surface compared with running two engines
  • Warm-query latency is competitive at under 10ms p50 despite the object-storage backing
  • Five official SDKs generated from a single API spec keep language clients consistent

Cons

  • Cold queries against uncached data are slow — roughly 300-500ms typical and p90 of about 1,214ms on 1M documents — which is a recurring practitioner complaint in Hacker News discussion
  • Write latency of 100-250ms means there is no sub-second write-then-read consistency, ruling out workflows that need immediate visibility
  • Cold fetches hurt p90 and p95 in fan-out workloads, making it a poorer fit for highly personalised ranking than for archival or generic retrieval
  • No free tier and no open-source or self-hosted option; enterprise controls such as BYOC, CMEK and private networking start at $4,096/month
  • Sacra flags high customer concentration and notes that the object-storage architecture is being copied by competitors, eroding the cost moat

Pricing

Launch

From $16/mo

  • All database features
  • Multi-tenant deployment
  • Community Slack and email support

Scale

From $256/mo

  • Everything in Launch
  • HIPAA-ready BAA
  • Single sign-on
  • Audit logs (audit log streams +$128/mo)
  • IP allowlisting
  • Private Slack channel, 8-5 support

Enterprise

From $4,096/mo

  • Single-tenancy and BYOC deployment
  • Private networking
  • CMEK per namespace
  • 24/7 support with 99.95% uptime SLA
  • 35% usage premium applies

There is no free tier. Pricing is pure consumption metered against a monthly tier minimum — customers pay the greater of usage or the floor, which is $16 on Launch (cut from $64 in June 2026), $256 on Scale and $4,096 on Enterprise, where a 35% usage premium also applies. Published rates are up to $0.33 per GB-month of storage, up to $2.00 per GB written (copy_from_namespace operations get a 50% write discount), and $1 per petabyte scanned on queries with volume discounts of 80% above 32GB scanned and 96% above 128GB, subject to a 1.28GB minimum billable scan per query. The query rate was cut from $5/PB to $1/PB in February 2026. HIPAA BAA and SSO require Scale; BYOC, single-tenancy, private networking and CMEK are gated behind Enterprise at $4,096/month or more.

Security & Compliance

soc2
gdpr
hipaa
iso27001
sso
data residency

THE DAILY BRIEF

Enterprise AI insights for technology and business leaders, twice weekly.

beri.net

Subscribe at beri.net/subscribe for twice-weekly AI insights delivered to your inbox.

LinkedIn: linkedin.com/in/rberi  |  X: x.com/rajeshberi

© 2026 Rajesh Beri. All rights reserved.

turbopuffer is a vector and full-text search database built object-storage-first, aimed at engineering teams running retrieval for AI products at very large scale. It keeps S3 or Google Cloud Storage as the single source of truth and uses memory and NVMe SSD only as a cache tier, which removes the cost of holding an entire index in provisioned RAM and makes enormous multi-tenant corpora economically viable.

turbopuffer is a search and retrieval database that treats object storage — S3 or Google Cloud Storage — as the single source of truth, with memory and NVMe SSD acting only as a cache tier. That inversion of the usual in-memory vector database design is the entire product thesis: because cold data lives in object storage rather than provisioned RAM, turbopuffer meters what customers actually consume instead of charging per node or per gigabyte of provisioned memory, and the company advertises roughly an order of magnitude lower cost than RAM-resident alternatives. A single engine serves vector search at over 90% recall, BM25 full-text ranking, regex via trigram indexes, and metadata filtering, so hybrid retrieval does not require running two systems side by side. The documented production envelope is 1 trillion-plus documents, 10 million-plus writes per second, 25,000-plus queries per second and up to 256TB per namespace, with copy-on-write branching and customer-managed encryption keys available per namespace. Founded in 2023 by former Shopify infrastructure engineers Simon Hørup Eskildsen and Justine Li and based in Ottawa, Canada, turbopuffer took a small angel round from Lachy Groom in early 2024 and an undisclosed seed round with Thrive Capital in December 2025. Its namespace-per-tenant model made it the default retrieval layer for AI-native products with very large multi-tenant corpora: Cursor indexes more than a trillion chunks of code across over 80 million namespaces, and Anthropic, Notion, Linear, Atlassian, Ramp, Grammarly, Harvey, TELUS and Superhuman are named production customers.

Ideal Buyer

The platform or infrastructure engineering team behind a multi-tenant AI product, whose vector index has grown large enough that provisioned-RAM pricing on Pinecone or Weaviate has become the dominant line item in the retrieval budget.

Key Benefit

Retrieval cost that scales with data volume in object storage rather than with provisioned memory — the query rate alone was cut from $5/PB to $1/PB in February 2026, up to 94% cheaper for the largest namespaces.

At a Glance

Category
Data & Analytics
Pricing
Usage-based, Subscription
Target Market
CTOs, Enterprise Developers, Platform Engineers, Data Scientists, ML Engineers
Deployment
Cloud-first, API-based, Hybrid
Founded
2023
Headquarters
Ottawa, Canada
Team Size
11-50

Key Features

  • Object-storage-native architecture

    S3 or GCS is the sole source of truth with memory and NVMe SSD as a cache layer, so storage cost tracks object storage rates instead of provisioned RAM

  • Hybrid vector, BM25 and regex search

    Vector search at over 90% recall, full-text BM25 ranking and trigram-indexed regex run in one engine, removing the need to operate a second search system

  • Namespace-per-tenant multi-tenancy

    Up to 256TB per namespace and tens of millions of namespaces per account, which is how Cursor isolates more than 80 million customer codebases

  • Copy-on-write branching

    Namespaces can be branched cheaply for testing index changes or re-embedding runs without duplicating the underlying stored data

  • Consumption-metered pricing with no platform fee

    Charges are storage per GB-month, writes per GB and queries per petabyte scanned, so idle data costs almost nothing rather than holding a paid node

  • Customer-managed encryption and private networking

    CMEK per namespace, IP allowlisting, audit log streams and private networking are available for regulated enterprise deployments

  • Five official SDKs generated from one API spec

    Python, TypeScript, Java, Go and Ruby clients are Stainless-generated from a single spec, so language clients stay consistent as the API evolves

Capabilities

text generation
image generation
video generation
code generation
workflow automation
api access
audio generation
fine tuning
agent orchestration

Use Cases

  • AI coding assistant code retrieval

    Cursor indexes over a trillion chunks of code across more than 80 million namespaces so each developer's repository stays isolated and searchable

  • In-product AI search over customer workspaces

    Notion migrated from Pinecone to power Notion AI, and Linear runs issue search on it, both requiring per-workspace isolation at scale

  • Enterprise RAG over large document corpora

    First-stage retrieval narrows millions of documents down to dozens or hundreds before a reranker or LLM sees them, which is the pattern the engine is tuned for

  • Email and communication search

    Superhuman uses it for email search, where each mailbox is a separate namespace and most historical mail is queried rarely

  • Cost-driven migration off provisioned vector databases

    Teams whose Pinecone or Weaviate bill scales with index size in RAM move to object-storage economics without giving up hybrid search

Ideal For

Best For

  • Multi-tenant RAG and semantic search where each customer needs an isolated namespace and the tenant count runs into the millions
  • Codebase and document indexing for AI coding assistants and knowledge products with unevenly accessed corpora
  • Hybrid retrieval that needs vector similarity, BM25 keyword ranking and regex filtering from one engine
  • Archival or long-tail corpora where most data is queried rarely and paying to keep it in RAM is uneconomic
  • Teams replacing a provisioned-node vector database whose bill has outgrown the value of the workload

Not Ideal For

  • Applications that need guaranteed sub-10ms latency on every query regardless of access pattern — a cold query against uncached data measures p90 of about 1,214ms on 1M documents, and cold-start latency averages roughly 444ms
  • Write-then-read-immediately workflows: writes go straight to object storage at 100-250ms (p90 248ms for a 512KB upsert), so sub-second read-your-writes consistency is not on offer
  • High-transaction OLTP paths such as checkout or ledger systems, which the object-storage design is explicitly not built for
  • Highly personalised ranking with heavy fan-out, where cold fetches degrade p90 and p95 tail latency
  • Teams wanting a free tier or a self-hosted open-source deployment — the entry plan starts at a $16/month minimum and the engine is proprietary

Integrations

SDK Available
SDK:PythonTypeScriptJavaGoRuby

Deployment

On-Premise

Market Analysis

Developer-firstEnterprise-gradeCost-optimized at scale

Pros

  • Dramatically lower cost at large scale than RAM-resident vector databases, with a February 2026 rate cut taking queries from $5/PB to $1/PB
  • Marquee production references at genuinely extreme scale (Cursor, Anthropic, Notion, Linear, Atlassian) rather than pilot logos
  • Hybrid vector, keyword and regex retrieval in one system reduces the operational surface compared with running two engines
  • Warm-query latency is competitive at under 10ms p50 despite the object-storage backing
  • Five official SDKs generated from a single API spec keep language clients consistent

Cons

  • Cold queries against uncached data are slow — roughly 300-500ms typical and p90 of about 1,214ms on 1M documents — which is a recurring practitioner complaint in Hacker News discussion
  • Write latency of 100-250ms means there is no sub-second write-then-read consistency, ruling out workflows that need immediate visibility
  • Cold fetches hurt p90 and p95 in fan-out workloads, making it a poorer fit for highly personalised ranking than for archival or generic retrieval
  • No free tier and no open-source or self-hosted option; enterprise controls such as BYOC, CMEK and private networking start at $4,096/month
  • Sacra flags high customer concentration and notes that the object-storage architecture is being copied by competitors, eroding the cost moat

Pricing

Launch

From $16/mo

  • All database features
  • Multi-tenant deployment
  • Community Slack and email support

Scale

From $256/mo

  • Everything in Launch
  • HIPAA-ready BAA
  • Single sign-on
  • Audit logs (audit log streams +$128/mo)
  • IP allowlisting
  • Private Slack channel, 8-5 support

Enterprise

From $4,096/mo

  • Single-tenancy and BYOC deployment
  • Private networking
  • CMEK per namespace
  • 24/7 support with 99.95% uptime SLA
  • 35% usage premium applies

There is no free tier. Pricing is pure consumption metered against a monthly tier minimum — customers pay the greater of usage or the floor, which is $16 on Launch (cut from $64 in June 2026), $256 on Scale and $4,096 on Enterprise, where a 35% usage premium also applies. Published rates are up to $0.33 per GB-month of storage, up to $2.00 per GB written (copy_from_namespace operations get a 50% write discount), and $1 per petabyte scanned on queries with volume discounts of 80% above 32GB scanned and 96% above 128GB, subject to a 1.28GB minimum billable scan per query. The query rate was cut from $5/PB to $1/PB in February 2026. HIPAA BAA and SSO require Scale; BYOC, single-tenancy, private networking and CMEK are gated behind Enterprise at $4,096/month or more.

Security & Compliance

soc2
gdpr
hipaa
iso27001
sso
data residency

Connect

Sources

This page was written from 7 sources, 5 on domains other than turbopuffer.com.

  1. 1.turbopuffer.compricingvendor
  2. 2.turbopuffer.comdocsvendor
  3. 3.sacra.comturbopuffer
  4. 4.usagepricing.comturbopuffer
  5. 5.modern-datatools.comturbopuffer
  6. 6.jxnl.coturbopuffer object storage first vector database architectur
  7. 7.stainless.comturbopuffer
Newsletter

Stay Ahead of the Curve

Weekly enterprise AI insights for technology leaders. No spam, no vendor pitches—unsubscribe anytime.

Subscribe