E-Commerce · head to head
BackToMe vs StarRocks

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

StarRocks
Databases
Apache 2.0 MPP analytical database built for joins on open table formats
- From
- Free
- Free plan
- Yes
The short version
- StarRocks is free; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only StarRocks lists cost-based optimiser.
- 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 StarRocks actually diverge.
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 StarRocks
- Cost-based optimiser
- Lakehouse query engine
- Primary key tables
- Materialised views
- Shared-data mode
- MySQL wire protocol
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot StarRocks
- Producing dated proof of a cancellation in a customer disputenot StarRocks
- Handling withdrawal requests across several EU languagesnot StarRocks
- Running one withdrawal process across multiple storefrontsnot StarRocks
- Passing a consumer-protection audit with exportable recordsnot StarRocks
StarRocks
- Customer-facing analytics where queries join a fact table to several dimensions and must return in well under a secondnot BackToMe
- Querying an Iceberg lakehouse directly without copying data into a proprietary warehouse formatnot BackToMe
- Replacing a ClickHouse deployment that has become unmanageable because every new question needs another denormalised tablenot BackToMe
- Real-time analytics fed by change data capture where rows must be updated in place rather than appendednot 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
StarRocks
- Self-hosting is a genuine operations job: frontend and backend node roles, tablet distribution, compaction and materialised view refresh all need an owner, and there is no small-team-friendly single-binary mode
- CelerData is by far the dominant contributor despite Linux Foundation stewardship, so the practical roadmap risk is the same as any single-vendor open source project
- It inherits a MySQL-flavoured SQL dialect from its Doris ancestry, so queries written for PostgreSQL, Snowflake or Trino need rewriting rather than porting
- Ecosystem support is thinner than ClickHouse or Trino: fewer client libraries, fewer managed hosting options and a much smaller pool of engineers who have run it in production
- Memory pressure under concurrent large joins is a common production failure, and the tuning knobs for query memory limits are unforgiving compared with a cloud warehouse that just scales
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
StarRocks
Free- StarRocksFree
- Apache 2.0 licence
- Linux Foundation governance
- No usage or node limits
- CelerData CloudOn request
- Managed StarRocks from the primary contributor
- BYOC and serverless deployment options
- Enterprise support and SLAs
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose StarRocks if
- You need cost-based optimiser.
- You want to start without paying.
- You work on Linux, Self-hosted.
- You also want lakehouse query engine.
Questions people ask
- Is BackToMe or StarRocks better?
- Neither clearly leads. BackToMe starts at €25/month and StarRocks at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or StarRocks?
- StarRocks has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for StarRocks.
- Does BackToMe or StarRocks run on more platforms?
- BackToMe runs on Web. StarRocks runs on Linux, Self-hosted.
- Can I use StarRocks for free?
- Yes. StarRocks 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 StarRocks is typically brought in for.
- What can BackToMe do that StarRocks cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. StarRocks covers Cost-based optimiser, Lakehouse query engine, Primary key tables, Materialised views.
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.
SourceStarRocks: Is StarRocks open source?
Yes, Apache 2.0, governed under the Linux Foundation since 2023.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceStarRocks: How does it differ from ClickHouse?
StarRocks is built for joins across a star schema with a cost-based optimiser; ClickHouse is fastest on denormalised single tables.
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.
SourceStarRocks: Who maintains it?
CelerData, formerly StarRocks Inc, is the dominant contributor and sells the managed service.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceStarRocks: Can it query Iceberg tables directly?
Yes, along with Hudi, Delta Lake, Hive and Paimon, with a local cache for repeat queries.
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.
SourceBackToMe: 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 ClickHouse
- BackToMe vs Apache Druid
- BackToMe vs Trino
- BackToMe vs Presto
- BackToMe vs DuckDB
- BackToMe vs Dremio
- BackToMe vs Aiven
- BackToMe vs Typesense
- BackToMe vs VerneMQ
- BackToMe vs PostgreSQL
- BackToMe vs DataGrip
- BackToMe vs Estuary
- BackToMe vs Firebolt
- BackToMe vs Apache Doris
- BackToMe vs Apache Kafka
- BackToMe vs Apache Pulsar
- BackToMe vs Cassandra
- BackToMe vs CouchDB
- StarRocks vs Temu
- StarRocks vs Amazon Shopping
- StarRocks vs Mailchimp
- StarRocks vs Shein
- StarRocks vs CJ Dropshipping
- StarRocks vs Memberful
- StarRocks vs Wish
- StarRocks vs Zendrop
- StarRocks vs Heartland Retail
- StarRocks vs Vinted
- StarRocks vs Mollie
- StarRocks vs TikTok Shop
- StarRocks vs SamCart
- StarRocks vs Sellfy
- StarRocks vs Shopware
- StarRocks vs Spree Commerce
- StarRocks vs Swell Commerce
- StarRocks vs Toast
- StarRocks vs ClickHouse
- StarRocks vs Apache Druid
- StarRocks vs Trino
- StarRocks vs Presto
- StarRocks vs DuckDB
- StarRocks vs Dremio
- StarRocks vs Aiven
- StarRocks vs Typesense
- StarRocks vs VerneMQ
- StarRocks vs PostgreSQL
- StarRocks vs DataGrip
- StarRocks vs Estuary
- StarRocks vs Firebolt
- StarRocks vs Apache Doris
- StarRocks vs Apache Kafka
- StarRocks vs Apache Pulsar
- StarRocks vs Cassandra
- StarRocks vs CouchDB
