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