E-Commerce · head to head
BackToMe vs RisingWave

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

RisingWave
Databases
Streaming database that maintains incremental materialised views in SQL instead of Flink jobs
- From
- Free
- Free plan
- Yes
The short version
- RisingWave has a free plan, then $0.227/mo; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only RisingWave lists SQL materialised views.
- 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 RisingWave actually diverge.
| Attribute | BackToMe | RisingWave |
|---|---|---|
| Starting price | €25/month | Free |
| Pricing model | Subscription | Per RisingWave Unit hour |
| Free tier | No | Yes |
| Platforms | Web | Linux, Self-hosted, Web |
| Category | E-Commerce | Databases |
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 RisingWave
- SQL materialised views
- Postgres wire compatibility
- Object storage state
- Source connectors
- Sink connectors
- Iceberg tables
- Watermarks and windowing
- User defined functions
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot RisingWave
- Producing dated proof of a cancellation in a customer disputenot RisingWave
- Handling withdrawal requests across several EU languagesnot RisingWave
- Running one withdrawal process across multiple storefrontsnot RisingWave
- Passing a consumer-protection audit with exportable recordsnot RisingWave
RisingWave
- A team with Kafka topics that needs continuously fresh aggregates for a dashboard without standing up a Flink clusternot BackToMe
- A fraud or risk team maintaining rolling counters and joins across event streams expressed as SQL viewsnot BackToMe
- A company doing Postgres CDC into a real-time denormalised view for search or servingnot BackToMe
- An analytics group that wants streaming results landed directly into Apache Iceberg without a separate writer jobnot 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
RisingWave
- Anything that does not fit SQL, such as custom windowing, complex event processing or heavy stateful logic, still needs Flink, so RisingWave often adds a system rather than removing one
- The Apache 2.0 community edition excludes premium features behind a licence key, and which capabilities sit on which side of that line moves between releases, so a self-hosted plan can be invalidated by an upgrade
- Long-running materialised views accumulate state in object storage, and cost and recovery time grow with retention in ways that are hard to forecast before you are in production
- The Postgres compatibility is protocol level; it is not a transactional Postgres and using it as a general purpose database, with point updates or high write concurrency, goes badly
- It is a comparatively young venture-funded project competing with Flink, Materialize and warehouse-native streaming, and the ecosystem of connectors, operators and third-party expertise is much thinner
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
RisingWave
Free- Community EditionFree
- Apache 2.0 licence, self-hosted
- Core streaming engine and connectors
- Premium features excluded and require a licence key
- Cloud Basic$0.227/hour
- Billed per RisingWave Unit hour
- Hosted on AWS, GCP or Azure
- Capped at 64 cores
- Cloud ProOn request
- No core limit
- Bring your own cloud option
- Premium features included
- Self-managed EnterpriseOn request
- On premises or Kubernetes
- Premium features unlocked by licence
- Annual contract with SLA
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose RisingWave if
- You need sql materialised views.
- You want to start without paying.
- You work on Linux, Self-hosted, Web.
- You also want postgres wire compatibility.
Questions people ask
- Is BackToMe or RisingWave better?
- Neither clearly leads. BackToMe starts at €25/month and RisingWave at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or RisingWave?
- RisingWave has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for RisingWave.
- Does BackToMe or RisingWave run on more platforms?
- BackToMe runs on Web. RisingWave runs on Linux, Self-hosted, Web.
- Can I use RisingWave for free?
- Yes. RisingWave 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 RisingWave is typically brought in for.
- What can BackToMe do that RisingWave cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. RisingWave covers SQL materialised views, Postgres wire compatibility, Object storage state, Source connectors.
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.
SourceRisingWave: Is RisingWave open source?
The community edition is Apache 2.0 and self-hostable, but a set of premium features requires a paid licence key.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceRisingWave: What does the cloud cost?
It starts at 0.227 US dollars per RisingWave Unit hour on the Basic tier, which is capped at 64 cores.
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.
SourceRisingWave: Does it replace Flink?
For SQL-expressible transformations, often yes. For custom stateful processing and complex event handling, no.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceRisingWave: Can I query it like Postgres?
Yes over the Postgres wire protocol, but it is an analytical streaming engine, not a transactional database.
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 Apache Flink
- BackToMe vs Materialize
- BackToMe vs Tinybird
- BackToMe vs Redpanda
- BackToMe vs Timeplus
- BackToMe vs Estuary
- BackToMe vs Instaclustr
- BackToMe vs Fivetran HVR
- BackToMe vs Trino
- BackToMe vs TiDB
- BackToMe vs Xata
- BackToMe vs ScyllaDB
- BackToMe vs Solace PubSub+
- BackToMe vs SQLite
- BackToMe vs StarRocks
- BackToMe vs SurrealDB
- BackToMe vs Teradata
- BackToMe vs Apache Kafka
- RisingWave vs Temu
- RisingWave vs Amazon Shopping
- RisingWave vs Mailchimp
- RisingWave vs Shein
- RisingWave vs CJ Dropshipping
- RisingWave vs Memberful
- RisingWave vs Wish
- RisingWave vs Zendrop
- RisingWave vs Heartland Retail
- RisingWave vs Vinted
- RisingWave vs Mollie
- RisingWave vs TikTok Shop
- RisingWave vs SamCart
- RisingWave vs Sellfy
- RisingWave vs Shopware
- RisingWave vs Spree Commerce
- RisingWave vs Swell Commerce
- RisingWave vs Toast
- RisingWave vs Apache Flink
- RisingWave vs Materialize
- RisingWave vs Tinybird
- RisingWave vs Redpanda
- RisingWave vs Timeplus
- RisingWave vs Estuary
- RisingWave vs Instaclustr
- RisingWave vs Fivetran HVR
- RisingWave vs Trino
- RisingWave vs TiDB
- RisingWave vs Xata
- RisingWave vs ScyllaDB
- RisingWave vs Solace PubSub+
- RisingWave vs SQLite
- RisingWave vs StarRocks
- RisingWave vs SurrealDB
- RisingWave vs Teradata
- RisingWave vs Apache Kafka
