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