Softwr

Databases · head to head

etcd vs Expo

etcd logo

etcd

Databases

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

From
Free
Free plan
Yes
Expo logo

Expo

Mobile Development

React Native framework and cloud platform for building and shipping apps

From
Free
Free plan
Yes

The short version

  • etcd is free; Expo starts at $19/mo.
  • Only etcd lists raft consensus; only Expo lists Expo SDK.
  • Where Expo falls short: free tier build counts and MAU support are low, pushing active projects to paid plans quickly.
  • Prices and features on this page were last checked on 20 November 2026.

How do etcd and Expo differ?

etcd and Expo differ on pricing model (Open-source against Freemium), platforms and category (Databases against Mobile Development). Only the attributes on which etcd and Expo actually diverge.

Attributes where etcd and Expo differ
AttributeetcdExpo
Pricing modelOpen-sourceFreemium
PlatformsWebWeb, iOS, Android, API
CategoryDatabasesMobile Development
Founded20132015

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

They share no listed features; 8 appear only for etcd and 7 only for Expo. 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 Expo

  • Expo SDK
  • EAS Build
  • EAS Submit
  • EAS Update
  • Expo Router
  • EAS Hosting
  • EAS Insights

What is each one used for?

etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL; Expo for building cross-platform apps with React Native without native tooling. 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 Expo
  • Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Expo
  • Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Expo
  • Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Expo

Expo

  • Building cross-platform apps with React Native without native toolingnot etcd
  • Running cloud builds and store submissions via EASnot etcd
  • Shipping over-the-air updates to bypass app store reviewnot etcd
  • Adding file-based navigation with Expo Routernot etcd
  • Hosting companion web apps and APIsnot etcd

Where do etcd and Expo fall short?

Expo's most cited limit: free tier build counts and MAU support are low, pushing active projects to paid plans quickly. 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

Expo

  • Free tier build counts and MAU support are low, pushing active projects to paid plans quickly
  • Usage-based overage charges for builds, CI/CD minutes, and MAUs can make costs less predictable
  • Concurrent build limits on lower tiers slow down teams with frequent releases
  • Some native functionality still requires ejecting to bare workflow or writing custom native modules

How much do etcd and Expo cost?

etcd is free to use; Expo has a free plan, with paid plans from $19/mo. Plan by plan below, from each vendor's own pricing page.

etcd

Free

No published plan breakdown. See the etcd review.

Expo

Free
  • FreeFree
    • 15 Android and 15 iOS builds
    • Low-priority build queue
    • 60 minutes of CI/CD workflows
  • Starter$19/mo
    • $45 build credit included
    • High-priority queue and large workers
    • 3,000 MAUs for updates
  • Production$199/mo
    • $225 build credit included
    • 2 concurrent builds
    • 50,000 MAU support
  • EnterpriseOn request
    • $1,000 build credit included
    • 5 concurrent builds
    • 1M+ MAU support

Which should you pick?

Choose etcd if

  • You need raft consensus.
  • You want to start without paying.
  • You also want linearizable reads.

Choose Expo if

  • You need expo sdk.
  • You want to start without paying.
  • You work on Web, iOS, Android, API.
  • You also want eas build.

Questions people ask

Is etcd or Expo better?
Neither clearly leads. etcd starts at Free and Expo at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, etcd or Expo?
etcd starts at Free and Expo at Free.
Does etcd or Expo run on more platforms?
etcd runs on Web. Expo runs on Web, iOS, Android, API.
Can I use etcd for free?
Both have a free tier, so you can try either at no cost before committing.
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 Expo is typically brought in for.
What can etcd do that Expo cannot?
etcd covers Raft consensus, Linearizable reads, Transactions, Leases. Expo covers Expo SDK, EAS Build, EAS Submit, EAS Update.

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.

Expo: What does Expo cost?

Expo offers a free plan, a Starter plan at $19/month with $45 build credit, a Production plan at $199/month with $225 build credit, and custom Enterprise pricing.

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.

Expo: Is there a free plan, and what are its limits?

The Free plan includes 15 Android and 15 iOS builds, low-priority build queue access, 60 minutes of CI/CD workflows, and support for 1,000 monthly active users on updates.

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.

Expo: How is usage metered on paid plans?

Beyond included build credit, Expo charges per build by platform and worker size, per CI/CD workflow minute, per million Observe events, and graduated per-MAU overage rates for updates.

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