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