Transparency alternatives to Cogniss
Other Low-code and internal tools vendors we measure, sorted by how much we found at them and not at Cogniss. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Cogniss on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cogniss has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Cogniss” is the one that closes them.
| Vendor | Score | Found there, not found at Cogniss | Found at Cogniss, not found there | |
|---|---|---|---|---|
| Retoolretool.comSee also Transparency alternatives to Retool | 61/100 | 6 Subprocessor list, Status page with history, Public pricing, +3 | 2 Data location stated, Uptime SLA with a figure | Compare |
| Forest Adminforestadmin.comSee also Transparency alternatives to Forest Admin | 70/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | 1 Uptime SLA with a figure | Compare |
| Caspiocaspio.comSee also Transparency alternatives to Caspio | 57/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | 3 Uptime SLA with a figure, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Teableteable.ioSee also Transparency alternatives to Teable | 57/100 | 4 Data processing agreement, Public pricing, security.txt (RFC 9116), +1 | 2 Uptime SLA with a figure, Named privacy contact | Compare |
| Mendixmendix.comSee also Transparency alternatives to Mendix | 52/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 1 Uptime SLA with a figure | Compare |
| Jet Adminjetadmin.ioSee also Transparency alternatives to Jet Admin | 48/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 3 Data location stated, Uptime SLA with a figure, Named privacy contact | Compare |
| Pegapega.comSee also Transparency alternatives to Pega | 52/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 1 Uptime SLA with a figure | Compare |
| Superblockssuperblocks.comSee also Transparency alternatives to Superblocks | 52/100 | 3 Subprocessor list, Public pricing, Certifications named | 1 Uptime SLA with a figure | Compare |
| Budibasebudibase.comSee also Transparency alternatives to Budibase | 48/100 | 3 Status page with history, Public pricing, Certifications named | 1 Uptime SLA with a figure | Compare |
| DronaHQdronahq.comSee also Transparency alternatives to DronaHQ | 35/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 3 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| RUAL Corerual.nlSee also Transparency alternatives to RUAL Core | 35/100 | 3 Public pricing, No third-party tracking before consent, security.txt (RFC 9116) | 2 Data location stated, Uptime SLA with a figure | Compare |
| Xanoxano.comSee also Transparency alternatives to Xano | 35/100 | 3 Public pricing, Certifications named, No third-party tracking before consent | 2 Data location stated, Uptime SLA with a figure | 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.