E-Commerce · head to head
BackToMe vs Turso

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

Turso
Databases
SQLite-lineage database platform for running very large numbers of small per-tenant databases, with an MIT-licensed engine.
- From
- Free
- Free plan
- Yes
The short version
- Turso has a free plan, then $4.99/mo; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only Turso lists per-tenant databases.
- 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 Turso actually diverge.
Identical on both: 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 Turso
- Per-tenant databases
- MIT licence
- Embedded replicas
- SQLite compatibility
- HTTP access
- Branching
- Point-in-time restore
- In-process engine
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot Turso
- Producing dated proof of a cancellation in a customer disputenot Turso
- Handling withdrawal requests across several EU languagesnot Turso
- Running one withdrawal process across multiple storefrontsnot Turso
- Passing a consumer-protection audit with exportable recordsnot Turso
Turso
- Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletionnot BackToMe
- Agent or session infrastructure that creates a throwaway database per task and destroys it afterwardsnot BackToMe
- Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returnsnot BackToMe
- Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problemnot 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
Turso
- SQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option
- Per-tenant databases mean per-tenant migrations, so every schema change becomes a fan-out job that must be idempotent and resumable, and multi-database schemas, the feature meant to solve this, is deprecated
- There are no cross-database queries; ATTACH is deprecated on the cloud, so any report or analytic spanning tenants must be assembled in your application or in a separate warehouse you also operate
- Data Edge, the multi-region edge replication that was Turso's original positioning, is deprecated, so a large share of the tutorials and articles describing Turso as an edge database describe behaviour you can no longer rely on
- Three engine lineages share the name, SQLite, the libSQL fork and the Rust rewrite, and the Rust engine is still maturing, so SQLite compatibility needs verifying against your specific pragmas, extensions and query patterns; the cloud already restricts journal_mode and busy_timeout and makes user_version read-only
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
Turso
Free- FreeFree
- 100 databases
- 5 GB storage
- 500M monthly rows read
- Developer$4.99/mo
- Unlimited databases
- 9 GB storage
- 2.5B monthly rows read
- Scaler$24.92/mo
- Unlimited databases
- 24 GB storage
- 100B monthly rows read
- Pro$416.58/mo
- Unlimited databases
- 50 GB storage
- 250B monthly rows read
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose Turso if
- You need per-tenant databases.
- You want to start without paying.
- You also want mit licence.
Questions people ask
- Is BackToMe or Turso better?
- Neither clearly leads. BackToMe starts at €25/month and Turso at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or Turso?
- Turso has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for Turso.
- Does BackToMe or Turso run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Turso for free?
- Yes. Turso 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 Turso is typically brought in for.
- What can BackToMe do that Turso cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. Turso covers Per-tenant databases, MIT licence, Embedded replicas, SQLite compatibility.
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.
SourceTurso: Is Turso just hosted SQLite?
Not exactly. It hosts databases built on the SQLite lineage: libSQL, an MIT fork of SQLite, and Turso Database, a newer Rust rewrite. The platform adds branching, backups, an HTTP API and programmatic database creation.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceTurso: Can I really run a million databases?
That is the design goal and the platform API exists to make provisioning and deletion programmatic. The practical constraints are the ones that come with it: migrations fan out, and nothing can query across databases.
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.
SourceTurso: How do embedded replicas handle read-after-write?
Reads come from the local replica and writes go to the primary, so a read immediately after a write can return stale data unless you wait for a sync. Application code has to account for that rather than assume it.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceTurso: What licence is it under?
libSQL and Turso Database are both MIT. Turso Cloud is a commercial managed service built on them, so the engine is genuinely open even though the platform is not.
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.
SourceTurso: Is Turso still an edge database?
No. Data Edge, the multi-region edge replication feature, is deprecated. The current positioning is per-tenant and embedded databases, and older material describing edge replication is out of date.
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 SurrealDB
- BackToMe vs MotherDuck
- BackToMe vs EMQX
- BackToMe vs DuckDB
- BackToMe vs Trino
- BackToMe vs Nile
- BackToMe vs SQLite
- BackToMe vs Teradata
- BackToMe vs Apache Kafka
- BackToMe vs BigQuery
- BackToMe vs Typesense
- BackToMe vs Apache Spark
- BackToMe vs IBM Db2
- BackToMe vs Instaclustr
- BackToMe vs Knack
- BackToMe vs LanceDB
- BackToMe vs Marqo
- BackToMe vs MongoDB
- Turso vs Temu
- Turso vs Amazon Shopping
- Turso vs Mailchimp
- Turso vs Shein
- Turso vs CJ Dropshipping
- Turso vs Memberful
- Turso vs Wish
- Turso vs Zendrop
- Turso vs Heartland Retail
- Turso vs Vinted
- Turso vs Mollie
- Turso vs TikTok Shop
- Turso vs SamCart
- Turso vs Sellfy
- Turso vs Shopware
- Turso vs Spree Commerce
- Turso vs Swell Commerce
- Turso vs Toast
- Turso vs SurrealDB
- Turso vs MotherDuck
- Turso vs EMQX
- Turso vs DuckDB
- Turso vs Trino
- Turso vs Nile
- Turso vs SQLite
- Turso vs Teradata
- Turso vs Apache Kafka
- Turso vs BigQuery
- Turso vs Typesense
- Turso vs Apache Spark
- Turso vs IBM Db2
- Turso vs Instaclustr
- Turso vs Knack
- Turso vs LanceDB
- Turso vs Marqo
- Turso vs MongoDB
