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