Transparency alternatives to ACCELQ
Other Test automation vendors we measure, sorted by how much we found at them and not at ACCELQ. This is a comparison of disclosure, not of features or fitness.
12 shown of 43 that differ from ACCELQ on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ACCELQ has 7 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at ACCELQ” is the one that closes them.
| Vendor | Score | Found there, not found at ACCELQ | Found at ACCELQ, not found there | |
|---|---|---|---|---|
| Cypresscypress.ioSee also Transparency alternatives to Cypress | 65/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 2 Data processing agreement, Named privacy contact | Compare |
| Replicated Compatibility Matrixreplicated.comSee also Transparency alternatives to Replicated Compatibility Matrix | 52/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Endtestendtest.ioSee also Transparency alternatives to Endtest | 48/100 | 3 Subprocessor list, Data location stated, Public pricing | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Katalonkatalon.comSee also Transparency alternatives to Katalon | 48/100 | 3 Data location stated, Status page with history, Public pricing | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Applitoolsapplitools.comSee also Transparency alternatives to Applitools | 43/100 | 3 Status page with history, Public pricing, Uptime SLA with a figure | 2 HTTPS enforced with HSTS, Notice before subprocessors change | Compare |
| Kobitonkobiton.comSee also Transparency alternatives to Kobiton | 43/100 | 3 Subprocessor list, Status page with history, Public pricing | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| PractiTestpractitest.comSee also Transparency alternatives to PractiTest | 39/100 | 3 Subprocessor list, Public pricing, Uptime SLA with a figure | 3 Data processing agreement, HTTPS enforced with HSTS, Named privacy contact | Compare |
| RadViewradview.comSee also Transparency alternatives to RadView | 26/100 | 3 Data location stated, Public pricing, Uptime SLA with a figure | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | Compare |
| Global App Testingglobalapptesting.comSee also Transparency alternatives to Global App Testing | 39/100 | 2 Data location stated, Public pricing | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Rainforest QArainforestqa.comSee also Transparency alternatives to Rainforest QA | 39/100 | 2 Data location stated, Status page with history | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Functionizefunctionize.comSee also Transparency alternatives to Functionize | 35/100 | 2 Data location stated, Public pricing | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Allure TestOpsqameta.ioSee also Transparency alternatives to Allure TestOps | 30/100 | 2 Public pricing, security.txt (RFC 9116) | 2 Data processing agreement, Notice before subprocessors change | 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.