E-Commerce · head to head
BackToMe vs TiDB

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

TiDB
Databases
Apache 2.0 distributed SQL database with MySQL wire compatibility and a separate columnar replica for analytical queries.
- From
- Free
- Free plan
- Yes
The short version
- TiDB has a free plan, then $250/mo; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only TiDB lists MySQL wire compatibility.
- 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 17 September 2026.
Where they differ
Only the attributes on which BackToMe and TiDB actually diverge.
Not yet recorded: founded for BackToMe.
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 TiDB
- MySQL wire compatibility
- Horizontal write scaling
- Distributed ACID transactions
- TiFlash columnar replica
- Automatic rebalancing
- Raft replication
- Apache 2.0 licence
- Online schema change
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot TiDB
- Producing dated proof of a cancellation in a customer disputenot TiDB
- Handling withdrawal requests across several EU languagesnot TiDB
- Running one withdrawal process across multiple storefrontsnot TiDB
- Passing a consumer-protection audit with exportable recordsnot TiDB
TiDB
- A MySQL workload that has hit the write ceiling of a single primary and would otherwise need an application-level sharding layernot BackToMe
- Reporting that must run against current transactional data, where the columnar replica removes the delay and the cost of an ETL pipelinenot BackToMe
- Multi-region deployments needing a single logical database with automatic failover rather than manual primary promotionnot BackToMe
- Migrating off a sharded MySQL estate where the sharding logic in the application has become the main source of bugs and operational toilnot 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
TiDB
- A production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database
- Every transaction takes a timestamp from the placement driver and crosses the network to storage nodes, so simple point queries are slower than on single-node MySQL and latency-sensitive paths need to be measured, not assumed
- MySQL compatibility is at the wire and dialect level but not complete; stored procedures, triggers and events are not supported, so an application that pushed logic into the database cannot simply be repointed
- The columnar replica is an extra full copy of the data on its own nodes, so hybrid analytics roughly doubles storage and adds hardware that must be sized and paid for separately
- Operating it well requires cluster-specific expertise in TiUP or the Kubernetes operator, region hot spots, and rebalancing behaviour, so the licence is free but the running cost includes an engineer who understands distributed storage
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
TiDB
Free- ServerlessFree
- 5GB storage
- 50M request units
- Free forever tier
- Dedicated$250/mo
- Dedicated resources
- SLA guarantees
- Enterprise support
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose TiDB if
- You need mysql wire compatibility.
- You want to start without paying.
- You work on Web, AWS, Azure, Self-managed.
- You also want horizontal write scaling.
Questions people ask
- Is BackToMe or TiDB better?
- Neither clearly leads. BackToMe starts at €25/month and TiDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or TiDB?
- TiDB has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for TiDB.
- Does BackToMe or TiDB run on more platforms?
- BackToMe runs on Web. TiDB runs on Web, AWS, Azure, Self-managed.
- Can I use TiDB for free?
- Yes. TiDB has a free tier, so you can try it without paying. BackToMe starts at €25/month.
- 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 TiDB is typically brought in for.
- What can BackToMe do that TiDB cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. TiDB covers MySQL wire compatibility, Horizontal write scaling, Distributed ACID transactions, TiFlash columnar replica.
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.
SourceTiDB: Is TiDB a drop-in replacement for MySQL?
At the protocol and dialect level it is close, and most applications connect unchanged. Stored procedures, triggers and events are not supported, and latency characteristics differ, so it needs testing rather than assumption.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceTiDB: What licence is it under?
Apache 2.0, for both TiDB and the underlying TiKV storage engine. TiKV is a graduated CNCF project, which is a meaningful governance signal in a market where several competitors moved to source-available licences.
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.
SourceTiDB: Do I need TiFlash?
Only for analytical queries. It is an optional columnar replica; without it TiDB is a distributed transactional database. With it you get analytics on live data at the cost of an additional full copy.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceTiDB: Is the managed cloud the same software?
TiDB Cloud runs the same engine, with the control plane, scaling and operational tooling provided as a service. The entry tier is metered differently from a dedicated cluster, so the cost model rather than the engine is what changes.
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.
SourceTiDB: When is TiDB the wrong choice?
When the database is small enough for one server, when latency on single-row lookups is the primary constraint, or when the application depends on MySQL stored procedures and triggers.
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 Cockroach Labs
- BackToMe vs Vitess
- BackToMe vs Elasticsearch
- BackToMe vs SingleStore
- BackToMe vs BigQuery
- BackToMe vs DuckDB
- BackToMe vs Amazon Redshift
- BackToMe vs ClickHouse
- BackToMe vs Apache Druid
- BackToMe vs Couchbase
- BackToMe vs MariaDB
- BackToMe vs TimescaleDB
- BackToMe vs Dremio
- BackToMe vs etcd
- BackToMe vs Fivetran HVR
- BackToMe vs Grist
- BackToMe vs IBM Db2
- BackToMe vs Instaclustr
- TiDB vs Temu
- TiDB vs Amazon Shopping
- TiDB vs Mailchimp
- TiDB vs Shein
- TiDB vs CJ Dropshipping
- TiDB vs Memberful
- TiDB vs Wish
- TiDB vs Zendrop
- TiDB vs Heartland Retail
- TiDB vs Vinted
- TiDB vs Mollie
- TiDB vs TikTok Shop
- TiDB vs SamCart
- TiDB vs Sellfy
- TiDB vs Shopware
- TiDB vs Spree Commerce
- TiDB vs Swell Commerce
- TiDB vs Toast
- TiDB vs Cockroach Labs
- TiDB vs Vitess
- TiDB vs Elasticsearch
- TiDB vs SingleStore
- TiDB vs BigQuery
- TiDB vs DuckDB
- TiDB vs Amazon Redshift
- TiDB vs ClickHouse
- TiDB vs Apache Druid
- TiDB vs Couchbase
- TiDB vs MariaDB
- TiDB vs TimescaleDB
- TiDB vs Dremio
- TiDB vs etcd
- TiDB vs Fivetran HVR
- TiDB vs Grist
- TiDB vs IBM Db2
- TiDB vs Instaclustr
