Databases · head to head
etcd vs Fly.io

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
- Fly.io starts at $29/mo; etcd prices on request.
- Only etcd lists raft consensus; only Fly.io lists global deployment.
- Where Fly.io falls short: stopped machines still bill at $0.15 per GB of root filesystem a month, so a paused service is not a free one.
- Prices and features on this page were last checked on 13 November 2026.
How do etcd and Fly.io differ?
etcd and Fly.io differ on starting price (On request against $29/month), pricing model (Open-source against Usage-based) and platforms. Only the attributes on which etcd and Fly.io 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 Fly.io. 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 Fly.io
- Global deployment
- Docker support
- Postgres databases
- Redis support
- Auto-scaling
- Health checks
- Backups
- Monitoring
What is each one used for?
etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL; Fly.io for deploying containerised applications close to users across regions. 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 Fly.io
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Fly.io
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Fly.io
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Fly.io
Fly.io
- Deploying containerised applications close to users across regionsnot etcd
- Running full stack apps and databases on managed machinesnot etcd
Where do etcd and Fly.io fall short?
Fly.io's most cited limit: stopped machines still bill at $0.15 per GB of root filesystem a month, so a paused service is not a free one. 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
Fly.io
- Egress is priced by destination region, from $0.02 per GB in North America and Europe to $0.12 per GB for Africa and India, so the same traffic costs six times more depending on where users are
- Stopped machines still bill at $0.15 per GB of root filesystem a month, so a paused service is not a free one
- Volumes are billed on provisioned capacity rather than usage, at $0.15 per GB a month
- Reservation discounts of 40% require paying a year up front, from $36 to $1,440
- Fly Kubernetes is a separate $75 a month per cluster
- Dedicated IPv4 addresses are $2 a month each
How much do etcd and Fly.io cost?
Fly.io starts at $29/mo. Plan by plan below, from each vendor's own pricing page.
etcd
On requestNo published plan breakdown. See the etcd review.
Fly.io
$29/month- Pay-as-You-GoOn request
- Micro VMs and persistent storage charged by usage
- FlyCTL CLI
- Unlimited users and organizations
- Serious Support$29/mo
- Access to dedicated engineering team
- All Pay-as-You-Go features
- Machine Reservation BlocksOn request
- 40% discount on machine usage
- Requires upfront payment for savings
- Compliance Package$99/mo
- HIPAA compliance
- BAAs
- SOC2 documentation
Which should you pick?
Choose Fly.io if
- You need global deployment.
- You work on Web, API, Self-hosted.
- You also want docker support.
Questions people ask
- Is etcd or Fly.io better?
- Neither clearly leads. etcd starts at On request and Fly.io at $29/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or Fly.io?
- etcd starts at On request and Fly.io at $29/month.
- Does etcd or Fly.io run on more platforms?
- etcd runs on Web. Fly.io runs on Web, API, Self-hosted.
- 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 Fly.io is typically brought in for.
- What can etcd do that Fly.io cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Fly.io covers Global deployment, Docker support, Postgres databases, Redis support.
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.
Fly.io: Is there a free tier for Fly.io?
Fly.io does not advertise a free tier. The base plan is pay-as-you-go with usage-based pricing for Micro VMs and persistent storage. All users get FlyCTL CLI, unlimited organizations, private networking, SSO, ACLs, and scoped tokens.
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.
Fly.io: How much does Fly.io Serious Support cost?
Serious Support costs 29 USD per month and provides access to a dedicated engineering team while maintaining all pay-as-you-go features for Micro VMs and storage.
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.
Fly.io: What does Fly.io Compliance Package include?
The Compliance Package is 99 USD per month and includes HIPAA compliance, BAAs, and SOC2 documentation for organizations requiring compliance certifications.
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.
Fly.io: Does Fly.io offer discounts for upfront commitment?
Yes, Fly.io offers Machine Reservation Blocks with 40% discount on machine usage. This requires upfront payment but applies savings on infrastructure costs.
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 Dokku
- etcd vs Porter
- etcd vs DigitalOcean
- etcd vs Koyeb
- etcd vs Zeabur
- etcd vs AWS (Amazon Web Services)
- etcd vs Coolify
- etcd vs Render
- etcd vs Railway
- etcd vs Beam Cloud
- etcd vs Northflank
- etcd vs Akamai
- etcd vs Deno Deploy
- etcd vs Go
- etcd vs Hetzner Cloud
- etcd vs Infracost
- etcd vs Jaeger
- etcd vs Lambda
- Fly.io vs DynamoDB
- Fly.io vs Timeplus
- Fly.io vs Firebase Realtime Database
- Fly.io vs Knack
- Fly.io vs Turso
- Fly.io vs BigQuery
- Fly.io vs TiDB
- Fly.io vs Dgraph
- Fly.io vs turbopuffer
- Fly.io vs Apache Kafka
- Fly.io vs Redis
- Fly.io vs Postgres
- Fly.io vs Presto
- Fly.io vs Privacera
- Fly.io vs RavenDB
- Fly.io vs Readyset
- Fly.io vs Redpanda
- Fly.io vs Apache Airflow
- Fly.io vs Dokku
- Fly.io vs Porter
- Fly.io vs DigitalOcean
- Fly.io vs Koyeb
- Fly.io vs Zeabur
- Fly.io vs AWS (Amazon Web Services)
- Fly.io vs Coolify
- Fly.io vs Render
- Fly.io vs Railway
- Fly.io vs Beam Cloud
- Fly.io vs Northflank
- Fly.io vs Akamai
- Fly.io vs Deno Deploy
- Fly.io vs Go
- Fly.io vs Hetzner Cloud
- Fly.io vs Infracost
- Fly.io vs Jaeger
- Fly.io vs Lambda

