Transparency alternatives to Kohezion
Other Low-code and internal tools vendors we measure, sorted by how much they publish that Kohezion does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Kohezion on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kohezion has 9 gaps in what we could measure: Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Kohezion does not” is the one that closes them.
| Vendor | Score | Publishes, and Kohezion does not | Kohezion publishes, and they do not | |
|---|---|---|---|---|
| Retoolretool.com | 61/100 | 7 Subprocessor list, Status page with history, Certifications named, +4 | 2 Data processing agreement, Data location stated | Compare |
| Forest Adminforestadmin.com | 52/100 | 5 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +2 | 2 Data processing agreement, Data location stated | Compare |
| Mendixmendix.com | 52/100 | 5 Status page with history, Certifications named, HTTPS enforced with HSTS, +2 | 1 Data processing agreement | Compare |
| Pegapega.com | 52/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | 2 Data processing agreement, Public pricing | Compare |
| Superblockssuperblocks.com | 52/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data processing agreement | Compare |
| Betty Blocksbettyblocks.com | 48/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data processing agreement | Compare |
| Budibasebudibase.com | 48/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data processing agreement | Compare |
| OutSystemsoutsystems.com | 24/100 | 4 Status page with history, Certifications named, security.txt (RFC 9116), +1 | 2 Data processing agreement, Data location stated | Compare |
| Caspiocaspio.com | 57/100 | 3 Certifications named, No third-party tracking before consent, Notice before subprocessors change | nothing | Compare |
| UI Bakeryuibakery.io | 43/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 1 Data processing agreement | Compare |
| Agilebaseagilebase.co.uk | 39/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 1 Data processing agreement | Compare |
| RUAL Corerual.nl | 32/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, Named privacy contact | 2 Data processing agreement, Data location stated | 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.