Transparency alternatives to Dexco
Other Legal practice management vendors we measure, sorted by how much they publish that Dexco does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 44 that differ from Dexco on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Dexco has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Dexco does not” is the one that closes them.
| Vendor | Score | Publishes, and Dexco does not | Dexco publishes, and they do not | |
|---|---|---|---|---|
| Cerenadecerenade.com | 48/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 1 Public pricing | Compare |
| Amberloamberlo.io | 43/100 | 4 Data processing agreement, Data location stated, Certifications named, +1 | 1 HTTPS enforced with HSTS | Compare |
| Litifylitify.com | 35/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 1 Public pricing | Compare |
| Smokeballsmokeball.com | 35/100 | 3 Data location stated, Status page with history, Certifications named | 1 Public pricing | Compare |
| Eliteelite.com | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 Public pricing | Compare |
| Filevinefilevine.com | 30/100 | 3 Subprocessor list, Data location stated, Certifications named | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Aderantaderant.com | 17/100 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Assembly Neosassemblysoftware.com | 35/100 | 2 Data location stated, Named privacy contact | nothing | Compare |
| Matters.Cloudmatters.cloud | 35/100 | 2 Subprocessor list, Data location stated | 1 HTTPS enforced with HSTS | Compare |
| Luminanceluminance.com | 30/100 | 2 Data location stated, Certifications named | 1 Public pricing | Compare |
| MyCasemycase.com | 30/100 | 2 Status page with history, Named privacy contact | nothing | Compare |
| Legitolegito.com | 29/100 | 2 Data location stated, Certifications named | 1 HTTPS enforced with HSTS | 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.