E-Commerce · head to head
BackToMe vs Chroma

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

Chroma
Databases
Apache 2.0 vector and full-text search engine that runs as an embedded library, a single server or a distributed cloud service.
- From
- Free
- Free plan
- Yes
The short version
- Chroma has a free plan, then $250/mo; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only Chroma lists embedded mode.
- 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 Chroma 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 Chroma
- Embedded mode
- Single-node server
- Distributed architecture
- Vector search
- Full-text search
- Metadata filtering
- Consistent API across modes
- Multi-language clients
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot Chroma
- Producing dated proof of a cancellation in a customer disputenot Chroma
- Handling withdrawal requests across several EU languagesnot Chroma
- Running one withdrawal process across multiple storefrontsnot Chroma
- Passing a consumer-protection audit with exportable recordsnot Chroma
Chroma
- Prototyping retrieval-augmented generation where the priority is having a working index in minutes rather than choosing a permanent storenot BackToMe
- Agent memory in a single application process, where an embedded store avoids adding a network dependencynot BackToMe
- A departmental search application under roughly ten million records where one server is sufficient and simplicity is worth more than headroomnot BackToMe
- Local and CI testing of retrieval code with the same client library used in productionnot 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
Chroma
- On a single node, available memory sets a hard upper bound on collection size, roughly 245,000 records per gigabyte of RAM at 1024 dimensions, so capacity planning is a memory purchase and the ceiling arrives without warning
- Single-node queries parallelise only up to the number of vCPUs, after which requests queue and latency rises linearly with concurrency, so throughput problems appear as a slow application rather than as errors
- The distributed deployment behind Chroma Cloud is a different architecture from the embedded library, so latency, consistency and failure behaviour observed in a local prototype do not predict production behaviour
- The open source server has no built-in authentication or multi-tenancy worth relying on, so a self-hosted deployment needs its own auth proxy and network controls before anything untrusted can reach it
- The project has moved quickly through major internal rewrites and version changes, so upgrades have historically involved data migrations and client changes, and pinning versions is necessary rather than cautious
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
Chroma
Free- StarterFree
- 10 databases
- 10 team members
- Community Slack access
- Team$250/mo
- 100 databases
- 30 team members
- $100 in included credits
- EnterpriseOn request
- Unlimited databases
- Unlimited team members
- Dedicated support
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose Chroma if
- You need embedded mode.
- You want to start without paying.
- You also want single-node server.
Questions people ask
- Is BackToMe or Chroma better?
- Neither clearly leads. BackToMe starts at €25/month and Chroma at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or Chroma?
- Chroma has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for Chroma.
- Does BackToMe or Chroma run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Chroma for free?
- Yes. Chroma 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 Chroma is typically brought in for.
- What can BackToMe do that Chroma cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. Chroma covers Embedded mode, Single-node server, Distributed architecture, Vector search.
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.
SourceChroma: Do I need to run a server?
No. Chroma runs embedded in your process with persistence to a local directory, which is how most projects start. The server and distributed modes exist for when multiple clients or larger collections require them.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceChroma: How large can a single node get?
The project puts single-node deployments at fewer than about ten million records across a handful of collections, with collection size bounded by system memory at roughly 245,000 records per gigabyte at 1024 dimensions.
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.
SourceChroma: Is Chroma Cloud the same software?
It is the same API and project, but the distributed deployment is a different architecture, using independent services, object storage and SSD caches rather than a single process. Behaviour under load differs accordingly.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceChroma: How does it compare with pgvector?
pgvector keeps vectors in a Postgres database you already operate, with SQL, joins and transactions. Chroma is a dedicated retrieval engine with a lower setup cost and a retrieval-shaped API. If you already run Postgres, pgvector removes a system; if you do not, Chroma removes a decision.
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.
SourceChroma: What licence is it under?
Apache 2.0, which permits self-hosting and embedding in commercial products without a competing-use restriction.
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 turbopuffer
- BackToMe vs Vespa
- BackToMe vs Qdrant
- BackToMe vs SQLite
- BackToMe vs Timeplus
- BackToMe vs EMQX
- BackToMe vs LanceDB
- BackToMe vs Presto
- BackToMe vs Zilliz
- BackToMe vs Elasticsearch
- BackToMe vs Redis
- BackToMe vs Apache Pinot
- BackToMe vs DataGrip
- BackToMe vs Estuary
- BackToMe vs Apache Pulsar
- BackToMe vs Cassandra
- BackToMe vs CouchDB
- Chroma vs Temu
- Chroma vs Amazon Shopping
- Chroma vs Mailchimp
- Chroma vs Shein
- Chroma vs CJ Dropshipping
- Chroma vs Memberful
- Chroma vs Wish
- Chroma vs Zendrop
- Chroma vs Heartland Retail
- Chroma vs Vinted
- Chroma vs Mollie
- Chroma vs TikTok Shop
- Chroma vs SamCart
- Chroma vs Sellfy
- Chroma vs Shopware
- Chroma vs Spree Commerce
- Chroma vs Swell Commerce
- Chroma vs Toast
- Chroma vs DuckDB
- Chroma vs turbopuffer
- Chroma vs Vespa
- Chroma vs Qdrant
- Chroma vs SQLite
- Chroma vs Timeplus
- Chroma vs EMQX
- Chroma vs LanceDB
- Chroma vs Presto
- Chroma vs Zilliz
- Chroma vs Elasticsearch
- Chroma vs Redis
- Chroma vs Apache Pinot
- Chroma vs DataGrip
- Chroma vs Estuary
- Chroma vs Apache Pulsar
- Chroma vs Cassandra
- Chroma vs CouchDB
