A serverless vector database

built from first principles on object storage: 10-100x cheaper, usage-based pricing, massive scalability

Join waitlist

         ╔════════════╗          
         ║            ║░         
      ┌──║   client   ║░         
      │  ║            ║░         
     API ╚════════════╝░         
      │   ░░░░░░░░░░░░░░         
      └─────────┐                
                │                
                ▼                
╔═turbopuffer══════════════════╗ 
║                              ║░
║  ┏━━━━━━━━━━━━━━━━━━━━━━━━┓  ║░
║  ┃        Memory/         ┃  ║░
║  ┃       SSD Cache        ┃  ║░
║  ┗━━━━━━━━━━━━━━━━━━━━━━━━┛  ║░
║               │              ║░
║               ▼              ║░
║     ┏━━━━━━━━━━━━━━━━━━━┓    ║░
║     ┃Object storage (S3)┃    ║░
║     ┗━━━━━━━━━━━━━━━━━━━┛    ║░
║                              ║░
╚══════════════════════════════╝░
 ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Cost calculator
Dimensions:
ItemsUnit costQuantityTotal
Storage
1M
$1.00
Writes
1M (~24 WPM)
$1.00
Queries
0
$0.00
Estimated subtotal

$2.00

Free credits (~1M vectors)

-$2.00

Estimated cost

FREE

per month

Latency
Query

Warm query: 1m vectors

Percentile

Latency

P50
35ms
P90
42ms
P99
58ms
MAX
81ms

Warm queries have all their data in cache.

Search for 100 random vectors from the dataset with top k = 10, when dataset is fully in cache. Warming the cache for an index takes about ~10s (for 1m vectors) after the first cold query, and typically stays in cache for a few hours.

Hear from our customers
X (formerly twitter) profile photo of Aman Sanger

Aman Sanger

@amanrsanger

After switching our vector db to @turbopuffer, we're saving an order of magnitude in costs and dealing with far less complexity!

Here's why...

(1/10)

Read full thread
Cursor iconThe AI-first Code Editor
X (formerly twitter) profile photo of Tristan Homsi

Tristan Homsi

@homsiT

Features that previously seemed prohibitively expensive are suddenly no-brainers with turbopuffer’s pricing.

Readwise logoThe best app for power-readers
Limits
MetricPrivate beta (current)Public beta (coming soon)
Max Vectors (Per Namespace)10 million100 million
Max Number of Namespaces1 billion1 billion
Max Dimensions10,75210,752
Max Inactive Time in Cache8h+TBD
Max Write Rate (Per Namespace)10,000 vectors/sec10,000 vectors/sec
Max Write Batch Rate (Per Namespace)1/sec4/sec
Max QPS (Per Namespace)100 QPS10,000 QPS
~90-95%Configurable
See full list

FAQ

© 2024 turbopuffer Inc.

All rights reserved.

Privacy policyTerms of serviceContact usSystem status
Follow us on X (twitter)