Transparency alternatives to Medusa
Other Ecommerce platforms vendors we measure, sorted by how much we found at them and not at Medusa. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Medusa on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Medusa has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Medusa” is the one that closes them.
| Vendor | Score | Found there, not found at Medusa | Found at Medusa, not found there | |
|---|---|---|---|---|
| Saleorsaleor.ioSee also Transparency alternatives to Saleor | 74/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 Status page with history | Compare |
| Shopifyshopify.comSee also Transparency alternatives to Shopify | 70/100 | 6 Data processing agreement, Certifications named, No third-party tracking before consent, +3 | nothing | Compare |
| Lightspeedlightspeedhq.comSee also Transparency alternatives to Lightspeed | 70/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | nothing | Compare |
| commercetoolscommercetools.comSee also Transparency alternatives to commercetools | 52/100 | 5 Data processing agreement, Subprocessor list, Certifications named, +2 | 2 Status page with history, Public pricing | Compare |
| Gumroadgumroad.comSee also Transparency alternatives to Gumroad | 52/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 1 Status page with history | Compare |
| Swellswell.isSee also Transparency alternatives to Swell | 52/100 | 2 Data processing agreement, Notice before subprocessors change | nothing | Compare |
| Ecwidecwid.comSee also Transparency alternatives to Ecwid | 36/100 | 2 Certifications named, Named privacy contact | nothing | Compare |
| BigCommercebigcommerce.comSee also Transparency alternatives to BigCommerce | 35/100 | 2 Certifications named, Named privacy contact | nothing | Compare |
| Shoplazzashoplazza.comSee also Transparency alternatives to Shoplazza | 35/100 | 2 Data location stated, Certifications named | 1 Status page with history | Compare |
| Vendurevendure.ioSee also Transparency alternatives to Vendure | 35/100 | 2 Data location stated, Named privacy contact | 1 Status page with history | Compare |
| Volusionvolusion.comSee also Transparency alternatives to Volusion | 35/100 | 2 Data location stated, Uptime SLA with a figure | 1 HTTPS enforced with HSTS | Compare |
| OXID eSalesoxid-esales.comSee also Transparency alternatives to OXID eSales | 26/100 | 2 security.txt (RFC 9116), Named privacy contact | 1 Status page with history | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.