Transparency alternatives to Duck Creek
Other Insurance software vendors we measure, sorted by how much we found at them and not at Duck Creek. This is a comparison of disclosure, not of features or fitness.
12 shown of 59 that differ from Duck Creek on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Duck Creek has 8 gaps in what we could measure: Data processing agreement, Status page with history, Public pricing, 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 Duck Creek” is the one that closes them.
| Vendor | Score | Found there, not found at Duck Creek | Found at Duck Creek, not found there | |
|---|---|---|---|---|
| Guidewireguidewire.comSee also Transparency alternatives to Guidewire | 35/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Subprocessor list, Certifications named | Compare |
| Zegurozeguro.comSee also Transparency alternatives to Zeguro | 35/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Subprocessor list, Named privacy contact | Compare |
| Ezlynxezlynx.comSee also Transparency alternatives to Ezlynx | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Subprocessor list, Data location stated | Compare |
| Ivansivans.comSee also Transparency alternatives to Ivans | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Subprocessor list, Data location stated | Compare |
| Root Platformrootplatform.comSee also Transparency alternatives to Root Platform | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Subprocessor list, Data location stated | Compare |
| Sapienssapiens.comSee also Transparency alternatives to Sapiens | 26/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Subprocessor list, Data location stated | Compare |
| Clarkclark.deSee also Transparency alternatives to Clark | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Subprocessor list, Data location stated, Certifications named | Compare |
| Nowcertsnowcerts.comSee also Transparency alternatives to Nowcerts | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 4 Subprocessor list, Data location stated, Certifications named, +1 | Compare |
| Ottonovaottonova.deSee also Transparency alternatives to Ottonova | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Subprocessor list, Data location stated, Certifications named | Compare |
| Quest Analyticsquestanalytics.comSee also Transparency alternatives to Quest Analytics | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Subprocessor list, Data location stated, Certifications named | Compare |
| Crawfordcrawco.comSee also Transparency alternatives to Crawford | 26/100 | 1 HTTPS enforced with HSTS | 2 Subprocessor list, Certifications named | Compare |
| Five Sigmafivesigmalabs.comSee also Transparency alternatives to Five Sigma | 26/100 | 1 HTTPS enforced with HSTS | 2 Subprocessor list, Certifications named | 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.