E-Commerce · head to head
BackToMe vs EMQX

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

EMQX
Databases
Erlang MQTT broker for large IoT fleets, relicensed to BSL with production free use limited to one node
- From
- Free
- Free plan
- Yes
The short version
- EMQX has a free plan, then $234/mo; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only EMQX lists erlang clustering.
- 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 EMQX 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 EMQX
- Erlang clustering
- MQTT 5.0 and QUIC
- Rule engine
- Data integration sinks
- Session persistence
- Multi protocol gateways
- Authentication and authorisation
- Dashboard and REST API
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot EMQX
- Producing dated proof of a cancellation in a customer disputenot EMQX
- Handling withdrawal requests across several EU languagesnot EMQX
- Running one withdrawal process across multiple storefrontsnot EMQX
- Passing a consumer-protection audit with exportable recordsnot EMQX
EMQX
- A connected vehicle platform needing millions of persistent MQTT sessions with QUIC for handover across mobile networksnot BackToMe
- An industrial operator routing sensor telemetry straight into TimescaleDB or Kafka without writing a consumer servicenot BackToMe
- An IoT product team that has outgrown a single Mosquitto instance and needs clustering and shared subscriptionsnot BackToMe
- A smart building deployment mixing MQTT, CoAP and LwM2M devices on one brokernot 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
EMQX
- The move to Business Source Licence 1.1 at version 5.9 in May 2025 limits free production use to a single node, so the clustering that justifies choosing EMQX now requires a paid subscription from the second node onward
- The relicensing arrived in a minor release, which caught users who had pinned to 5.x expecting Apache 2.0 terms and forced legal review of existing deployments
- Running an Erlang/OTP cluster well requires operational knowledge most teams do not have, and diagnosing distribution, mnesia or memory issues means learning a runtime you use for nothing else
- Enterprise pricing is quoted rather than published for the self-managed edition, so the cost of the clustered configuration you actually need is invisible until you talk to sales
- The Serverless tier caps at around a thousand connections and shares infrastructure, which makes it a prototyping tier rather than a genuine small production option
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
EMQX
Free- Open Source single nodeFree
- BSL 1.1 licence since version 5.9
- Free production use of one node only
- All former enterprise features visible
- ServerlessFree
- Free monthly quota then pay as you go
- Up to 1,000 connections
- 8 by 5 support
- Dedicated Flex$234/mo
- Single tenant cluster
- Traffic allowance included
- 24/7 support
- Enterprise self-managedOn request
- Deploy on premises, at the edge or in any cloud
- Clustering licensed
- 256 MB maximum message size
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose EMQX if
- You need erlang clustering.
- You want to start without paying.
- You work on Linux, Self-hosted, Web, macOS.
- You also want mqtt 5.0 and quic.
Questions people ask
- Is BackToMe or EMQX better?
- Neither clearly leads. BackToMe starts at €25/month and EMQX at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or EMQX?
- EMQX has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for EMQX.
- Does BackToMe or EMQX run on more platforms?
- BackToMe runs on Web. EMQX runs on Linux, Self-hosted, Web, macOS.
- Can I use EMQX for free?
- Yes. EMQX 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 EMQX is typically brought in for.
- What can BackToMe do that EMQX cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. EMQX covers Erlang clustering, MQTT 5.0 and QUIC, Rule engine, Data integration sinks.
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.
SourceEMQX: Is EMQX still open source?
Not in the OSI sense since version 5.9. It is source-available under Business Source Licence 1.1, reverting to Apache 2.0 four years after each release.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceEMQX: Can I run a free cluster?
No. The additional use grant permits free production use of one node; clustering requires a commercial licence.
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.
SourceEMQX: What changed for existing users?
Community and enterprise editions merged, so all features are now visible, but the licence terms tightened in the same minor release.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceEMQX: Which version is still Apache 2.0?
Releases before 5.9 remain under Apache 2.0, and each BSL release converts to Apache 2.0 four years after publication.
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 VerneMQ
- BackToMe vs RabbitMQ
- BackToMe vs NATS
- BackToMe vs Solace PubSub+
- BackToMe vs Canary Labs
- BackToMe vs TIBCO Enterprise Message Service
- BackToMe vs TimescaleDB
- BackToMe vs Turso
- BackToMe vs Chroma
- BackToMe vs Redis
- BackToMe vs DuckDB
- BackToMe vs Trino
- BackToMe vs Xata
- BackToMe vs YugabyteDB
- BackToMe vs Zilliz
- BackToMe vs Airtable
- BackToMe vs Cockroach Labs
- BackToMe vs PostgreSQL
- EMQX vs Temu
- EMQX vs Amazon Shopping
- EMQX vs Mailchimp
- EMQX vs Shein
- EMQX vs CJ Dropshipping
- EMQX vs Memberful
- EMQX vs Wish
- EMQX vs Zendrop
- EMQX vs Heartland Retail
- EMQX vs Vinted
- EMQX vs Mollie
- EMQX vs TikTok Shop
- EMQX vs SamCart
- EMQX vs Sellfy
- EMQX vs Shopware
- EMQX vs Spree Commerce
- EMQX vs Swell Commerce
- EMQX vs Toast
- EMQX vs VerneMQ
- EMQX vs RabbitMQ
- EMQX vs NATS
- EMQX vs Solace PubSub+
- EMQX vs Canary Labs
- EMQX vs TIBCO Enterprise Message Service
- EMQX vs TimescaleDB
- EMQX vs Turso
- EMQX vs Chroma
- EMQX vs Redis
- EMQX vs DuckDB
- EMQX vs Trino
- EMQX vs Xata
- EMQX vs YugabyteDB
- EMQX vs Zilliz
- EMQX vs Airtable
- EMQX vs Cockroach Labs
- EMQX vs PostgreSQL
