Alternatives to DocuWare
Other Document management vendors we measure, sorted by how much they publish that DocuWare does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from DocuWare on at least one criterion we measured for both. Public transparency score, not a product or security rating.
DocuWare has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and DocuWare does not” is the one that closes them.
| Vendor | Score | Publishes, and DocuWare does not | DocuWare publishes, and they do not | |
|---|---|---|---|---|
| Templafytemplafy.com | 74/100 | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Laserfichelaserfiche.com | 52/100 | 5 Data location stated, Status page with history, Public pricing, +2 | nothing | Compare |
| Ademeroademero.com | 48/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 1 security.txt (RFC 9116) | Compare |
| DynaFiledynafile.com | 43/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
| windreamwindream.com | 26/100 | 2 Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| OpenTextopentext.com | 20/100 | 1 Status page with history | nothing | Compare |
| Dokmeedokmee.com | 17/100 | 1 Public pricing | 1 security.txt (RFC 9116) | Compare |
| M-Filesm-files.com | 17/100 | 1 Public pricing | 1 security.txt (RFC 9116) | Compare |
| Thereforetherefore.net | 17/100 | 1 No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| d.velopd-velop.de | 13/100 | 1 Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| FileHoldfilehold.com | 13/100 | 1 Data location stated | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| iManageimanage.com | 13/100 | 1 Named privacy contact | 1 security.txt (RFC 9116) | 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.