Alternatives to Volusion
Other Ecommerce platforms vendors we measure, sorted by how much they publish that Volusion does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from Volusion on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Volusion has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “publishes and Volusion does not” is the one that closes them.
| Vendor | Score | Publishes, and Volusion does not | Volusion publishes, and they do not | |
|---|---|---|---|---|
| Shopifyshopify.com | 80/100 | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | 1 Uptime SLA with a figure | Compare |
| Lightspeedlightspeedhq.com | 70/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 2 Data location stated, Uptime SLA with a figure | Compare |
| Saleorsaleor.io | 74/100 | 3 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| commercetoolscommercetools.com | 43/100 | 3 Data processing agreement, Subprocessor list, Certifications named | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Ecwidecwid.com | 50/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Uptime SLA with a figure | Compare |
| Gumroadgumroad.com | 50/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 2 Status page with history, Uptime SLA with a figure | Compare |
| Shopwareshopware.com | 40/100 | 2 Data processing agreement, security.txt (RFC 9116) | 2 Data location stated, Uptime SLA with a figure | Compare |
| BigCommercebigcommerce.com | 35/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Data location stated, Uptime SLA with a figure | Compare |
| Shoplazzashoplazza.com | 33/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Status page with history, Public pricing, Uptime SLA with a figure | Compare |
| OXID eSalesoxid-esales.com | 30/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Status page with history | Compare |
| Sana Commercesana-commerce.com | 25/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| VTEXvtex.com | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data location stated, Status page with history, Public pricing, +1 | 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.