Alternatives to Tractable
Other Insurance software vendors we measure, sorted by how much they publish that Tractable does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from Tractable on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Tractable has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, 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 “publishes and Tractable does not” is the one that closes them.
| Vendor | Score | Publishes, and Tractable does not | Tractable publishes, and they do not | |
|---|---|---|---|---|
| Ezlynxezlynx.com | 39/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Ivansivans.com | 39/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Zegurozeguro.com | 35/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Root Platformrootplatform.com | 26/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Sapienssapiens.com | 26/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Duck Creekduckcreek.com | 35/100 | 2 Subprocessor list, Certifications named | nothing | Compare |
| Guidewireguidewire.com | 35/100 | 2 Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| Clarkclark.de | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Eberleberls.com | 17/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Nowcertsnowcerts.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Ottonovaottonova.de | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Majescomajesco.com | 14/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Data location stated, 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.