Softwr

Databases · head to head

etcd vs Gumroad

etcd logo

etcd

Databases

A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.

From
On request
Free plan
No
Gumroad logo

Gumroad

E-Commerce

Hosted storefront for selling digital products, memberships and courses on a per sale fee

From
On request
Free plan
No

The short version

  • Only etcd lists raft consensus; only Gumroad lists digital product delivery.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which etcd and Gumroad actually diverge.

Attributes where etcd and Gumroad differ
AttributeetcdGumroad
Pricing modelOpen-sourceTransaction
CategoryDatabasesE-Commerce

Identical on both: starting price (On request), free tier (No), platforms (Web).

What each one covers

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 Gumroad

  • Digital product delivery
  • Memberships and subscriptions
  • Merchant of record
  • No monthly subscription
  • Discover marketplace
  • Hosted checkout
  • Licence keys
  • Email to customers

What people use each for

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 Gumroad
  • Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Gumroad
  • Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Gumroad
  • Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Gumroad

Gumroad

  • An individual creator selling ebooks, templates or presets without wanting to run any infrastructurenot etcd
  • A developer selling a small software product that needs licence key issuance and deliverynot etcd
  • A writer or educator running a paid membership or course for an existing audiencenot etcd
  • Anyone selling digital goods internationally who does not want to register for VAT across jurisdictionsnot etcd

Where each one falls 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

Gumroad

  • The fee is a flat percentage of every sale with no monthly plan to cap it, so a product that succeeds pays proportionally more forever, and past a certain monthly revenue a self-hosted cart plus a payment processor costs a fraction of it
  • Sales that come through the Discover marketplace carry a substantially higher cut, so marketplace-sourced revenue is materially less profitable than direct revenue and the two need tracking separately to know what the channel is really worth
  • The storefront is a Gumroad-hosted page with limited layout and branding control, so the customer experience is recognisably Gumroad's rather than yours, and there is no template language to extend it
  • Stored payment methods cannot be transferred to another platform, so migrating an active membership requires every subscriber to re-enter their card, and the churn that causes is the real exit cost rather than any contract term
  • Acting as merchant of record means Gumroad, not you, is the party in the customer's bank statement and in the tax records, which simplifies compliance but weakens the direct customer relationship and limits what you can do with the transaction data

Pricing, plan by plan

etcd

On request

No published plan breakdown. See the etcd review.

Gumroad

On request
  • Direct SalesOn request
  • Marketplace DiscoveryOn request

Which should you pick?

Choose etcd if

  • You need raft consensus.
  • You also want linearizable reads.

Choose Gumroad if

  • You need digital product delivery.
  • You also want memberships and subscriptions.

Questions people ask

Is etcd or Gumroad better?
Neither clearly leads. etcd starts at On request and Gumroad at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, etcd or Gumroad?
etcd starts at On request and Gumroad at On request.
Does etcd or Gumroad run on more platforms?
Both run on Web, so platform support will not decide this one for you.
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 Gumroad is typically brought in for.
What can etcd do that Gumroad cannot?
etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Gumroad covers Digital product delivery, Memberships and subscriptions, Merchant of record, No monthly subscription.

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.

Gumroad: How does Gumroad charge?

A flat percentage of each sale rather than a monthly subscription, with a higher rate on sales it sources through Discover. Check the current pricing page for whether payment processing is included in or added to that percentage.

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.

Gumroad: When does it stop making financial sense?

When your monthly revenue times the percentage exceeds what a hosted cart subscription plus standard processing would cost. That crossover arrives earlier than most sellers expect.

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.

Gumroad: Does it handle VAT on digital goods?

Yes. It acts as merchant of record and takes on calculating and remitting VAT and sales tax on digital sales, which is the main reason solo creators selling internationally choose it.

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.

Gumroad: Can I move my subscribers elsewhere later?

You can export customer records, but not stored payment methods. Every active subscriber has to re-enter a card on the new platform, and some will not.

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.

Gumroad: Can I sell physical products?

It is built for digital goods. Inventory, shipping and fulfilment are not what it is designed around, so a physical catalogue belongs on a store platform.

Share

Related pages

Other head to heads