E-Commerce · head to head
BackToMe vs etcd

BackToMe
E-Commerce
Right-of-withdrawal handling for European e-commerce
- From
- €25/month
- Free plan
- No

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
- BackToMe starts at €25/mo; etcd prices on request.
- Only BackToMe lists floating withdrawal button; only etcd lists raft consensus.
- Where BackToMe falls short: the scope is European consumer law. A merchant selling outside the EU has no use for it.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which BackToMe and etcd actually diverge.
Identical on both: 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 BackToMe
- Floating withdrawal button
- Automatic acknowledgement
- Sealed archiving
- Withdrawal dashboard
- One-click proof export
- Multi-store from one account
Only in etcd
- Raft consensus
- Linearizable reads
- Transactions
- Leases
- Watches
- MVCC revision history
- Role-based access control
- Snapshot backup and restore
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot etcd
- Producing dated proof of a cancellation in a customer disputenot etcd
- Handling withdrawal requests across several EU languagesnot etcd
- Running one withdrawal process across multiple storefrontsnot etcd
- Passing a consumer-protection audit with exportable recordsnot etcd
etcd
- Storing Kubernetes cluster state, which is what the overwhelming majority of etcd deployments are doingnot BackToMe
- Leader election and distributed locking in a home-grown scheduler or control plane, using leases and transactionsnot BackToMe
- Service discovery and dynamic configuration where readers need to be notified of changes rather than poll for themnot BackToMe
- Coordinating failover in a clustered database, as Patroni does for PostgreSQLnot BackToMe
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
BackToMe
- The scope is European consumer law. A merchant selling outside the EU has no use for it
- The site and dashboard are French. The customer-facing button covers 24 EU languages, but the merchant side is not multilingual
- One price, one feature set. There is no tier for a shop that wants only the archive or only the button
- It runs as an injected script on the storefront, so a shop with a strict content security policy has an extra step before the button will render
- A young French vendor with no independent review coverage, so there is nothing outside the vendor's own material to corroborate the archive's evidentiary weight
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
Pricing, plan by plan
BackToMe
€25/month- Monthly€25/mo
- Per active store, excluding VAT
- Unlimited withdrawal requests
- 24 EU languages
- Annual€250/yr
- Per store, excluding VAT
- Two months free against the monthly rate
- Everything in the monthly plan
etcd
On requestNo published plan breakdown. See the etcd review.
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Questions people ask
- Is BackToMe or etcd better?
- Neither clearly leads. BackToMe starts at €25/month and etcd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or etcd?
- BackToMe starts at €25/month and etcd at On request.
- Does BackToMe or etcd run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- What is BackToMe best used for?
- BackToMe is most often used for meeting eu directive 2023/2673 withdrawal obligations, producing dated proof of a cancellation in a customer dispute, handling withdrawal requests across several eu languages, running one withdrawal process across multiple storefronts. Of those, meeting eu directive 2023/2673 withdrawal obligations and producing dated proof of a cancellation in a customer dispute are not what etcd is typically brought in for.
- What can BackToMe do that etcd cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. etcd covers Raft consensus, Linearizable reads, Transactions, Leases.
Answered from the vendors’ own pages
BackToMe: What does BackToMe cost?
25 euros excluding VAT per month per active store, or 250 euros excluding VAT per year, which works out at two months free. The price does not change with the number of withdrawal requests.
Sourceetcd: 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.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
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.
BackToMe: Is there a free trial?
Seven days. A card is required to start it but nothing is charged upfront, and cancelling before day seven costs nothing. There is also a 30-day money-back guarantee.
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.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
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.
BackToMe: What happens to the archive if I cancel?
Cancellation is available at any time with no commitment, premium access runs to the end of the paid period, and the account stays open with archived withdrawals and proofs accessible indefinitely. Reactivation is self-service.
Sourceetcd: 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.
BackToMe: Which e-commerce platforms does it support?
Shopify, WordPress, WooCommerce, PrestaShop, Wix, Webflow, WiziShop and Squarespace, plus custom builds through a single line of script. The vendor puts installation at five minutes on any platform.
SourceRelated pages
Other head to heads
- BackToMe vs Temu
- BackToMe vs Amazon Shopping
- BackToMe vs Mailchimp
- BackToMe vs Shein
- BackToMe vs CJ Dropshipping
- BackToMe vs Memberful
- BackToMe vs Wish
- BackToMe vs Zendrop
- BackToMe vs Heartland Retail
- BackToMe vs Vinted
- BackToMe vs Mollie
- BackToMe vs TikTok Shop
- BackToMe vs SamCart
- BackToMe vs Sellfy
- BackToMe vs Shopware
- BackToMe vs Spree Commerce
- BackToMe vs Swell Commerce
- BackToMe vs Toast
- BackToMe vs DynamoDB
- BackToMe vs Timeplus
- BackToMe vs Firebase Realtime Database
- BackToMe vs Knack
- BackToMe vs Turso
- BackToMe vs BigQuery
- BackToMe vs TiDB
- BackToMe vs Dgraph
- BackToMe vs turbopuffer
- BackToMe vs Apache Kafka
- BackToMe vs Redis
- BackToMe vs Fivetran HVR
- BackToMe vs Grist
- BackToMe vs IBM Db2
- BackToMe vs Instaclustr
- BackToMe vs LanceDB
- BackToMe vs Marqo
- BackToMe vs Apache Airflow
- etcd vs Temu
- etcd vs Amazon Shopping
- etcd vs Mailchimp
- etcd vs Shein
- etcd vs CJ Dropshipping
- etcd vs Memberful
- etcd vs Wish
- etcd vs Zendrop
- etcd vs Heartland Retail
- etcd vs Vinted
- etcd vs Mollie
- etcd vs TikTok Shop
- etcd vs SamCart
- etcd vs Sellfy
- etcd vs Shopware
- etcd vs Spree Commerce
- etcd vs Swell Commerce
- etcd vs Toast
- 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 Fivetran HVR
- etcd vs Grist
- etcd vs IBM Db2
- etcd vs Instaclustr
- etcd vs LanceDB
- etcd vs Marqo
- etcd vs Apache Airflow
