E-Commerce · head to head
BackToMe vs Xata

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

Xata
Databases
Apache 2.0 platform for running many Postgres instances on Kubernetes, with copy-on-write branching and scale-to-zero.
- From
- Free
- Free plan
- Yes
The short version
- Xata has a free plan, then $1/mo; BackToMe starts at €25/mo.
- Only BackToMe lists floating withdrawal button; only Xata lists copy-on-write branching.
- 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 Xata 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 Xata
- Copy-on-write branching
- Scale-to-zero compute
- Compute autoscaling and bin-packing
- High availability with failover
- Point-in-time recovery
- Serverless driver
- pgroll migrations
- pgstream replication
What people use each for
The jobs each tool is most often brought in to do.
BackToMe
- Meeting EU Directive 2023/2673 withdrawal obligationsnot Xata
- Producing dated proof of a cancellation in a customer disputenot Xata
- Handling withdrawal requests across several EU languagesnot Xata
- Running one withdrawal process across multiple storefrontsnot Xata
- Passing a consumer-protection audit with exportable recordsnot Xata
Xata
- Giving every pull request or coding agent its own branch of the production database, with real data volumes rather than a seeded fixturenot BackToMe
- Running managed-Postgres economics in your own cloud account where data residency or compliance rules out a third-party control planenot BackToMe
- Consolidating many small, mostly idle Postgres databases onto shared infrastructure where scale-to-zero and bin-packing recover the idle costnot BackToMe
- Testing a destructive migration against a copy of production without waiting for a full restore or paying for a duplicate of the storagenot 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
Xata
- Self-hosting means operating Kubernetes and CloudNativePG, so the Apache 2.0 licence removes the vendor bill but replaces it with a platform team, and a database platform is not something a part-time operator maintains safely
- Copy-on-write branches are cheap to create but diverge as they are written to, so a long-lived branch carrying a heavy backfill quietly accumulates real storage and the cost arrives later than the decision that caused it
- Scale-to-zero means the first connection after an idle period pays a cold start, which is invisible in a busy production database and very visible in a demo, a staging environment or a cron job that runs once an hour
- The Xata sold before 2025 was a different product, a proprietary API and SDK layered over Postgres, so tutorials, blog posts and SDK examples from that era describe something that no longer exists and existing users had to migrate
- As a managed service it competes with RDS, Aurora and Cloud SQL, and it is a much smaller company, so procurement, certification coverage and the depth of the support bench behind a 3am corruption incident are all weaker than the incumbent even though the underlying Postgres is the same
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
Xata
Free- Free TrialFree
- 14 days free
- No credit card required
- Usage-Based$1
- 1,000 branches for $1
- Scale-to-zero compute model
- Branches hibernate when idle
Which should you pick?
Choose BackToMe if
- You need floating withdrawal button.
- You also want automatic acknowledgement.
Choose Xata if
- You need copy-on-write branching.
- You want to start without paying.
- You also want scale-to-zero compute.
Questions people ask
- Is BackToMe or Xata better?
- Neither clearly leads. BackToMe starts at €25/month and Xata at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, BackToMe or Xata?
- Xata has a free tier; the other does not. Paid plans start at €25/month for BackToMe and Free for Xata.
- Does BackToMe or Xata run on more platforms?
- Both run on Web, so platform support will not decide this one for you.
- Can I use Xata for free?
- Yes. Xata 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 Xata is typically brought in for.
- What can BackToMe do that Xata cannot?
- BackToMe covers Floating withdrawal button, Automatic acknowledgement, Sealed archiving, Withdrawal dashboard. Xata covers Copy-on-write branching, Scale-to-zero compute, Compute autoscaling and bin-packing, High availability with failover.
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.
SourceXata: Is it real Postgres or a compatible reimplementation?
Real Postgres. It runs upstream Postgres instances on Kubernetes via CloudNativePG, so extensions, the wire protocol and version upgrades behave as they do anywhere else.
BackToMe: Which regulation does it address?
EU Directive 2023/2673, which governs the consumer right of withdrawal on distance contracts in e-commerce.
SourceXata: Can I self-host the whole thing?
Yes. The platform is Apache 2.0 and designed for self-hosting a large number of Postgres instances on your own Kubernetes. Xata Cloud is the same platform run as a service.
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.
SourceXata: Does branching copy my data?
No. Branches are copy-on-write at the storage layer, so creating one is near-instant regardless of database size and storage is only consumed as the branch diverges from its parent.
BackToMe: Are staging and development stores billed?
No. Only activated stores are billed, and the withdrawal button does not display on inactive ones.
SourceXata: Is this the same Xata I used a couple of years ago?
No. The earlier product was a proprietary database API with its own SDK and search layer. The current product is a Postgres platform, and material written for the old one does not apply.
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.
SourceXata: What happens to a branch when the parent changes?
A branch is a point-in-time fork. Later changes on the parent are not propagated, so long-lived branches drift and need to be recreated rather than refreshed if you want current data.
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 Amazon Aurora
- BackToMe vs PostgreSQL
- BackToMe vs DuckDB
- BackToMe vs Trino
- BackToMe vs Convex
- BackToMe vs turbopuffer
- BackToMe vs PlanetScale
- BackToMe vs Apache Druid
- BackToMe vs Materialize
- BackToMe vs BigQuery
- BackToMe vs etcd
- BackToMe vs Fivetran HVR
- BackToMe vs Grist
- BackToMe vs IBM Db2
- BackToMe vs Instaclustr
- BackToMe vs Knack
- BackToMe vs DynamoDB
- BackToMe vs Apache Pulsar
- Xata vs Temu
- Xata vs Amazon Shopping
- Xata vs Mailchimp
- Xata vs Shein
- Xata vs CJ Dropshipping
- Xata vs Memberful
- Xata vs Wish
- Xata vs Zendrop
- Xata vs Heartland Retail
- Xata vs Vinted
- Xata vs Mollie
- Xata vs TikTok Shop
- Xata vs SamCart
- Xata vs Sellfy
- Xata vs Shopware
- Xata vs Spree Commerce
- Xata vs Swell Commerce
- Xata vs Toast
- Xata vs Amazon Aurora
- Xata vs PostgreSQL
- Xata vs DuckDB
- Xata vs Trino
- Xata vs Convex
- Xata vs turbopuffer
- Xata vs PlanetScale
- Xata vs Apache Druid
- Xata vs Materialize
- Xata vs BigQuery
- Xata vs etcd
- Xata vs Fivetran HVR
- Xata vs Grist
- Xata vs IBM Db2
- Xata vs Instaclustr
- Xata vs Knack
- Xata vs DynamoDB
- Xata vs Apache Pulsar
