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