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