Softwr

E-Commerce · head to head

BackToMe vs Trino

BackToMe logo

BackToMe

E-Commerce

Right-of-withdrawal handling for European e-commerce

From
€25/month
Free plan
No
Trino logo

Trino

Databases

A distributed SQL engine that queries data where it already lives, across object storage, warehouses and operational databases.

From
Free
Free plan
Yes

The short version

  • Trino is free; BackToMe starts at €25/mo.
  • Only BackToMe lists floating withdrawal button; only Trino lists federated querying.
  • 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 Trino actually diverge.

Attributes where BackToMe and Trino differ
AttributeBackToMeTrino
Starting price€25/monthFree
Pricing modelSubscriptionOpen-source
Free tierNoYes
CategoryE-CommerceDatabases

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 Trino

  • Federated querying
  • Connector architecture
  • Predicate and aggregation pushdown
  • Massively parallel execution
  • Fault-tolerant execution
  • Resource groups
  • Iceberg and Delta table support
  • Standard client protocols

What people use each for

The jobs each tool is most often brought in to do.

BackToMe

  • Meeting EU Directive 2023/2673 withdrawal obligationsnot Trino
  • Producing dated proof of a cancellation in a customer disputenot Trino
  • Handling withdrawal requests across several EU languagesnot Trino
  • Running one withdrawal process across multiple storefrontsnot Trino
  • Passing a consumer-protection audit with exportable recordsnot Trino

Trino

  • Ad hoc analysis that spans a data lake and one or more operational databases, without building an ingestion pipeline firstnot BackToMe
  • Serving a BI tool a single SQL endpoint over an estate that is actually several separate storage systemsnot BackToMe
  • Querying Iceberg or Delta tables on object storage interactively, as the compute layer of a lakehousenot BackToMe
  • Investigating whether a dataset is worth ingesting, by querying it in place before committing to a pipeline for itnot 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

Trino

  • Trino stores nothing and computes no statistics of its own, so the plan it produces is only as good as the partitioning, file sizes and table statistics on the source; a Hive table of thousands of small files or a lake with no stats produces a slow query the engine cannot improve
  • Federated queries pull data out of the systems they touch, so a join between a lake table and a production Postgres can put a full table scan onto an OLTP database that other applications depend on, and the person who wrote the query will not see the incident it causes
  • Releases come roughly every one to two weeks with no community long-term support line, and deprecations arrive quickly, so you either dedicate someone to keeping current or you buy Starburst Enterprise for a supported long-term version
  • It is memory-based and disk spilling was deprecated in favour of fault-tolerant execution, so a query exceeding cluster memory fails outright rather than degrading; enabling fault-tolerant execution requires an external exchange store on object storage and makes queries measurably slower
  • It is a query engine and not a warehouse: there is no built-in job scheduling, no incremental materialised view maintenance and no transformation framework, so producing curated tables still needs dbt or an equivalent layer that somebody has to own
  • The 2020 fork split the ecosystem, so documentation, connectors, Stack Overflow answers and vendor material written before then describe PrestoDB, which is now a different project with different behaviour, and following the wrong one wastes real time

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

Trino

Free

No published plan breakdown. See the Trino review.

Which should you pick?

Choose BackToMe if

  • You need floating withdrawal button.
  • You also want automatic acknowledgement.

Choose Trino if

  • You need federated querying.
  • You want to start without paying.
  • You also want connector architecture.

Questions people ask

Is BackToMe or Trino better?
Neither clearly leads. BackToMe starts at €25/month and Trino at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, BackToMe or Trino?
Trino has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for Trino.
Does BackToMe or Trino run on more platforms?
Both run on Web, so platform support will not decide this one for you.
Can I use Trino for free?
Yes. Trino 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 Trino is typically brought in for.
What can BackToMe do that Trino cannot?
BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. Trino covers Federated querying, Connector architecture, Predicate and aggregation pushdown, Massively parallel execution.

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.

Source
Trino: What is the difference between Trino and Presto?

They share an origin. The original creators left Meta and renamed their fork from PrestoSQL to Trino in December 2020; PrestoDB continues separately under the Linux Foundation. They have diverged in features, connectors and SQL behaviour, so material written for one may not apply to the other.

BackToMe: Which regulation does it address?

EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.

Source
Trino: Does Trino replace my data warehouse?

Not on its own. It is compute without storage, scheduling or transformation. Paired with Iceberg or Delta on object storage and something like dbt for modelling it can serve as a lakehouse; used alone it is a query layer over what you already have.

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.

Source
Trino: Why is my federated query slow?

Usually because a connector could not push a filter or aggregation down, so Trino is pulling whole tables across the network to join them itself. The fix is usually better source-side partitioning or statistics, or ingesting that source rather than federating it.

BackToMe: Are staging and development stores billed?

No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.

Source
Trino: What happens when a query runs out of memory?

It fails. Disk spilling was deprecated in favour of fault-tolerant execution, which checkpoints to an external exchange store such as S3 and lets long queries survive memory pressure and worker loss, at the cost of noticeably slower execution.

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.

Source
Trino: Is there commercial support?

Yes, from Starburst, which offers Starburst Enterprise with long-term supported releases and Starburst Galaxy as a managed service. The open source project itself has no long-term support line.

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.

Source
Share

Related pages

Other head to heads