Databases · head to head
etcd vs Heroku

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
- Heroku is a cloud platform as a service.
- Heroku starts at $5/mo; etcd prices on request.
- Only etcd lists raft consensus; only Heroku lists dynos (containers).
- Where Heroku falls short: there is no free dyno tier; the cheapest Eco dyno is $5 per month.
- Prices and features on this page were last checked on 13 November 2026.
How do etcd and Heroku differ?
etcd and Heroku differ on starting price (On request against $5/month), pricing model (Open-source against Subscription) and platforms (Web against Web, API, Workers). Only the attributes on which etcd and Heroku actually diverge.
Identical on both: free tier (No).
Not yet recorded: founded for etcd.
Which features does each one have?
They share no listed features; 8 appear only for etcd and 20 only for Heroku. 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 Heroku
- Git-based deployment
- Buildpacks
- Dynos (containers)
- Add-ons marketplace
- Postgres database
- Environment variables
- Logging
- API
What is each one used for?
etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL; Heroku for application hosting. 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 Heroku
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Heroku
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Heroku
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Heroku
Heroku
- Application hostingnot etcd
- Database as a servicenot etcd
- CI/CD pipelinesnot etcd
- API deploymentnot etcd
Where do etcd and Heroku fall short?
Heroku's most cited limit: there is no free dyno tier; the cheapest Eco dyno is $5 per month. 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
Heroku
- There is no free dyno tier; the cheapest Eco dyno is $5 per month
- Eco dynos sleep after 30 minutes of inactivity, are restricted to personal accounts and allow only 2 process types
- Free SSL and 10 process types start at the Basic dyno at $7 per month
- Private and Shield dyno types require a Private Space, which is billed on top of the dynos
- Private Space dynos start at $250 per month for Private-M and $500 per month for Private-L
- Dyno prices are per dyno per month, so an app with several process types multiplies the bill
How much do etcd and Heroku cost?
Heroku starts at $5/mo. Plan by plan below, from each vendor's own pricing page.
etcd
On requestNo published plan breakdown. See the etcd review.
Heroku
$5/month- Eco Dyno$5/mo
- 0.5 GB RAM
- Git/Docker deploy
- Custom domains
- Basic Dyno$7/mo
- 0.5 GB RAM
- Always-on
- Free SSL
- Standard-1X Dyno$25/mo
- 0.5 GB RAM
- Horizontal scaling
- App metrics
- Standard-2X Dyno$50/mo
- 1 GB RAM
- Horizontal scaling
- App metrics
Which should you pick?
Choose Heroku if
- You need git-based deployment.
- You work on Web, API, Workers.
- You also want buildpacks.
Questions people ask
- Is etcd or Heroku better?
- Neither clearly leads. etcd starts at On request and Heroku at $5/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or Heroku?
- etcd starts at On request and Heroku at $5/month.
- Does etcd or Heroku run on more platforms?
- etcd runs on Web. Heroku runs on Web, API, Workers.
- 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 Heroku is typically brought in for.
- What can etcd do that Heroku cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Heroku covers Git-based deployment, Buildpacks, Dynos (containers), Add-ons marketplace.
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.
Heroku: How much does Heroku cost?
Heroku dyno pricing starts at $5 per month USD for the Eco tier (with 30-minute inactivity sleep), $7 per month for Basic (always-on), and scales up to $1,500 per month for Performance-2XL with 126 GB RAM.
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.
Heroku: What is the cheapest always-on Heroku plan?
The Basic Dyno at $7 per month USD is Heroku's cheapest always-on container option. It provides 0.5 GB RAM, free SSL, and support for 10 process types.
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.
Heroku: How is Heroku Postgres priced?
Heroku Postgres Essential tier (shared resources) starts at $5-$20 per month for 1-32 GB disk. Standard tier (dedicated) ranges $50-$12,000 per month. Premium, Private, Shield, and Advanced tiers offer higher performance at corresponding prices.
Sourceetcd: 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 Coolify
- etcd vs Neon
- etcd vs Dokku
- etcd vs DigitalOcean
- etcd vs AWS (Amazon Web Services)
- etcd vs Render
- etcd vs Porter
- etcd vs SST
- etcd vs Encore
- etcd vs Zeabur
- etcd vs Railway
- etcd vs Linode
- etcd vs Go
- etcd vs Hetzner Cloud
- etcd vs Infracost
- etcd vs Jaeger
- etcd vs Lambda
- etcd vs Longhorn
- Heroku vs DynamoDB
- Heroku vs Timeplus
- Heroku vs Firebase Realtime Database
- Heroku vs Knack
- Heroku vs Turso
- Heroku vs BigQuery
- Heroku vs TiDB
- Heroku vs Dgraph
- Heroku vs turbopuffer
- Heroku vs Apache Kafka
- Heroku vs Redis
- Heroku vs Postgres
- Heroku vs Presto
- Heroku vs Privacera
- Heroku vs RavenDB
- Heroku vs Readyset
- Heroku vs Redpanda
- Heroku vs Apache Airflow
- Heroku vs Coolify
- Heroku vs Neon
- Heroku vs Dokku
- Heroku vs DigitalOcean
- Heroku vs AWS (Amazon Web Services)
- Heroku vs Render
- Heroku vs Porter
- Heroku vs SST
- Heroku vs Encore
- Heroku vs Zeabur
- Heroku vs Railway
- Heroku vs Linode
- Heroku vs Go
- Heroku vs Hetzner Cloud
- Heroku vs Infracost
- Heroku vs Jaeger
- Heroku vs Lambda
- Heroku vs Longhorn

