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