Databases · head to head
etcd vs GitHub

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
- GitHub is a development platform inspired.
- GitHub starts at $4/mo; etcd prices on request.
- Only etcd lists raft consensus; only GitHub lists git repositories.
- Where GitHub falls short: acquired by Microsoft in 2018, reducing pure independence despite operational autonomy.
- Prices and features on this page were last checked on 17 November 2026.
How do etcd and GitHub differ?
etcd and GitHub differ on starting price (On request against Free), pricing model (Open-source against Subscription) and free tier (No against Yes). Only the attributes on which etcd and GitHub actually diverge.
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 GitHub. 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 GitHub
- Git repositories
- Pull requests
- Code review
- Issues & projects
- GitHub Actions CI/CD
- GitHub Pages
- Security scanning
- Dependency management
What is each one used for?
etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL; GitHub for version control. 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 GitHub
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot GitHub
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot GitHub
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot GitHub
GitHub
- Version controlnot etcd
- Code collaborationnot etcd
- CI/CD pipelinesnot etcd
- Project managementnot etcd
- Documentation hostingnot etcd
Where do etcd and GitHub fall short?
GitHub's most cited limit: acquired by Microsoft in 2018, reducing pure independence despite operational autonomy. 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
GitHub
- Acquired by Microsoft in 2018, reducing pure independence despite operational autonomy
- Primary focus on source control differs from purpose-built project management tools like Jira
- Pricing for enterprise features and private repositories adds up compared to some self-hosted alternatives
How much do etcd and GitHub cost?
GitHub has a free plan, with paid plans from $4/mo. Plan by plan below, from each vendor's own pricing page.
etcd
On requestNo published plan breakdown. See the etcd review.
GitHub
Free- FreeFree
- Unlimited public/private repos
- 2,000 CI/CD minutes/month
- 500MB package storage
- Team$4/mo
- Everything in Free
- 3,000 CI/CD minutes/month
- 2GB package storage
- Enterprise$21/mo
- Everything in Team
- 50,000 CI/CD minutes/month
- 50GB package storage
Which should you pick?
Choose GitHub if
- You need git repositories.
- You want to start without paying.
- You work on Web, Windows, macOS, iOS, Android.
- You also want pull requests.
Questions people ask
- Is etcd or GitHub better?
- Neither clearly leads. etcd starts at On request and GitHub at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or GitHub?
- GitHub has a free tier; the other does not. Paid plans start at On request for etcd and Free for GitHub.
- Does etcd or GitHub run on more platforms?
- etcd runs on Web. GitHub runs on Web, Windows, macOS, iOS, Android.
- Can I use GitHub for free?
- Yes. GitHub 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 GitHub is typically brought in for.
- What can etcd do that GitHub cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. GitHub covers Git repositories, Pull requests, Code review, Issues & projects.
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.
GitHub: What is a Git repository and how does GitHub use it?
A repository is the centralized database that stores the complete collection of files and folders for a codebase, along with the revision history. GitHub uses Git to provide distributed version control access to repositories with version tracking, branching, and collaboration features.
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.
GitHub: How does GitHub authentication work?
When you connect to a GitHub repository from Git, you need to authenticate with GitHub using either HTTPS or SSH. GitHub supports multiple authentication methods including passwords, personal access tokens, SSH keys, and GitHub Apps.
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.
GitHub: How long has GitHub been operating?
GitHub was founded in 2008 and launched publicly on April 10, 2008, making it the dominant git hosting platform for nearly two decades.
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.
GitHub: Who owns GitHub and when did the acquisition occur?
Microsoft acquired GitHub for $7.5 billion USD, with the deal announced June 4, 2018 and completed October 26, 2018. GitHub operates as an independent subsidiary within Microsoft.
Sourceetcd: 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 GitLab
- etcd vs Eclipse
- etcd vs Docker
- etcd vs Cortex
- etcd vs Jenkins
- etcd vs Kubernetes
- etcd vs Postman
- etcd vs Bazel
- etcd vs Depot
- etcd vs Nx Cloud
- etcd vs Atlantis
- etcd vs WarpBuild
- etcd vs OpsLevel
- etcd vs PartyKit
- etcd vs PhpStorm
- etcd vs Pieces for Developers
- etcd vs RAD Studio
- etcd vs Refact
- GitHub vs DynamoDB
- GitHub vs Timeplus
- GitHub vs Firebase Realtime Database
- GitHub vs Knack
- GitHub vs Turso
- GitHub vs BigQuery
- GitHub vs TiDB
- GitHub vs Dgraph
- GitHub vs turbopuffer
- GitHub vs Apache Kafka
- GitHub vs Redis
- GitHub vs Postgres
- GitHub vs Presto
- GitHub vs Privacera
- GitHub vs RavenDB
- GitHub vs Readyset
- GitHub vs Redpanda
- GitHub vs Apache Airflow
- GitHub vs GitLab
- GitHub vs Eclipse
- GitHub vs Docker
- GitHub vs Cortex
- GitHub vs Jenkins
- GitHub vs Kubernetes
- GitHub vs Postman
- GitHub vs Bazel
- GitHub vs Depot
- GitHub vs Nx Cloud
- GitHub vs Atlantis
- GitHub vs WarpBuild
- GitHub vs OpsLevel
- GitHub vs PartyKit
- GitHub vs PhpStorm
- GitHub vs Pieces for Developers
- GitHub vs RAD Studio
- GitHub vs Refact

