Transparency alternatives to Modern Requirements
Other Quality management vendors we measure, sorted by how much we found at them and not at Modern Requirements. This is a comparison of disclosure, not of features or fitness.
12 shown of 83 that differ from Modern Requirements on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Modern Requirements has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, 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 Modern Requirements” is the one that closes them.
| Vendor | Score | Found there, not found at Modern Requirements | Found at Modern Requirements, not found there | |
|---|---|---|---|---|
| Qualioqualio.comSee also Transparency alternatives to Qualio | 57/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 1 Certifications named | Compare |
| SimplerQMSsimplerqms.comSee also Transparency alternatives to SimplerQMS | 48/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | 1 Certifications named | Compare |
| Ketryxketryx.comSee also Transparency alternatives to Ketryx | 43/100 | 5 Data processing agreement, Public pricing, Uptime SLA with a figure, +2 | nothing | Compare |
| AM System Classicamsystem.comSee also Transparency alternatives to AM System Classic | 39/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Cognidoxcognidox.comSee also Transparency alternatives to Cognidox | 39/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | nothing | Compare |
| myoshmyosh.comSee also Transparency alternatives to myosh | 39/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Grand Avenue Softwaregrandavenue.comSee also Transparency alternatives to Grand Avenue Software | 35/100 | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | 1 Certifications named | Compare |
| Propelpropelsoftware.comSee also Transparency alternatives to Propel | 35/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | nothing | Compare |
| TrackWisespartasystems.comSee also Transparency alternatives to TrackWise | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Certainty Softwarecertaintysoftware.comSee also Transparency alternatives to Certainty Software | 35/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | nothing | Compare |
| Arenaarenasolutions.comSee also Transparency alternatives to Arena | 26/100 | 3 Status page with history, Public pricing, Uptime SLA with a figure | nothing | Compare |
| Openbomopenbom.comSee also Transparency alternatives to Openbom | 26/100 | 3 Data location stated, Public pricing, 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.