SaaS Ranking

Alternatives to Applitools

Other Test automation vendors we measure, sorted by how much they publish that Applitools does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 26 that differ from Applitools on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Applitools has 6 gaps in what we could measure: Subprocessor list, Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Applitools does not” is the one that closes them.

VendorScorePublishes, and Applitools does notApplitools publishes, and they do not
Cypresscypress.io 65/100 4 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +1 3 Data processing agreement, Uptime SLA with a figure, Named privacy contact Compare
BrowserStackbrowserstack.com 63/100 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent 2 Data processing agreement, Uptime SLA with a figure Compare
Endtestendtest.io 48/100 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS 4 Data processing agreement, Status page with history, Uptime SLA with a figure, +1 Compare
Applauseapplause.com 39/100 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent 4 Data processing agreement, Status page with history, Public pricing, +1 Compare
Xraygetxray.app 39/100 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS 5 Data processing agreement, Status page with history, Public pricing, +2 Compare
Katalonkatalon.com 48/100 2 Data location stated, HTTPS enforced with HSTS 2 Data processing agreement, Uptime SLA with a figure Compare
PractiTestpractitest.com 48/100 2 Subprocessor list, Notice before subprocessors change 2 Data processing agreement, Named privacy contact Compare
ACCELQaccelq.com 39/100 2 HTTPS enforced with HSTS, Notice before subprocessors change 3 Status page with history, Public pricing, Uptime SLA with a figure Compare
Global App Testingglobalapptesting.com 39/100 2 Data location stated, HTTPS enforced with HSTS 3 Data processing agreement, Status page with history, Uptime SLA with a figure Compare
Rainforest QArainforestqa.com 39/100 2 Data location stated, HTTPS enforced with HSTS 3 Data processing agreement, Public pricing, Uptime SLA with a figure Compare
Kobitonkobiton.com 35/100 2 Subprocessor list, HTTPS enforced with HSTS 4 Data processing agreement, Status page with history, Uptime SLA with a figure, +1 Compare
QA Wolfqawolf.com 35/100 2 Data location stated, HTTPS enforced with HSTS 4 Data processing agreement, Status page with history, Uptime SLA with a figure, +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.