Databases · head to head
etcd vs Windmill

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

Windmill
Automation Integration
Open-source developer platform for building scripts, workflows, and internal apps
- From
- Free
- Free plan
- Yes
The short version
- Windmill starts at $120/mo; etcd prices on request.
- Only etcd lists raft consensus; only Windmill lists script-to-workflow engine.
- Where Windmill falls short: free self-hosted tier caps SSO users at 10 and workspaces at 3, requiring Enterprise for larger teams.
- Prices and features on this page were last checked on 17 November 2026.
How do etcd and Windmill differ?
etcd and Windmill differ on starting price (On request against Free), free tier (No against Yes) and platforms. Only the attributes on which etcd and Windmill actually diverge.
Identical on both: pricing model (Open-source).
Which features does each one have?
They share no listed features; 8 appear only for etcd and 6 only for Windmill. 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 Windmill
- Script-to-workflow engine
- Auto-generated UIs
- Self-hosted deployment
- Git sync
- SSO support
- Audit logs
What is each one used for?
etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL; Windmill for turning ad-hoc scripts into scheduled jobs and APIs. 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 Windmill
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Windmill
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Windmill
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Windmill
Windmill
- Turning ad-hoc scripts into scheduled jobs and APIsnot etcd
- Building internal tools from existing Python/TypeScript codenot etcd
- Self-hosted automation for engineering teamsnot etcd
- Orchestrating multi-language workflowsnot etcd
Where do etcd and Windmill fall short?
Windmill's most cited limit: free self-hosted tier caps SSO users at 10 and workspaces at 3, requiring Enterprise for larger teams. 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
Windmill
- Free self-hosted tier caps SSO users at 10 and workspaces at 3, requiring Enterprise for larger teams
- Compute unit and seat-based pricing (developer vs. operator seats, worker compute units) adds pricing complexity beyond a flat monthly fee
- Email triggers are capped at 100/day on the free tier, limiting event-driven use cases without upgrading
- Smaller ecosystem of pre-built integrations compared to more established automation tools like n8n
How much do etcd and Windmill cost?
Windmill has a free plan, with paid plans from $120/mo. Plan by plan below, from each vendor's own pricing page.
etcd
On requestNo published plan breakdown. See the etcd review.
Windmill
Free- Free / Open-sourceFree
- Unlimited executions
- Self-hosted deployment
- Max 10 users with SSO
- Enterprise$120/mo
- Unlimited executions and workspaces
- Uncapped SSO seats
- 24/7 priority support (3-hour response)
Which should you pick?
Choose Windmill if
- You need script-to-workflow engine.
- You want to start without paying.
- You work on Web, API, Linux, Windows, macOS.
- You also want auto-generated uis.
Questions people ask
- Is etcd or Windmill better?
- Neither clearly leads. etcd starts at On request and Windmill at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or Windmill?
- Windmill has a free tier; the other does not. Paid plans start at On request for etcd and Free for Windmill.
- Does etcd or Windmill run on more platforms?
- etcd runs on Web. Windmill runs on Web, API, Linux, Windows, macOS.
- Can I use Windmill for free?
- Yes. Windmill 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 Windmill is typically brought in for.
- What can etcd do that Windmill cannot?
- etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Windmill covers Script-to-workflow engine, Auto-generated UIs, Self-hosted deployment, Git sync.
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.
Windmill: What does Windmill cost?
Windmill's Free and Open-source edition is $0/month for self-hosted use with unlimited executions, while Enterprise starts at $120/month with unlimited workspaces and uncapped SSO seats, priced further by developer/operator seats and compute units.
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.
Windmill: Is there a free plan and what are its limits?
The free self-hosted plan supports unlimited executions but caps SSO at 10 users, workspaces at 3, groups/permissions at 4, and email triggers at 100 per day.
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.
Windmill: How is usage metered on Windmill Enterprise?
Enterprise usage is metered through seats (developer seats at $20/month, operator seats at $10/month) and compute units, e.g. $100/month for 2 standard-worker compute units.
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.
Windmill: What happens to a self-hosted Windmill deployment if the company shuts down?
The pricing page addresses this directly as an FAQ topic, noting that self-hosted applications built on the open-source edition can continue running independently of Windmill the company.
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 n8n
- etcd vs Temporal
- etcd vs Prefect
- etcd vs Pipedream
- etcd vs Trigger.dev
- etcd vs Nango
- etcd vs Airbyte
- etcd vs Meltano
- etcd vs Flowable
- etcd vs RudderStack
- etcd vs Grouparoo
- etcd vs Activiti
- etcd vs Merge
- etcd vs Parabola
- etcd vs Hevo Data
- etcd vs Paragon
- etcd vs Workato
- etcd vs Automation Anywhere
- Windmill vs DynamoDB
- Windmill vs Timeplus
- Windmill vs Firebase Realtime Database
- Windmill vs Knack
- Windmill vs Turso
- Windmill vs BigQuery
- Windmill vs TiDB
- Windmill vs Dgraph
- Windmill vs turbopuffer
- Windmill vs Apache Kafka
- Windmill vs Redis
- Windmill vs Postgres
- Windmill vs Presto
- Windmill vs Privacera
- Windmill vs RavenDB
- Windmill vs Readyset
- Windmill vs Redpanda
- Windmill vs Apache Airflow
- Windmill vs n8n
- Windmill vs Temporal
- Windmill vs Prefect
- Windmill vs Pipedream
- Windmill vs Trigger.dev
- Windmill vs Nango
- Windmill vs Airbyte
- Windmill vs Meltano
- Windmill vs Flowable
- Windmill vs RudderStack
- Windmill vs Grouparoo
- Windmill vs Activiti
- Windmill vs Merge
- Windmill vs Parabola
- Windmill vs Hevo Data
- Windmill vs Paragon
- Windmill vs Workato
- Windmill vs Automation Anywhere
