Alternatives to Crowdin
Other Translation and localization vendors we measure, sorted by how much they publish that Crowdin does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 18 that differ from Crowdin on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Crowdin has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Crowdin does not” is the one that closes them.
| Vendor | Score | Publishes, and Crowdin does not | Crowdin publishes, and they do not | |
|---|---|---|---|---|
| Lokaliselokalise.com | 87/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 Certifications named | Compare |
| Transifextransifex.com | 83/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 security.txt (RFC 9116) | Compare |
| Bureau Worksbureauworks.com | 74/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| LingoHublingohub.com | 74/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Locizelocize.com | 65/100 | 6 Data processing agreement, Data location stated, Public pricing, +3 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Wordbeewordbee.com | 39/100 | 3 Public pricing, No third-party tracking before consent, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Tolgeetolgee.io | 30/100 | 2 Data location stated, Public pricing | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Localazylocalazy.com | 26/100 | 2 Public pricing, Named privacy contact | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Text Unitedtextunited.com | 26/100 | 2 Data location stated, Named privacy contact | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Localizelylocalizely.com | 22/100 | 2 Data location stated, Public pricing | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Gridlygridly.com | 30/100 | 1 Public pricing | 1 security.txt (RFC 9116) | Compare |
| memoQmemoq.com | 30/100 | 1 Public pricing | 1 security.txt (RFC 9116) | 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.