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