Databases · head to head
etcd vs turbopuffer

etcd
Databases
A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
- From
- On request
- Free plan
- No

turbopuffer
Databases
Closed-source vector and full-text search service built directly on object storage, with cold queries measured in seconds rather than milliseconds.
- From
- $16/month
- Free plan
- No
The short version
- turbopuffer starts at $16/mo; etcd prices on request.
- Only etcd lists raft consensus; only turbopuffer lists object storage architecture.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which etcd and turbopuffer actually diverge.
| Attribute | etcd | turbopuffer |
|---|---|---|
| Starting price | On request | $16/month |
| Pricing model | Open-source | Subscription |
Identical on both: free tier (No), platforms (Web), category (Databases).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in etcd
- Raft consensus
- Linearizable reads
- Transactions
- Leases
- Watches
- MVCC revision history
- Role-based access control
- Snapshot backup and restore
Only in turbopuffer
- Object storage architecture
- Namespaces
- Vector search
- Full-text search
- Attribute filtering
- Documented limits
- Configurable consistency
- Durable writes
What people use each for
The jobs each tool is most often brought in to do.
etcd
- Storing Kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doingnot turbopuffer
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot turbopuffer
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot turbopuffer
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot turbopuffer
turbopuffer
- A product with one search index per customer and thousands of customers, most of whose data is idle on any given daynot etcd
- Very large corpora where holding every vector in memory is the dominant cost and occasional cold-query latency is acceptablenot etcd
- Hybrid retrieval combining BM25 and vector search where running and synchronising two separate systems is the problem being solvednot etcd
- Retrieval for agent and assistant products where indexes are created and destroyed frequently and per-index overhead must be near zeronot etcd
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
etcd
- It is sized for coordination data, not application data: the default backend quota is 2 GB and 8 GB is the documented recommended maximum, and exceeding it puts the cluster into a NOSPACE alarm where it accepts no writes until an operator compacts, defragments and clears the alarm by hand
- Every write is replicated and fsynced before acknowledgement, so cluster performance is bounded by the slowest disk in it; a member on network-attached storage with high fsync latency causes leader elections and cluster-wide latency spikes that look like network problems and are not
- Adding members increases availability but reduces write throughput, because each write must reach a larger quorum; you run three or five members for fault tolerance, and increasing capacity means faster hardware rather than more nodes
- There is no sharding and no multi-tenancy, so isolating workloads means running separate clusters, each with its own quorum, certificates, backup schedule and upgrade path, and that operational multiplication is often unexpected
- Running it yourself is a real job: periodic compaction and defragmentation, snapshot backups you have actually rehearsed restoring, and rotation of both peer and client TLS certificates, none of which happens automatically outside a managed Kubernetes service
- Losing quorum is not self-healing; recovering a cluster that has lost a majority means restoring from a snapshot and accepting that everything written since that snapshot is gone, which makes backup frequency a data-loss budget decision rather than a routine setting
turbopuffer
- A cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second
- Queries are eventually consistent by default, and after roughly 128 MiB of outstanding writes new data is invisible until indexed, which the vendor puts at tens of seconds for small namespaces and tens of minutes for large ones, so a bulk re-index is not immediately queryable
- It is closed source with no community edition, so single-tenant or bring-your-own-cloud deployment is a commercial negotiation rather than a deployment choice, and there is no path to running it yourself if the relationship ends
- Per-namespace ceilings, roughly 10,000 writes per second, 32 MB/s and 500 million documents per shard, mean a single enormous index has to be sharded across namespaces by your application rather than by the service
- It is a search engine, not a database: there are no joins, no cross-document transactions and no SQL, so it sits beside a primary datastore and keeping the two in step is work that belongs to you
Pricing, plan by plan
etcd
On requestNo published plan breakdown. See the etcd review.
turbopuffer
$16/month- Launch$16/mo
- All database features
- Multi-tenancy deployment
- SOC2 & GDPR-ready DPA
- Scale$256/mo
- Everything in Launch
- HIPAA-ready BAA
- Single Sign-On (SSO)
- Enterprise$4,096/mo
- Everything in Scale
- Single-tenancy & BYOC deployment options
- Private networking
Which should you pick?
Choose turbopuffer if
- You need object storage architecture.
- You also want namespaces.
Questions people ask
- Is etcd or turbopuffer better?
- Neither clearly leads. etcd starts at On request and turbopuffer at $16/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or turbopuffer?
- etcd starts at On request and turbopuffer at $16/month.
- Does etcd or turbopuffer run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- What is etcd best used for?
- etcd is most often used for storing kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doing, leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactions, service discovery and dynamic configuration where readers need to be notified of changes rather than poll for them, coordinating failover in a clustered database, as patroni does for postgresql. Of those, storing kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doing and leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactions are not what turbopuffer is typically brought in for.
- What can etcd do that turbopuffer cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.
Answered from the vendors’ own pages
etcd: Can I use etcd as an application database?
No. It is designed for metadata and coordination, with a recommended maximum store size of around 8 GB, no sharding and a write path deliberately optimised for durability rather than throughput. Application data belongs in a database built for it.
turbopuffer: Can I self-host turbopuffer?
There is no open source or community edition. Single-tenant and bring-your-own-cloud deployments exist as commercial arrangements, but there is no way to run it independently of the vendor.
etcd: How many members should a cluster have?
Three for most cases, five where you need to survive two simultaneous failures. Always an odd number, because an even-sized cluster gains no additional fault tolerance while making quorum harder to reach.
turbopuffer: How fast is it really?
Warm queries perform comparably to in-memory search engines. Cold queries, where data is not cached, have a documented p90 around 1,214 ms on a million documents. Write p90 is around 248 ms for a 512 KB upsert because writes go straight to object storage.
etcd: What happens when the store fills up?
The cluster raises a NOSPACE alarm and stops accepting writes, becoming effectively read-only. Recovery requires compacting old revisions, defragmenting each member and then explicitly disarming the alarm, all done by an operator.
turbopuffer: Is it consistent?
Eventually consistent by default, with the vendor reporting that over 99.8% of queries return consistent data. Strong consistency can be requested per query at a latency cost. Large write bursts have a longer visibility delay while indexing catches up.
etcd: Why is my etcd cluster slow or unstable?
Almost always disk latency. Because every write is fsynced before acknowledgement, slow or shared storage causes heartbeat timeouts, leader elections and cascading latency. Local SSDs with low fsync latency are effectively a requirement.
turbopuffer: What is it best at?
Large numbers of namespaces where most are idle. The architecture makes cold data cheap to keep, which is exactly the shape of a multi-tenant product with a long tail of inactive customers.
etcd: How does it compare with Consul or ZooKeeper?
All three provide consensus-backed coordination. etcd has the simplest data model and the Kubernetes ecosystem behind it; Consul bundles service discovery, health checking and a service mesh; ZooKeeper is older, JVM-based and still common under Kafka and Hadoop-era systems.
turbopuffer: What are the hard limits?
Up to 128 billion documents and 256 TB per namespace, 500 million documents per shard, 64 MiB per document, 10,752 dense vector dimensions, roughly 10,000 writes per second per namespace and a maximum result set of 10,000.
Related pages
More on turbopuffer
Other head to heads
- etcd vs DynamoDB
- etcd vs Timeplus
- etcd vs Firebase Realtime Database
- etcd vs Knack
- etcd vs Turso
- etcd vs BigQuery
- etcd vs TiDB
- etcd vs Dgraph
- etcd vs Apache Kafka
- etcd vs Redis
- etcd vs Fivetran HVR
- etcd vs Grist
- etcd vs IBM Db2
- etcd vs Instaclustr
- etcd vs LanceDB
- etcd vs Marqo
- etcd vs Apache Airflow
- etcd vs Chroma
- etcd vs Dremio
- etcd vs DuckDB
- etcd vs Trino
- etcd vs Typesense
- etcd vs Dragonfly
- etcd vs Readyset
- etcd vs TIBCO Enterprise Message Service
- etcd vs Vespa
- etcd vs Xata
- etcd vs EMQX
- etcd vs FaunaDB
- etcd vs Memcached
- etcd vs MotherDuck
- etcd vs Firestore
- turbopuffer vs DynamoDB
- turbopuffer vs Timeplus
- turbopuffer vs Firebase Realtime Database
- turbopuffer vs Knack
- turbopuffer vs Turso
- turbopuffer vs BigQuery
- turbopuffer vs TiDB
- turbopuffer vs Dgraph
- turbopuffer vs Apache Kafka
- turbopuffer vs Redis
- turbopuffer vs Fivetran HVR
- turbopuffer vs Grist
- turbopuffer vs IBM Db2
- turbopuffer vs Instaclustr
- turbopuffer vs LanceDB
- turbopuffer vs Marqo
- turbopuffer vs Apache Airflow
- turbopuffer vs Chroma
- turbopuffer vs Dremio
- turbopuffer vs DuckDB
- turbopuffer vs Trino
- turbopuffer vs Typesense
- turbopuffer vs Dragonfly
- turbopuffer vs Readyset
- turbopuffer vs TIBCO Enterprise Message Service
- turbopuffer vs Vespa
- turbopuffer vs Xata
- turbopuffer vs EMQX
- turbopuffer vs FaunaDB
- turbopuffer vs Memcached
- turbopuffer vs MotherDuck
- turbopuffer vs Firestore
