Databases · head to head
etcd vs Qovery

etcd
Databases
A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
- From
- On request
- Free plan
- No

Qovery
Cloud
Deployment platform that provisions and operates Kubernetes inside your own cloud account
- From
- On request
- Free plan
- No
The short version
- Only etcd lists raft consensus; only Qovery lists bring your own cloud.
- Prices and features on this page were last checked on 13 November 2026.
How do etcd and Qovery differ?
etcd and Qovery differ on pricing model (Open-source against Quote), platforms and category (Databases against Cloud). Only the attributes on which etcd and Qovery actually diverge.
Identical on both: starting price (On request), free tier (No).
Which features does each one have?
They share no listed features; 8 appear only for etcd and 6 only for Qovery. 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 Qovery
- Bring your own cloud
- Preview environments
- Cluster lifecycle
- Terraform provider
- MCP server
- Policy as code
What is each one used for?
etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL. 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 Qovery
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Qovery
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Qovery
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Qovery
Qovery
- A regulated business that must keep application data inside its own AWS account but has nobody to build a deployment platformnot etcd
- Giving twenty engineers preview environments per pull request without writing and maintaining Terraform and Helm by handnot etcd
- Standardising deployment across AWS and GCP when acquisitions have left the organisation on two cloudsnot etcd
- Replacing a managed platform when data residency rules put every hosted option out of reachnot etcd
Where do etcd and Qovery fall 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
Qovery
- No plan publishes a price, deployment minute overage rates are not disclosed, and there is a 14 day trial rather than a free tier, so you cannot budget or compare against alternatives without going through sales
- The GPL-3.0 engine and console do not constitute a self-hostable product, because the control plane and API are closed and the self-hosted option is gated behind Enterprise, so the open licence gives you no exit if the company changes direction
- Qovery provisions managed Kubernetes into your account, which means the cloud bill sits on top of the licence and Qovery initiates control plane and ingress controller upgrades on infrastructure your team is accountable for
- The company repositioned to agentic infrastructure in June 2026 and now ships a deployment platform, a browser development portal and autonomous coding agents concurrently, so a buyer of the deployment product is not at the centre of the roadmap
- Team and Business are capped at two and three connected clusters with fixed 4 vCPU CI runners and no single sign-on on Team, which pushes teams of moderate size onto quoted Enterprise pricing earlier than the plan names imply
How much do etcd and Qovery cost?
Qovery is priced on request. Plan by plan below, from each vendor's own pricing page.
etcd
On requestNo published plan breakdown. See the etcd review.
Qovery
On request- TeamOn request
- Billed on usage with no published rate card
- 10 users, up to 100 environments, 2 connected clusters
- 5,000 deployment minutes and 7 day audit logs
- BusinessOn request
- Billed on usage with no published rate card
- 20 users, up to 250 environments, 3 connected clusters
- 10,000 deployment minutes and 30 day audit logs
- EnterpriseOn request
- Custom users, environments and clusters
- Self-hosted or air-gapped control plane
- On-premises and bring-your-own-Kubernetes
Which should you pick?
Choose Qovery if
- You need bring your own cloud.
- You work on Web, API, Self-hosted.
- You also want preview environments.
Questions people ask
- Is etcd or Qovery better?
- Neither clearly leads. etcd starts at On request and Qovery at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or Qovery?
- etcd starts at On request and Qovery at On request.
- Does etcd or Qovery run on more platforms?
- etcd runs on Web. Qovery 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 Qovery is typically brought in for.
- What can etcd do that Qovery cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Qovery covers Bring your own cloud, Preview environments, Cluster lifecycle, Terraform provider.
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.
Qovery: Does Qovery run my applications on its own servers?
No. It provisions and operates Kubernetes inside your AWS, GCP, Azure or Scaleway account, so compute and data stay with your cloud provider and that bill is entirely separate from the Qovery licence.
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.
Qovery: Can I self-host Qovery?
Only on Enterprise. The deployment engine and console are GPL-3.0, but the control plane is closed source and the self-hosted and air-gapped deployments are commercial Enterprise features.
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.
Qovery: What does it cost?
Qovery does not publish a rate card. Team and Business are billed on usage and quoted through sales, and Enterprise is fully custom. There is a 14 day trial with no card required.
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.
Qovery: What survives if I stop paying?
The Kubernetes cluster and the workloads keep running in your cloud account, but you lose the console, the deployment pipeline, preview environments and every process built on top of them.
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 Render
- etcd vs Porter
- etcd vs Northflank
- etcd vs CapRover
- etcd vs Coolify
- etcd vs Railway
- etcd vs Dokku
- etcd vs Scaleway
- etcd vs Portworx
- etcd vs Podman
- etcd vs containerd
- etcd vs Encore
- etcd vs CloudAMQP
- etcd vs Deno Deploy
- etcd vs Go
- etcd vs Hetzner Cloud
- etcd vs Infracost
- etcd vs Jaeger
- Qovery vs DynamoDB
- Qovery vs Timeplus
- Qovery vs Firebase Realtime Database
- Qovery vs Knack
- Qovery vs Turso
- Qovery vs BigQuery
- Qovery vs TiDB
- Qovery vs Dgraph
- Qovery vs turbopuffer
- Qovery vs Apache Kafka
- Qovery vs Redis
- Qovery vs Postgres
- Qovery vs Presto
- Qovery vs Privacera
- Qovery vs RavenDB
- Qovery vs Readyset
- Qovery vs Redpanda
- Qovery vs Apache Airflow
- Qovery vs Render
- Qovery vs Porter
- Qovery vs Northflank
- Qovery vs CapRover
- Qovery vs Coolify
- Qovery vs Railway
- Qovery vs Dokku
- Qovery vs Scaleway
- Qovery vs Portworx
- Qovery vs Podman
- Qovery vs containerd
- Qovery vs Encore
- Qovery vs CloudAMQP
- Qovery vs Deno Deploy
- Qovery vs Go
- Qovery vs Hetzner Cloud
- Qovery vs Infracost
- Qovery vs Jaeger
