Databases · head to head
etcd vs SST

etcd
Databases
A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
- From
- On request
- Free plan
- No
The short version
- SST is an infrastructure-as-code framework.
- SST is free; etcd prices on request.
- Only etcd lists raft consensus; only SST lists single config file.
- Where SST falls short: primarily optimized for AWS with Cloudflare support.
- Prices and features on this page were last checked on 13 November 2026.
How do etcd and SST differ?
etcd and SST differ on starting price (On request against Free), free tier (No against Yes) and platforms (Web against AWS, Web, API). Only the attributes on which etcd and SST actually diverge.
Not yet recorded: pricing model for SST.
Which features does each one have?
They share no listed features; 8 appear only for etcd and 6 only for SST. 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 SST
- Single config file
- Resource linking
- Local development
- Multi-cloud support
- Multiple deployment stages
- VPC tunneling
What is each one used for?
etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL; SST for deploying Next.js frontends with serverless backends. 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 SST
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot SST
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot SST
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot SST
SST
- Deploying Next.js frontends with serverless backendsnot etcd
- Managing databases and storage alongside application codenot etcd
- Creating staging environments for feature testingnot etcd
Where do etcd and SST fall short?
SST's most cited limit: primarily optimized for AWS with Cloudflare support. 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
SST
- Primarily optimized for AWS with Cloudflare support
- Learning curve for developers unfamiliar with infrastructure concepts
- Limited documentation for some advanced use cases
How much do etcd and SST cost?
SST is free to use. Plan by plan below, from each vendor's own pricing page.
etcd
On requestNo published plan breakdown. See the etcd review.
SST
FreeNo published plan breakdown. See the SST review.
Which should you pick?
Choose SST if
- You need single config file.
- You want to start without paying.
- You work on AWS, Web, API.
- You also want resource linking.
Questions people ask
- Is etcd or SST better?
- Neither clearly leads. etcd starts at On request and SST at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or SST?
- SST has a free tier; the other does not. Paid plans start at On request for etcd and Free for SST.
- Does etcd or SST run on more platforms?
- etcd runs on Web. SST runs on AWS, Web, API.
- Can I use SST for free?
- Yes. SST has a free tier, so you can try it without paying. etcd starts at On request.
- 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 SST is typically brought in for.
- What can etcd do that SST cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. SST covers Single config file, Resource linking, Local development, Multi-cloud support.
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.
SST: Is SST free?
Yes, SST is open source and free. You only pay for cloud resources from AWS and other providers.
Sourceetcd: 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.
SST: What cloud providers does SST support?
SST supports over 150 providers through built-in AWS and Cloudflare components, plus Pulumi and Terraform providers.
Sourceetcd: 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.
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.
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.
Related pages
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 turbopuffer
- etcd vs Apache Kafka
- etcd vs Redis
- etcd vs Postgres
- etcd vs Presto
- etcd vs Privacera
- etcd vs RavenDB
- etcd vs Readyset
- etcd vs Redpanda
- etcd vs Apache Airflow
- etcd vs Pulumi
- etcd vs Serverless Framework
- etcd vs Heroku
- etcd vs Packer
- etcd vs Encore
- etcd vs Render
- etcd vs Porter
- etcd vs Coolify
- etcd vs CapRover
- etcd vs Terragrunt
- etcd vs Zeabur
- etcd vs Railway
- etcd vs Vultr
- etcd vs Akamai
- etcd vs Alibaba Cloud
- etcd vs Azure Functions
- etcd vs Chef
- etcd vs Cilium
- SST vs DynamoDB
- SST vs Timeplus
- SST vs Firebase Realtime Database
- SST vs Knack
- SST vs Turso
- SST vs BigQuery
- SST vs TiDB
- SST vs Dgraph
- SST vs turbopuffer
- SST vs Apache Kafka
- SST vs Redis
- SST vs Postgres
- SST vs Presto
- SST vs Privacera
- SST vs RavenDB
- SST vs Readyset
- SST vs Redpanda
- SST vs Apache Airflow
- SST vs Pulumi
- SST vs Serverless Framework
- SST vs Heroku
- SST vs Packer
- SST vs Encore
- SST vs Render
- SST vs Porter
- SST vs Coolify
- SST vs CapRover
- SST vs Terragrunt
- SST vs Zeabur
- SST vs Railway
- SST vs Vultr
- SST vs Akamai
- SST vs Alibaba Cloud
- SST vs Azure Functions
- SST vs Chef
- SST vs Cilium

