Softwr

Databases · head to head

etcd vs Shopkeep

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
Shopkeep logo

Shopkeep

E-Commerce

Cloud-based POS for small businesses

From
$89/month
Free plan
No

The short version

  • Shopkeep is a cloud-based point of sale system.
  • Shopkeep starts at $89/mo; etcd prices on request.
  • Only etcd lists raft consensus; only Shopkeep lists point of sale.
  • Where Shopkeep falls short: all plans require 24/7 phone and chat support; no tiered support options.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which etcd and Shopkeep actually diverge.

Attributes where etcd and Shopkeep differ
AttributeetcdShopkeep
Starting priceOn request$89/month
Pricing modelOpen-sourceSubscription
PlatformsWebiOS, Web
CategoryDatabasesE-Commerce

Identical on both: free tier (No).

Not yet recorded: founded for etcd.

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 Shopkeep

  • Point of sale
  • Payment processing
  • Inventory management
  • Customer profiles
  • Sales analytics
  • Employee management
  • Mobile POS
  • Reporting

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

Shopkeep

No use cases recorded yet. See the Shopkeep review.

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

Shopkeep

  • All plans require 24/7 phone and chat support; no tiered support options
  • Prices vary by business type and industry with additional service fees possible
  • Extra locations and registers incur additional charges beyond base plan cost

Pricing, plan by plan

etcd

On request

No published plan breakdown. See the etcd review.

Shopkeep

$89/month
  • Basic$89/mo
    • Retail POS platform
    • 1 register included
    • Integrated Payments 1.5%
  • Core$149/mo
    • All Basic features
    • Advanced management tools
    • Business growth support
  • Plus$289/mo
    • All Core features
    • Advanced customization
    • Established retail operations support

Which should you pick?

Choose etcd if

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

Choose Shopkeep if

  • You need point of sale.
  • You work on iOS, Web.
  • You also want payment processing.

Questions people ask

Is etcd or Shopkeep better?
Neither clearly leads. etcd starts at On request and Shopkeep at $89/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, etcd or Shopkeep?
etcd starts at On request and Shopkeep at $89/month.
Does etcd or Shopkeep run on more platforms?
etcd runs on Web. Shopkeep runs on iOS, Web.
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 Shopkeep is typically brought in for.
What can etcd do that Shopkeep cannot?
etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Shopkeep covers Point of sale, Payment processing, Inventory management, Customer profiles.

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.

Shopkeep: What is included in the Lightspeed Retail Basic plan at $89 per month?

The Basic plan includes 1 register, retail POS platform, integrated payments at 1.5% card-present rate, inventory management, Lightspeed Wholesale access, NuORDER Catalog with 5 million+ products, built-in eCommerce, loyalty programs, and 24/7 support.

Source
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.

Shopkeep: How much can I save by paying annually instead of monthly?

Shopkeep (Lightspeed Retail) offers up to 18% discount when paying annually instead of month-to-month. All three plans (Basic, Core, Plus) qualify for this annual discount.

Source
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.

Shopkeep: What additional costs should I budget beyond the monthly subscription?

Beyond the monthly plan cost, extra locations require additional charges, extra registers incur per-register fees, and hardware (terminals, scanners, iPad devices) have separate costs. Integrated payment processing charges 1.5% per transaction.

Source
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.

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.

Share

Related pages

Other head to heads