etcdvs
Asana


Asana: Manage your team's work, projects, & tasks online

A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
As of 30 August 2026, etcd is free to use. etcd gives you strongly consistent, linearizable reads and writes across a small cluster, and is the store behind every Kubernetes cluster. Softwr lists it under Technology.
Overview
etcd is a distributed key-value store written in Go, created at CoreOS, licensed under Apache 2.0 and now a graduated project of the Cloud Native Computing Foundation. It uses the Raft consensus algorithm to replicate a consistent log across an odd-numbered cluster, normally three or five members, and serves a gRPC API with linearizable reads by default. Its primitives are the ones coordination needs: atomic compare-and-swap transactions, leases with time-to-live, and watches that stream key changes to clients from a given revision. It is the datastore behind Kubernetes, and also underpins products such as CoreDNS setups, Patroni-managed Postgres and various schedulers. The distinguishing property is that it prioritises correctness over throughput and is honest about it. Every write is committed to a quorum and fsynced to disk before it is acknowledged, so a client that receives a success knows the write survives the loss of a minority of nodes, and a linearizable read never returns stale data. That guarantee is what makes it safe to build leader election, distributed locks and cluster membership on top of, which is the entire reason it exists; systems that need those primitives cannot use an eventually consistent store without inventing their own consensus. It is chosen by platform teams building schedulers, control planes and clustered systems, and inherited by everyone running Kubernetes whether they chose it or not. The trade-offs are the direct price of the guarantee. Performance is bounded by the slowest disk in the cluster because of the fsync on every write; adding members increases availability but decreases write throughput; and the store is sized for coordination data, with a default backend quota of 2 GB and 8 GB the recommended maximum, beyond which the cluster enters a read-only alarm state that a human must clear.
The honest half
Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about etcd.
Cross-shopped
Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.


Asana: Manage your team's work, projects, & tasks online


ClickUp: One app to replace them all


Linear: The issue tracking tool you'll enjoy using


Figma: The collaborative interface design tool
Capabilities
Raft consensus
Replicates a consistent log across members with automatic leader election, tolerating loss of a minority of nodes
Linearizable reads
Reads go through the leader by default and never return stale data, with a serialisable option when speed matters more
Transactions
Compare-and-swap style if/then/else transactions over multiple keys, which is what makes distributed locking safe
Leases
Keys with a time-to-live that a client must renew, so a crashed client's registration or lock expires automatically
Watches
Streams key changes to clients from a given revision, so a watcher that reconnects does not miss events
MVCC revision history
Keeps historical revisions so clients can read a consistent past snapshot, subject to the compaction policy
Role-based access control
Users, roles and key-range permissions, with mutual TLS for both client and peer connections
Snapshot backup and restore
A point-in-time snapshot command and a documented restore path, which is the recovery mechanism after quorum loss
Answered, with sources
Each answer names the page it came from, so you can check it rather than take our word for it.
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.
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.
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.
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.
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.
Keep looking
A Kubernetes service mesh that adds mutual TLS, traffic control and telemetry between services without changing application code.
Cloud native core banking, sold as Finxact from Fiserv since the 2022 acquisition
Application monitoring platform built by developers for developers
A distributed SQL engine that queries data where it already lives, across object storage, warehouses and operational databases.
A self-hosted automation server that can build almost anything, through a plugin ecosystem that is also its main liability.
The original open source framework for distributed storage and batch processing on commodity servers, now largely a legacy platform.
A project management tool from a small independent vendor that uses AI agents to handle routine ticket maintenance.
Highly configurable text editor built to enable efficient text editing
A distributed engine for batch, SQL, streaming and machine learning workloads over data that does not fit on one machine.
The original open source framework for distributed storage and batch processing on commodity servers, now largely a legacy platform.
Softwr does not host reviews and shows no star rating for etcd, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.
What people switch to, and what they give up
Every tier, and where the cost actually lands
Put it head to head with anything we hold
Its rating, and an embed for your own site
Secure access for everyone
The digital analytics platform to understand your users
Apple's WebKit browser, available only on Apple operating systems and updated only with them.
free