Transparency alternatives to RadView
Other Test automation vendors we measure, sorted by how much they publish that RadView does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from RadView on at least one criterion we measured for both. Public transparency score, not a product or security rating.
RadView has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and RadView does not” is the one that closes them.
| Vendor | Score | Publishes, and RadView does not | RadView publishes, and they do not | |
|---|---|---|---|---|
| Testsigmatestsigma.com | 48/100 | 6 Data processing agreement, Status page with history, Certifications named, +3 | 3 Data location stated, Public pricing, Uptime SLA with a figure | Compare |
| Cypresscypress.io | 65/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 1 Uptime SLA with a figure | Compare |
| Replicated Compatibility Matrixreplicated.com | 52/100 | 5 Status page with history, Certifications named, HTTPS enforced with HSTS, +2 | 1 Uptime SLA with a figure | Compare |
| ACCELQaccelq.com | 39/100 | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | 3 Data location stated, Public pricing, Uptime SLA with a figure | Compare |
| Katalonkatalon.com | 48/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 Uptime SLA with a figure | Compare |
| Allure TestOpsqameta.io | 43/100 | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Uptime SLA with a figure | Compare |
| Applitoolsapplitools.com | 43/100 | 4 Data processing agreement, Status page with history, Certifications named, +1 | 1 Data location stated | Compare |
| Rainforest QArainforestqa.com | 39/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 2 Public pricing, Uptime SLA with a figure | Compare |
| Horizonthetestmart.com | 35/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Data location stated, Public pricing, Uptime SLA with a figure | Compare |
| Applauseapplause.com | 26/100 | 4 Certifications named, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 3 Data location stated, Public pricing, Uptime SLA with a figure | Compare |
| testRigortestrigor.com | 26/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 3 Data location stated, Public pricing, Uptime SLA with a figure | Compare |
| Endtestendtest.io | 48/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 1 Uptime SLA with a figure | 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.