Alternatives to Kontent.ai
Other Content management systems vendors we measure, sorted by how much they publish that Kontent.ai does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 23 that differ from Kontent.ai on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kontent.ai has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Kontent.ai does not” is the one that closes them.
| Vendor | Score | Publishes, and Kontent.ai does not | Kontent.ai publishes, and they do not | |
|---|---|---|---|---|
| Uniformuniform.dev | 57/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Directusdirectus.io | 52/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Pantheonpantheon.io | 52/100 | 4 Subprocessor list, Data location stated, Certifications named, +1 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Contentstackcontentstack.com | 48/100 | 4 Subprocessor list, Data location stated, Certifications named, +1 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Craft CMScraftcms.com | 48/100 | 3 Subprocessor list, Data location stated, Public pricing | 2 Status page with history, Named privacy contact | Compare |
| Hygraphhygraph.com | 35/100 | 2 Data location stated, Public pricing | 2 Status page with history, security.txt (RFC 9116) | Compare |
| ButterCMSbuttercms.com | 30/100 | 2 Public pricing, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Progress Sitefinityprogress.com | 30/100 | 2 Data location stated, Certifications named | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Cockpitgetcockpit.com | 22/100 | 2 Data location stated, No third-party tracking before consent | 4 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Ibexaibexa.co | 30/100 | 1 Data location stated | 1 Status page with history | Compare |
| Joomlajoomla.org | 30/100 | 1 Data location stated | 1 Status page with history | Compare |
| CoreMediacoremedia.com | 26/100 | 1 Data location stated | 2 Status page with history, 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.