Transparency alternatives to Kenesto
Other Document management vendors we measure, sorted by how much we found at them and not at Kenesto. This is a comparison of disclosure, not of features or fitness.
12 shown of 65 that differ from Kenesto on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kenesto has 9 gaps in what we could measure: Data processing agreement, 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. The column “Found there, not found at Kenesto” is the one that closes them.
| Vendor | Score | Found there, not found at Kenesto | Found at Kenesto, not found there | |
|---|---|---|---|---|
| Templafytemplafy.comSee also Transparency alternatives to Templafy | 74/100 | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | 1 Named privacy contact | Compare |
| CloudFilescloudfiles.ioSee also Transparency alternatives to CloudFiles | 70/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | 1 Public pricing | Compare |
| Intralinksintralinks.comSee also Transparency alternatives to Intralinks | 70/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 Public pricing | Compare |
| Smallpdfsmallpdf.comSee also Transparency alternatives to Smallpdf | 57/100 | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| Laserfichelaserfiche.comSee also Transparency alternatives to Laserfiche | 52/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Onehubonehub.comSee also Transparency alternatives to Onehub | 52/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Ademeroademero.comSee also Transparency alternatives to Ademero | 43/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data location stated, Named privacy contact | Compare |
| DynaFiledynafile.comSee also Transparency alternatives to DynaFile | 43/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 2 Public pricing, Named privacy contact | Compare |
| Papermarkpapermark.comSee also Transparency alternatives to Papermark | 43/100 | 3 Certifications named, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Named privacy contact | Compare |
| Fabasoftfabasoft.comSee also Transparency alternatives to Fabasoft | 35/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Public pricing | Compare |
| The Drive AIthedrive.aiSee also Transparency alternatives to The Drive AI | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Thereforetherefore.netSee also Transparency alternatives to Therefore | 22/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | 3 Data location stated, Public pricing, 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.