Transparency alternatives to EIS Group
Other Insurance software vendors we measure, sorted by how much we found at them and not at EIS Group. This is a comparison of disclosure, not of features or fitness.
12 shown of 58 that differ from EIS Group on at least one criterion we measured for both. Public transparency score, not a product or security rating.
EIS Group 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 “Found there, not found at EIS Group” is the one that closes them.
| Vendor | Score | Found there, not found at EIS Group | Found at EIS Group, not found there | |
|---|---|---|---|---|
| Zegurozeguro.comSee also Transparency alternatives to Zeguro | 35/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Ezlynxezlynx.comSee also Transparency alternatives to Ezlynx | 26/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Ivansivans.comSee also Transparency alternatives to Ivans | 26/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Root Platformrootplatform.comSee also Transparency alternatives to Root Platform | 26/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Sapienssapiens.comSee also Transparency alternatives to Sapiens | 26/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Duck Creekduckcreek.comSee also Transparency alternatives to Duck Creek | 35/100 | 2 Subprocessor list, Certifications named | nothing | Compare |
| Guidewireguidewire.comSee also Transparency alternatives to Guidewire | 35/100 | 2 Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| Clarkclark.deSee also Transparency alternatives to Clark | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Eberleberls.comSee also Transparency alternatives to Eberl | 17/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Majescomajesco.comSee also Transparency alternatives to Majesco | 17/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Nowcertsnowcerts.comSee also Transparency alternatives to Nowcerts | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Ottonovaottonova.deSee also Transparency alternatives to Ottonova | 17/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | 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.