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