E-Commerce · head to head
BackToMe vs DuckDB

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

DuckDB
Databases
MIT-licensed analytical SQL database that runs inside your process, with no server, no dependencies and one writer at a time.
- From
- Free
- Free plan
- Yes
The short version
- DuckDB is free; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only DuckDB lists in-process execution.
- 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 DuckDB 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 DuckDB
- In-process execution
- Vectorised columnar engine
- Direct file querying
- Zero dependencies
- Larger-than-memory queries
- MIT licence
- Postgres-flavoured SQL
- Extension ecosystem
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot DuckDB
- Producing dated proof of a cancellation in a customer disputenot DuckDB
- Handling withdrawal requests across several EU languagesnot DuckDB
- Running one withdrawal process across multiple storefrontsnot DuckDB
- Passing a consumer-protection audit with exportable recordsnot DuckDB
DuckDB
- Transformation steps in a data pipeline that would otherwise need Spark, replaced by SQL over Parquet in a single processnot BackToMe
- Analytical queries embedded in an application or a dashboard where shipping a database server alongside it is not acceptablenot BackToMe
- Local exploration of files that are too large for a pandas dataframe but far too small to justify a warehousenot BackToMe
- Continuous integration and testing of analytical SQL, where a real engine can run in the test process without provisioning anythingnot 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
DuckDB
- A database file accepts one read-write process at a time; other processes must open it read-only and will not see subsequent writes, so DuckDB cannot be the shared database behind several services
- There is no network protocol, authentication or user management, so exposing it to remote clients means writing and securing your own service around it
- It is built for scans and aggregations, not for many small transactions, so a workload of high-frequency single-row inserts and updates performs badly compared with SQLite or Postgres
- Storage files are backwards compatible but not forwards compatible, so a file written by a newer version cannot be read by an older one and every consumer of a shared file must be upgraded together
- Query memory settings matter: some operations still need to hold significant state, so an under-configured memory limit turns a large join or a high-cardinality aggregation into a spill-heavy query or an out-of-memory failure rather than a slow success
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
DuckDB
FreeNo published plan breakdown. See the DuckDB review.
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose DuckDB if
- You need in-process execution.
- You want to start without paying.
- You work on Linux, macOS, Windows, Web.
- You also want vectorised columnar engine.
Questions people ask
- Is BackToMe or DuckDB better?
- Neither clearly leads. BackToMe starts at €25/month and DuckDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or DuckDB?
- DuckDB has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for DuckDB.
- Does BackToMe or DuckDB run on more platforms?
- BackToMe runs on Web. DuckDB runs on Linux, macOS, Windows, Web.
- Can I use DuckDB for free?
- Yes. DuckDB 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 DuckDB is typically brought in for.
- What can BackToMe do that DuckDB cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. DuckDB covers In-process execution, Vectorised columnar engine, Direct file querying, Zero dependencies.
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.
SourceDuckDB: Can multiple applications share one DuckDB database?
Not for writing. One process holds the database read-write; others may attach read-only and will not see later writes. Shared multi-writer access needs a different database or a table format with a catalogue.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceDuckDB: Is it a replacement for a data warehouse?
For single-node analytical workloads up to a few hundred gigabytes it very often is. It is not a replacement when many concurrent users need a shared, governed, always-on service.
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.
SourceDuckDB: Do I have to load data into it?
No. It queries Parquet, CSV, JSON and Arrow in place, including on object storage. Its own storage format is optional and mainly useful when you want indexes, constraints and faster repeated access.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceDuckDB: What is MotherDuck's relationship to it?
MotherDuck is a separate company offering a managed and hybrid service built on the DuckDB engine. DuckDB itself remains MIT-licensed and independent of it, with the IP held by the DuckDB Foundation.
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.
SourceDuckDB: Is it suitable for OLTP?
No. It is designed for analytical scans. For transactional workloads with frequent small writes, SQLite or Postgres is the right tool.
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 SingleStore
- BackToMe vs SQLite
- BackToMe vs ClickHouse
- BackToMe vs Apache Druid
- BackToMe vs Firebolt
- BackToMe vs OpenSearch
- BackToMe vs StarRocks
- BackToMe vs QuestDB
- BackToMe vs BigQuery
- BackToMe vs Elasticsearch
- BackToMe vs Materialize
- BackToMe vs Oracle Database
- BackToMe vs TimescaleDB
- BackToMe vs Trino
- BackToMe vs Turso
- BackToMe vs Amazon RDS
- BackToMe vs Apache Pinot
- BackToMe vs Apache Flink
- DuckDB vs Temu
- DuckDB vs Amazon Shopping
- DuckDB vs Mailchimp
- DuckDB vs Shein
- DuckDB vs CJ Dropshipping
- DuckDB vs Memberful
- DuckDB vs Wish
- DuckDB vs Zendrop
- DuckDB vs Heartland Retail
- DuckDB vs Vinted
- DuckDB vs Mollie
- DuckDB vs TikTok Shop
- DuckDB vs SamCart
- DuckDB vs Sellfy
- DuckDB vs Shopware
- DuckDB vs Spree Commerce
- DuckDB vs Swell Commerce
- DuckDB vs Toast
- DuckDB vs SingleStore
- DuckDB vs SQLite
- DuckDB vs ClickHouse
- DuckDB vs Apache Druid
- DuckDB vs Firebolt
- DuckDB vs OpenSearch
- DuckDB vs StarRocks
- DuckDB vs QuestDB
- DuckDB vs BigQuery
- DuckDB vs Elasticsearch
- DuckDB vs Materialize
- DuckDB vs Oracle Database
- DuckDB vs TimescaleDB
- DuckDB vs Trino
- DuckDB vs Turso
- DuckDB vs Amazon RDS
- DuckDB vs Apache Pinot
- DuckDB vs Apache Flink
