Technology · head to head
etcd vs Fig
etcd
Technology
A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
- From
- On request
- Free plan
- No
Fig
Developer Tools
IDE-style autocomplete for your existing terminal
- From
- Free
- Free plan
- Yes
The short version
- Only Fig has a free tier, so it costs nothing to try first.
- Each has a real cost: 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.; Fig shut down on 1 September 2024. Amazon acquired Fig in August 2023 and folded it into Amazon Q Developer, which now carries the terminal autocomplete
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which etcd and Fig actually diverge.
Identical on both: platforms (Web), user rating (Not yet rated).
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 Fig
Nothing recorded that etcd does not also cover.
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 Fig
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Fig
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Fig
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Fig
Fig
No use cases recorded yet. See the Fig review.
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.
Fig
- Shut down on 1 September 2024. Amazon acquired Fig in August 2023 and folded it into Amazon Q Developer, which now carries the terminal autocomplete
- The standalone desktop app is no longer available or supported
- The completion specs remain open source on GitHub, but the product that consumed them is gone
Pricing, plan by plan
etcd
On requestNo published plan breakdown. See the etcd review.
Fig
FreeNo published plan breakdown. See the Fig review.
Which should you pick?
Questions people ask
- Is etcd or Fig better?
- Neither clearly leads. etcd starts at On request and Fig at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or Fig?
- Fig has a free tier; the other does not. Paid plans start at On request for etcd and Free for Fig.
- Does etcd or Fig run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Fig for free?
- Yes. Fig 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 Fig is typically brought in for.
- What can etcd do that Fig cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases.
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.
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.
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.
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 Linear
- etcd vs Asana
- etcd vs ClickUp
- etcd vs Figma
- etcd vs Istio
- etcd vs MongoDB
- etcd vs Finxact
- etcd vs Sentry
- etcd vs Trino
- etcd vs Jenkins
- etcd vs Apache Hadoop
- etcd vs Height
- etcd vs Raycast
- etcd vs Superhuman
- etcd vs Vim
- etcd vs Whimsical
- etcd vs Apache Spark
- etcd vs Visual Studio Code
- etcd vs ESLint
- etcd vs Turborepo
- etcd vs pnpm
- etcd vs Sweep
- etcd vs Cody
- etcd vs Warp
- etcd vs Keycloak
- etcd vs Rust
- etcd vs CodeSandbox
- etcd vs Vite
- etcd vs Daytona
- etcd vs Visual Studio
- etcd vs Xlinesoft
- etcd vs Ona (formerly Gitpod)
- etcd vs Sourcegraph
- Fig vs Linear
- Fig vs Asana
- Fig vs ClickUp
- Fig vs Figma
- Fig vs Istio
- Fig vs MongoDB
- Fig vs Finxact
- Fig vs Sentry
- Fig vs Trino
- Fig vs Jenkins
- Fig vs Apache Hadoop
- Fig vs Height
- Fig vs Raycast
- Fig vs Superhuman
- Fig vs Vim
- Fig vs Whimsical
- Fig vs Apache Spark
- Fig vs Visual Studio Code
- Fig vs ESLint
- Fig vs Turborepo
- Fig vs pnpm
- Fig vs Sweep
- Fig vs Cody
- Fig vs Warp
- Fig vs Keycloak
- Fig vs Rust
- Fig vs CodeSandbox
- Fig vs Vite
- Fig vs Daytona
- Fig vs Visual Studio
- Fig vs Xlinesoft
- Fig vs Ona (formerly Gitpod)
- Fig vs Sourcegraph