Transparency alternatives to SoftComply
Other Quality management vendors we measure, sorted by how much we found at them and not at SoftComply. This is a comparison of disclosure, not of features or fitness.
12 shown of 85 that differ from SoftComply on at least one criterion we measured for both. Public transparency score, not a product or security rating.
SoftComply has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at SoftComply” is the one that closes them.
| Vendor | Score | Found there, not found at SoftComply | Found at SoftComply, not found there | |
|---|---|---|---|---|
| Qualioqualio.comSee also Transparency alternatives to Qualio | 57/100 | 4 Data processing agreement, Data location stated, Status page with history, +1 | 2 Public pricing, Certifications named | Compare |
| SimplerQMSsimplerqms.comSee also Transparency alternatives to SimplerQMS | 48/100 | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | 3 Public pricing, Certifications named, Notice before subprocessors change | Compare |
| Ketryxketryx.comSee also Transparency alternatives to Ketryx | 43/100 | 3 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| AM System Classicamsystem.comSee also Transparency alternatives to AM System Classic | 39/100 | 3 Data processing agreement, Status page with history, HTTPS enforced with HSTS | 3 Public pricing, Certifications named, Named privacy contact | Compare |
| TrackWisespartasystems.comSee also Transparency alternatives to TrackWise | 35/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 3 Public pricing, Certifications named, Notice before subprocessors change | Compare |
| Cognidoxcognidox.comSee also Transparency alternatives to Cognidox | 39/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| myoshmyosh.comSee also Transparency alternatives to myosh | 39/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Certainty Softwarecertaintysoftware.comSee also Transparency alternatives to Certainty Software | 35/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Notice before subprocessors change, Named privacy contact | Compare |
| Propelpropelsoftware.comSee also Transparency alternatives to Propel | 35/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Arenaarenasolutions.comSee also Transparency alternatives to Arena | 26/100 | 2 Status page with history, Uptime SLA with a figure | 2 Notice before subprocessors change, Named privacy contact | Compare |
| Orcanosorcanos.comSee also Transparency alternatives to Orcanos | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Public pricing, Certifications named, Notice before subprocessors change | Compare |
| EoSceneeoscene.comSee also Transparency alternatives to EoScene | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 4 Public pricing, Certifications named, Notice before subprocessors change, +1 | 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.