Transparency alternatives to Statamic
Other Content management systems vendors we measure, sorted by how much we found at them and not at Statamic. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Statamic on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Statamic has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Statamic” is the one that closes them.
| Vendor | Score | Found there, not found at Statamic | Found at Statamic, not found there | |
|---|---|---|---|---|
| Sanitysanity.ioSee also Transparency alternatives to Sanity | 78/100 | 8 Data processing agreement, Data location stated, Status page with history, +5 | nothing | Compare |
| Storyblokstoryblok.comSee also Transparency alternatives to Storyblok | 74/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 security.txt (RFC 9116) | Compare |
| Pantheonpantheon.ioSee also Transparency alternatives to Pantheon | 52/100 | 6 Subprocessor list, Data location stated, Status page with history, +3 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Contentstackcontentstack.comSee also Transparency alternatives to Contentstack | 57/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| Directusdirectus.ioSee also Transparency alternatives to Directus | 52/100 | 5 Data processing agreement, Status page with history, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Shorthandshorthand.comSee also Transparency alternatives to Shorthand | 39/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Uniformuniform.devSee also Transparency alternatives to Uniform | 43/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| Strapistrapi.ioSee also Transparency alternatives to Strapi | 39/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 security.txt (RFC 9116) | Compare |
| Progress Sitefinityprogress.comSee also Transparency alternatives to Progress Sitefinity | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Craft CMScraftcms.comSee also Transparency alternatives to Craft CMS | 48/100 | 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS | nothing | Compare |
| Hygraphhygraph.comSee also Transparency alternatives to Hygraph | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Prismicprismic.ioSee also Transparency alternatives to Prismic | 35/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | 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.