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