Databases · head to head
etcd vs Letta

etcd
Databases
A distributed key-value store using Raft consensus, built for cluster coordination rather than application data.
- From
- On request
- Free plan
- No
The short version
- Letta starts at $20/mo; etcd prices on request.
- Where Letta falls short: free tier limited to 3 stateful agents.
- Prices and features on this page were last checked on 13 November 2026.
How do etcd and Letta differ?
etcd and Letta differ on starting price (On request against Free), pricing model (Open-source against Freemium) and free tier (No against Yes). Only the attributes on which etcd and Letta actually diverge.
Identical on both: platforms (Web).
Which features does each one have?
They share no listed features; 8 appear only for etcd. 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 Letta
Nothing recorded that etcd does not also cover.
What is each one used for?
etcd is most often brought in for coordinating failover in a clustered database, as Patroni does for PostgreSQL; Letta for building agents with memory for continuous learning. 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 Letta
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot Letta
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot Letta
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot Letta
Letta
- Building agents with memory for continuous learningnot etcd
- Enabling reflection during idle periods via sleep-computenot etcd
- Managing agent context and extracting learningsnot etcd
Where do etcd and Letta fall short?
Letta's most cited limit: free tier limited to 3 stateful agents. 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
Letta
- Free tier limited to 3 stateful agents
- Pro tier capped at 20 stateful agents
- API Plan usage charges apply beyond base tier
How much do etcd and Letta cost?
Letta has a free plan, with paid plans from $20/mo. Plan by plan below, from each vendor's own pricing page.
etcd
On requestNo published plan breakdown. See the etcd review.
Letta
Free- FreeFree
- Limited agents
- Limited Letta Auto usage
- Bring your own API keys
- Pro$20/mo
- Weekly and monthly Letta Auto quota
- Pay-as-you-go overage
- Up to 20 stateful agents
- API Plan$20/mo
- Unlimited agents
- $0.10/active agent/month
- $0.00015/second for tool execution
- Teams Pro$20/mo
- Per seat pricing
- Add teammates
- Letta Auto quota
Which should you pick?
Questions people ask
- Is etcd or Letta better?
- Neither clearly leads. etcd starts at On request and Letta at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, etcd or Letta?
- Letta has a free tier; the other does not. Paid plans start at On request for etcd and Free for Letta.
- Does etcd or Letta run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Letta for free?
- Yes. Letta 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 Letta is typically brought in for.
- What can etcd do that Letta 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.
Letta: How much does Letta cost?
Letta offers a free tier, then Pro plan at $20/month with up to 20 stateful agents, API Plan at $20/month base plus usage charges ($0.10/active agent/month, $0.00015/second for tool execution), and Teams Pro at $20/seat/month.
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.
Letta: How many agents can I create on the free plan?
The free tier is limited to 3 stateful agents. Pro plan allows up to 20 stateful agents, while API Plan offers unlimited agents.
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.
Letta: Does Letta charge for tool execution?
On the API Plan, Letta charges $0.00015 per second for tool execution. The Pro and Teams Pro plans include execution in their monthly fee.
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.
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.
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 Autonoly
- etcd vs Trigger.dev
- etcd vs Inngest
- etcd vs Dagster
- etcd vs Merge
- etcd vs CrewAI
- etcd vs Alloy Automation
- etcd vs Browser Use
- etcd vs Browserbase
- etcd vs Flowise
- etcd vs IBM MQ
- etcd vs Relevance AI
- etcd vs Workato
- etcd vs Automation Anywhere
- etcd vs Blue Prism
- etcd vs Mage AI
- etcd vs Meltano
- etcd vs mParticle
- Letta vs DynamoDB
- Letta vs Timeplus
- Letta vs Firebase Realtime Database
- Letta vs Knack
- Letta vs Turso
- Letta vs BigQuery
- Letta vs TiDB
- Letta vs Dgraph
- Letta vs turbopuffer
- Letta vs Apache Kafka
- Letta vs Redis
- Letta vs Postgres
- Letta vs Presto
- Letta vs Privacera
- Letta vs RavenDB
- Letta vs Readyset
- Letta vs Redpanda
- Letta vs Apache Airflow
- Letta vs Autonoly
- Letta vs Trigger.dev
- Letta vs Inngest
- Letta vs Dagster
- Letta vs Merge
- Letta vs CrewAI
- Letta vs Alloy Automation
- Letta vs Browser Use
- Letta vs Browserbase
- Letta vs Flowise
- Letta vs IBM MQ
- Letta vs Relevance AI
- Letta vs Workato
- Letta vs Automation Anywhere
- Letta vs Blue Prism
- Letta vs Mage AI
- Letta vs Meltano
- Letta vs mParticle

