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