Transparency alternatives to Coface
Other Supply chain risk vendors we measure, sorted by how much we found at them and not at Coface. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from Coface on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Coface has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent. The column “Found there, not found at Coface” is the one that closes them.
| Vendor | Score | Found there, not found at Coface | Found at Coface, not found there | |
|---|---|---|---|---|
| Resilincresilinc.comSee also Transparency alternatives to Resilinc | 74/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 security.txt (RFC 9116) | Compare |
| Assentassent.comSee also Transparency alternatives to Assent | 52/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 1 security.txt (RFC 9116) | Compare |
| Versoverso.deSee also Transparency alternatives to Verso | 50/100 | 3 Data location stated, Status page with history, No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| Avettaavetta.comSee also Transparency alternatives to Avetta | 35/100 | 3 Status page with history, Public pricing, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Circulorcirculor.comSee also Transparency alternatives to Circulor | 39/100 | 2 Data processing agreement, Data location stated | 1 security.txt (RFC 9116) | Compare |
| LexisNexis Riskrisk.lexisnexis.comSee also Transparency alternatives to LexisNexis Risk | 39/100 | 2 Subprocessor list, Data location stated | 1 security.txt (RFC 9116) | Compare |
| TrusTracetrustrace.comSee also Transparency alternatives to TrusTrace | 35/100 | 2 Data location stated, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Sayarisayari.comSee also Transparency alternatives to Sayari | 30/100 | 2 Subprocessor list, Certifications named | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| ISNisnetworld.comSee also Transparency alternatives to ISN | 26/100 | 2 Data location stated, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Dun & Bradstreetdnb.comSee also Transparency alternatives to Dun & Bradstreet | 22/100 | 2 Status page with history, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Everstreameverstream.aiSee also Transparency alternatives to Everstream | 26/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Exigerexiger.comSee also Transparency alternatives to Exiger | 26/100 | 1 Data location stated | 1 security.txt (RFC 9116) | 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.