SaaS Ranking

Transparency alternatives to WLT Software

Other Insurance software vendors we measure, sorted by how much we found at them and not at WLT Software. This is a comparison of disclosure, not of features or fitness.

12 shown of 58 that differ from WLT Software on at least one criterion we measured for both. Public transparency score, not a product or security rating.

WLT Software has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, 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, Named privacy contact. The column “Found there, not found at WLT Software” is the one that closes them.

VendorScoreFound there, not found at WLT SoftwareFound at WLT Software, not found there
Guidewireguidewire.comSee also Transparency alternatives to Guidewire 39/100 4 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 1 Certifications named Compare
Ezlynxezlynx.comSee also Transparency alternatives to Ezlynx 26/100 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact 1 Data location stated Compare
Ivansivans.comSee also Transparency alternatives to Ivans 26/100 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact 1 Data location stated Compare
Root Platformrootplatform.comSee also Transparency alternatives to Root Platform 26/100 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact 1 Data location stated Compare
Sapienssapiens.comSee also Transparency alternatives to Sapiens 26/100 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact 1 Data location stated Compare
Clarkclark.deSee also Transparency alternatives to Clark 17/100 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact 2 Data location stated, Certifications named Compare
Ottonovaottonova.deSee also Transparency alternatives to Ottonova 17/100 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact 2 Data location stated, Certifications named Compare
Duck Creekduckcreek.comSee also Transparency alternatives to Duck Creek 35/100 2 Subprocessor list, Named privacy contact nothing Compare
Zegurozeguro.comSee also Transparency alternatives to Zeguro 35/100 2 Public pricing, HTTPS enforced with HSTS nothing Compare
Clearspeedclearspeed.comSee also Transparency alternatives to Clearspeed 26/100 2 HTTPS enforced with HSTS, Named privacy contact 1 Certifications named Compare
Crawfordcrawco.comSee also Transparency alternatives to Crawford 26/100 2 HTTPS enforced with HSTS, Named privacy contact 1 Certifications named Compare
Snapsheetsnapsheetclaims.comSee also Transparency alternatives to Snapsheet 26/100 2 Status page with history, Named privacy contact 1 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.