Technology · head to head
etcd vs Height
etcd
Technology
A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
- From
- On request
- Rated
- -
Height
Technology
A project management tool from a small independent vendor that uses AI agents to handle routine ticket maintenance.
- From
- Free
- Rated
- -
The short version
- Only Height 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.; Height it is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.
- They diverge on capability: etcd covers Raft consensus, Height covers Autonomous triage.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which etcd and Height actually diverge.
Identical on both: platforms (Web), user rating (Not yet rated), category (Technology).
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 Height
- Autonomous triage
- Duplicate detection
- Attribute maintenance
- Per-task chat
- Multiple views
- Developer integrations
- Custom fields and filters
- Public API
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 Height
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Height
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Height
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Height
Height
- A product or engineering team with no dedicated project manager, where backlog upkeep currently falls on whoever has timenot etcd
- Teams leaving Jira because its configuration and administration cost more attention than the tracking is worthnot etcd
- A support or intake queue where incoming requests need categorising and deduplicating before anyone can plan themnot etcd
- Startups that want tasks, chat and progress tracking in one tool rather than stitching a tracker to a chat appnot 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.
Height
- It is one product from one small venture-funded company with no second line of business underwriting it, so adopting it as your system of record is a bet on that company's funding, and the tool holds work history you would have to reconstruct elsewhere if the bet fails.
- The 2024 relaunch as Height 2.0 reoriented the product around AI agents and changed workflows customers had already built on, which is the clearest available evidence of how much the product may be re-shaped again under you.
- The ecosystem is small next to Jira, Linear and Asana: fewer third-party integrations, no consultancy market, and far less written material to search when something behaves unexpectedly, so support questions go to the vendor and wait.
- The automation only pays off if tasks contain enough substance for a model to work with; on a team whose tickets are two-word titles, the agents have nothing to triage or deduplicate and the product reduces to an ordinary tracker at a premium.
- Task content is processed by hosted large language models, so a security review becomes a question about subprocessors and data handling, and there is no self-hosted or on-premises deployment to fall back on if the answer is unacceptable.
- There is no widely used two-way synchronisation with Jira, so an organisation where one team adopts Height and the rest stay on Jira ends up with two systems of record and manual reconciliation between them.
Pricing, plan by plan
etcd
On requestNo published plan breakdown. See the etcd review.
Height
FreeNo published plan breakdown. See the Height review.
Which should you pick?
Choose Height if
- You need autonomous triage.
- You want to start without paying.
- You also want duplicate detection.
Questions people ask
- Is etcd or Height better?
- Neither clearly leads. etcd starts at On request and Height at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or Height?
- Height has a free tier; the other does not. Paid plans start at On request for etcd and Free for Height.
- Does etcd or Height run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Height for free?
- Yes. Height 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 Height is typically brought in for.
- What can etcd do that Height cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Height covers Autonomous triage, Duplicate detection, Attribute maintenance, Per-task chat.
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.
Height: How is this different from Jira automation?
Jira automation is rule-based: you define a trigger and an action. Height's agents read the content of tasks and act on judgement, such as recognising that two tickets describe the same bug, which no rule can express.
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.
Height: Can we self-host it?
No. It is software as a service only, with no on-premises or private-cloud deployment. If your requirements rule out a hosted tracker, this is not a candidate.
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.
Height: What happens to our data if the company fails?
You would need an export and a migration to another tool. This is the standard risk with a single-product startup, and it is worth confirming the export path covers task history, comments and custom fields before committing to it.
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.
Height: Does it work for non-engineering teams?
Yes, the views and custom fields are generic enough for marketing, operations or support queues. Its integrations, though, are aimed at software teams, so a non-engineering team gets less of the surrounding value.
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.
Height: Do the AI features need our tickets to be well written?
In practice, yes. Triage, deduplication and attribute maintenance work from what is written in the task, so the return is much higher on a team that already writes descriptive tickets than on one that does not.
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 Raycast
- etcd vs Superhuman
- etcd vs Vim
- etcd vs Whimsical
- etcd vs Apache Spark
- etcd vs Monday.com
- etcd vs Shortcut
- etcd vs Coda
- etcd vs Intercom
- etcd vs Attio
- etcd vs Kubernetes
- etcd vs Notion
- etcd vs Site24x7
- etcd vs StatusCake
- etcd vs Storybook
- etcd vs WebStorm
- etcd vs Zabbix Cloud
- Height vs Linear
- Height vs Asana
- Height vs ClickUp
- Height vs Figma
- Height vs Istio
- Height vs MongoDB
- Height vs Finxact
- Height vs Sentry
- Height vs Trino
- Height vs Jenkins
- Height vs Apache Hadoop
- Height vs Raycast
- Height vs Superhuman
- Height vs Vim
- Height vs Whimsical
- Height vs Apache Spark
- Height vs Monday.com
- Height vs Shortcut
- Height vs Coda
- Height vs Intercom
- Height vs Attio
- Height vs Kubernetes
- Height vs Notion
- Height vs Site24x7
- Height vs StatusCake
- Height vs Storybook
- Height vs WebStorm
- Height vs Zabbix Cloud