Softwr

Databases · head to head

etcd vs OpenRouter

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

OpenRouter

Machine Learning

Unified API gateway routing requests across 500+ models from 80+ providers

From
Free
Free plan
Yes

The short version

  • OpenRouter is a meta-API platform.
  • OpenRouter is free; etcd prices on request.
  • Where OpenRouter falls short: no free tier; all usage incurs cost.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which etcd and OpenRouter actually diverge.

Attributes where etcd and OpenRouter differ
AttributeetcdOpenRouter
Starting priceOn requestFree
Pricing modelOpen-sourceUsage-based
Free tierNoYes
PlatformsWebAPI, Web
CategoryDatabasesMachine Learning

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 OpenRouter

Nothing recorded that etcd does not also cover.

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

OpenRouter

  • Multi-model applications optimising for cost or performancenot etcd
  • Provider-agnostic deployments avoiding vendor lock-innot etcd
  • Enterprise applications with custom data policies and provider requirementsnot etcd
  • Development workflows testing multiple models without code changesnot 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

OpenRouter

  • No free tier; all usage incurs cost
  • Pricing varies by model; specific rates not published on main site without account access
  • Adds latency through additional routing layer compared to direct provider APIs
  • Dependent on upstream provider uptime and API compatibility

Pricing, plan by plan

etcd

On request

No published plan breakdown. See the etcd review.

OpenRouter

Free
  • FreeFree
    • 50 requests per day
    • Access to 25+ free models across 4 providers
    • Community support
  • Pay-as-you-goOn request
    • 5.5% platform fee on inference costs
    • Access to 500+ models across 80+ providers
    • Email support
  • EnterpriseOn request
    • Negotiable platform fees
    • 200,000 USD of list price inference per month with no fees, then 5% fee after
    • SSO/SAML support

Which should you pick?

Choose etcd if

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

Choose OpenRouter if

  • You want to start without paying.
  • You work on API, Web.

Questions people ask

Is etcd or OpenRouter better?
Neither clearly leads. etcd starts at On request and OpenRouter at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, etcd or OpenRouter?
OpenRouter has a free tier; the other does not. Paid plans start at On request for etcd and Free for OpenRouter.
Does etcd or OpenRouter run on more platforms?
etcd runs on Web. OpenRouter runs on API, Web.
Can I use OpenRouter for free?
Yes. OpenRouter 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 OpenRouter is typically brought in for.
What can etcd do that OpenRouter cannot?
etcd covers Raft consensus, Linearizable reads, Transactions, Leases.

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.

OpenRouter: How much does OpenRouter charge?

OpenRouter charges a 5.5% platform fee on top of the actual inference costs from selected models. Customers purchase credits on a pay-as-you-go basis with no subscriptions or minimum spend requirements.

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.

OpenRouter: Is there a free tier?

Yes. OpenRouter offers a free tier with 50 requests per day and access to 25+ free models across 4 providers. The free tier provides community support only.

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.

OpenRouter: What does the Enterprise plan include?

The Enterprise plan includes 200,000 USD of list price inference per month at no cost, with a 5% platform fee applied to usage above that threshold. It also includes SSO/SAML support, contractual SLAs, and dedicated support with a shared Slack channel.

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