etcd

etcd is a self-hosted, strongly consistent key-value store for distributed systems and machine clusters. It suits infrastructure teams, Kubernetes operators, and developers who need coordinated state under their own operational control. The zero-license-cost model is compelling, but running it reliably requires platform expertise and intentional security setup.

Overview

etcd distributes data with the Raft protocol, combining a shared key-value store with consensus and failure handling. It can conduct leader elections during network partitions and tolerate machine failures, including loss of the current leader. That makes it a serious coordination datastore rather than a lightweight embedded cache.

The software is Apache 2.0 licensed and self-hosted. You are responsible for deployment, upgrades, capacity, and protection of the service. The project generally maintains only its two latest minor versions; its 2025 release announcement identified those as v3.5 and v3.6 at that time, so version planning matters for teams that need a supported release.

Key features

Values are arranged in a hierarchical directory structure, and clients can watch keys or directories for changes. Watchers let services react to configuration and coordination updates without repeatedly polling. Optional time-to-live settings allow keys to expire when temporary state should not remain indefinitely.

Clients can read and write values with ordinary HTTP tools such as curl, while gRPC and HTTP/JSON are supported protocols. The project reports benchmarks of thousands of writes per second per instance. That indicates the workload it targets, not a guaranteed result for every hardware, network, or cluster design.

Kubernetes uses etcd as its primary datastore, and the integrations listing includes CoreDNS plus client libraries for several languages. Those third-party tools and libraries are not tested or maintained by the etcd team, so their ongoing fit and upkeep remain your responsibility.

TLS and client-certificate authentication are available for both client-to-server and peer communication, but these protections are disabled by default. An installation that leaves them off is not making use of etcd's available transport and identity controls.

Pricing

Open-source etcd — free (Apache 2.0 licensed, self-hosted software). There is no paid tier or trial period. This is the right economic choice for teams able to supply their own infrastructure and operations; it does not remove the cost of machines, storage, monitoring, maintenance, or security work. There are no hosted seats or service quotas in this plan, because the deployment is yours to size and run.

Platforms

etcd supports API, Linux, macOS, self-hosted deployments, and Windows. The current platform table rates Linux on AMD64 and ARM64 as tier 1. Darwin and Windows on AMD64 or ARM64 are tier 3, while unlisted platforms are unsupported. Pre-built binaries, source builds, and container images are provided. Operating-system package-manager installs may be outdated and are not officially supported, so they are a weaker choice when version currency matters.

Who it's for

Choose etcd when a platform or infrastructure team needs strongly consistent shared state, clustering, key watches, TTL-based cleanup, and tolerance for leader or machine failure. Kubernetes operators are a particularly natural audience because Kubernetes depends on etcd as its primary datastore. It is less suitable for teams seeking a managed service or unwilling to operate consensus software, secure communications, and version upgrades themselves.

Pros and cons

Pros

• Strong consistency with Raft: leader elections and failure tolerance support coordination across machines.
• Useful change handling: hierarchical keys, directory and key watches, and TTL expiry cover common configuration and ephemeral-state patterns.
• Broad access options: HTTP tools, gRPC, and HTTP/JSON make integration possible from standard tooling and client libraries.
• Free, permissively licensed deployment: Apache 2.0 and self-hosting avoid license fees and vendor hosting dependence.

Cons

• Operational ownership is mandatory: reliability, upgrades, capacity, and backups are not supplied as a managed service.
• Security needs deliberate configuration: TLS and client certificates are not enabled by default.
• Platform tiers are uneven: Linux AMD64 and ARM64 are tier 1, while Darwin and Windows are tier 3 and unlisted platforms are unsupported.
• Integration responsibility remains with you: listed third-party tools and libraries are not tested or maintained by the etcd team.

Alternatives

Amazon DynamoDB is the better fit when you want a cloud service with a free tier, free trial, and broad web and mobile platform coverage instead of self-hosting. Riak KV suits teams wanting an open-source key-value system with masterless built-in replication and HTTP or Protocol Buffers access.

RocksDB is a free open-source C++ library rather than a distributed datastore service. Redis Insight is a free cross-platform option when you specifically want its desktop and web interface. Aerospike Database offers a freemium model with a Community Edition capped at 8 nodes, 2.5 TB, and 2 namespaces.

Google Cloud Bigtable is a paid cloud alternative with a free trial. SuperMassive is another free, BSD-3-Clause open-source choice with no commercial plans listed. TiKV is a free open-source alternative for teams evaluating another distributed key-value project.

For more options, browse Key-Value Databases.

Verdict

etcd is a strong recommendation for Kubernetes operators and infrastructure teams that need consensus-backed, watchable state and can run a self-hosted cluster. Its main reason to choose is dependable distributed coordination without license fees; its main reason to look elsewhere is the operational and security responsibility that a managed alternative would take away.