Alternatives to Toloka
Other Data labelling vendors we measure, sorted by how much they publish that Toloka does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from Toloka on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Toloka has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Toloka does not” is the one that closes them.
| Vendor | Score | Publishes, and Toloka does not | Toloka publishes, and they do not | |
|---|---|---|---|---|
| Scale AIscale.com | 65/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | nothing | Compare |
| SuperAnnotatesuperannotate.com | 57/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Datasaurdatasaur.ai | 43/100 | 3 Data location stated, Status page with history, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Hivethehive.ai | 43/100 | 3 Data location stated, Status page with history, Public pricing | 2 Certifications named, security.txt (RFC 9116) | Compare |
| HumanSignalhumansignal.com | 43/100 | 3 Data processing agreement, Status page with history, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| CVATcvat.ai | 39/100 | 3 Data location stated, Status page with history, Public pricing | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Dataloopdataloop.ai | 39/100 | 2 Data location stated, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Kognickognic.com | 35/100 | 2 Data location stated, Status page with history | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Roboflowroboflow.com | 30/100 | 2 Status page with history, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Kilikili-technology.com | 26/100 | 2 Status page with history, Public pricing | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Segments.aisegments.ai | 22/100 | 2 Data location stated, Public pricing | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| V7v7labs.com | 35/100 | 1 Data location stated | nothing | 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.