E-Commerce · head to head
BackToMe vs LanceDB

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

LanceDB
Databases
Embedded retrieval library over the Apache 2.0 Lance columnar format, with proprietary Cloud and Enterprise tiers for serving at scale.
- From
- On request
- Free plan
- No
The short version
- LanceDB is a library, not a server.
- BackToMe starts at €25/mo; LanceDB prices on request.
- Only BackToMe lists floating withdrawal button; only LanceDB lists embedded operation.
- 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 LanceDB 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 LanceDB
- Embedded operation
- Lance columnar format
- Object storage native
- Multimodal storage
- Vector indexes
- Full-text and hybrid search
- Scalar filtering
- Dataset versioning
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot LanceDB
- Producing dated proof of a cancellation in a customer disputenot LanceDB
- Handling withdrawal requests across several EU languagesnot LanceDB
- Running one withdrawal process across multiple storefrontsnot LanceDB
- Passing a consumer-protection audit with exportable recordsnot LanceDB
LanceDB
- Retrieval over a dataset that includes images, audio or video, where keeping the embeddings and the source media in one format avoids a second storage systemnot BackToMe
- A training and retrieval pipeline that must read the same rows for both purposes without maintaining two copies and a sync jobnot BackToMe
- Prototyping search locally with the same code path that later runs against S3, with no local server to installnot BackToMe
- Keeping a large, mostly cold vector corpus on object storage rather than paying to hold it in memory in a conventional vector databasenot 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
LanceDB
- The open source build is a library with no network endpoint, authentication or tenancy model, so exposing it to more than one application means writing your own service in front of it and handing every consumer credentials to the bucket
- Queries that miss the cache pay object storage round trips, so interactive latency depends on local SSD caching or the Enterprise serving tier rather than on the library itself
- Concurrent writers to the same dataset coordinate through commits on the object store, so multi-writer setups can conflict and the safe pattern is a single writer per table, which is an architectural constraint on your ingest design
- Newly written rows are not in the index until the index is rebuilt or updated, and until then they are searched by brute force, so recall and latency drift between reindexing jobs that you have to schedule and pay for
- The capabilities that make it operable at scale, distributed index building, managed caching and hosted serving, live in the proprietary Cloud and Enterprise tiers, so the open licence protects the data but not the production deployment
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
LanceDB
On requestNo published plan breakdown. See the LanceDB review.
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Questions people ask
- Is BackToMe or LanceDB better?
- Neither clearly leads. BackToMe starts at €25/month and LanceDB at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or LanceDB?
- BackToMe starts at €25/month and LanceDB at On request.
- Does BackToMe or LanceDB 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 LanceDB is typically brought in for.
- What can BackToMe do that LanceDB cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. LanceDB covers Embedded operation, Lance columnar format, Object storage native, Multimodal storage.
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.
SourceLanceDB: Is LanceDB open source?
The LanceDB library and the underlying Lance format are Apache 2.0. LanceDB Cloud and LanceDB Enterprise are proprietary managed products built on top of them.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceLanceDB: Do I need the managed service?
Not for development or for embedded use in a single application. You typically need it when many clients must query concurrently with predictable latency, or when index builds outgrow one machine.
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.
SourceLanceDB: Can other tools read my data?
Yes. Lance datasets are readable from DuckDB, Polars, Pandas, PyArrow and PyTorch, which is the main practical difference from a vector database that owns its own storage.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceLanceDB: How does it compare to pgvector?
pgvector keeps vectors next to relational data in a database you already run. LanceDB keeps them in object storage in a format built for random access and multimodal payloads, and scales storage independently of any server.
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.
SourceLanceDB: What happens to updates and deletes?
Writes append new fragments and mark old rows deleted, with compaction reclaiming space later, so a workload with heavy in-place updates accumulates overhead until compaction runs.
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 DuckDB
- BackToMe vs BigQuery
- BackToMe vs DynamoDB
- BackToMe vs Trino
- BackToMe vs Chroma
- BackToMe vs Convex
- BackToMe vs Dremio
- BackToMe vs Teradata
- BackToMe vs turbopuffer
- BackToMe vs Zilliz
- BackToMe vs Apache Druid
- BackToMe vs Elasticsearch
- BackToMe vs PlanetScale
- BackToMe vs Redis
- BackToMe vs Supabase
- BackToMe vs Meilisearch
- BackToMe vs Apache Pulsar
- BackToMe vs Apache Airflow
- LanceDB vs Temu
- LanceDB vs Amazon Shopping
- LanceDB vs Mailchimp
- LanceDB vs Shein
- LanceDB vs CJ Dropshipping
- LanceDB vs Memberful
- LanceDB vs Wish
- LanceDB vs Zendrop
- LanceDB vs Heartland Retail
- LanceDB vs Vinted
- LanceDB vs Mollie
- LanceDB vs TikTok Shop
- LanceDB vs SamCart
- LanceDB vs Sellfy
- LanceDB vs Shopware
- LanceDB vs Spree Commerce
- LanceDB vs Swell Commerce
- LanceDB vs Toast
- LanceDB vs DuckDB
- LanceDB vs BigQuery
- LanceDB vs DynamoDB
- LanceDB vs Trino
- LanceDB vs Chroma
- LanceDB vs Convex
- LanceDB vs Dremio
- LanceDB vs Teradata
- LanceDB vs turbopuffer
- LanceDB vs Zilliz
- LanceDB vs Apache Druid
- LanceDB vs Elasticsearch
- LanceDB vs PlanetScale
- LanceDB vs Redis
- LanceDB vs Supabase
- LanceDB vs Meilisearch
- LanceDB vs Apache Pulsar
- LanceDB vs Apache Airflow
