Transparency alternatives to Achievers
Other Performance management vendors we measure, sorted by how much we found at them and not at Achievers. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Achievers on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Achievers has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Achievers” is the one that closes them.
| Vendor | Score | Found there, not found at Achievers | Found at Achievers, not found there | |
|---|---|---|---|---|
| Betterworksbetterworks.comSee also Transparency alternatives to Betterworks | 65/100 | 6 Subprocessor list, Public pricing, Uptime SLA with a figure, +3 | nothing | Compare |
| Latticelattice.comSee also Transparency alternatives to Lattice | 57/100 | 6 Subprocessor list, Status page with history, Public pricing, +3 | 1 Data location stated | Compare |
| PerformYardperformyard.comSee also Transparency alternatives to PerformYard | 65/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | nothing | Compare |
| Leapsomeleapsome.comSee also Transparency alternatives to Leapsome | 61/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | 1 Certifications named | Compare |
| Perdooperdoo.comSee also Transparency alternatives to Perdoo | 61/100 | 5 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Profit.coprofit.coSee also Transparency alternatives to Profit.co | 57/100 | 5 Data processing agreement, Status page with history, Uptime SLA with a figure, +2 | nothing | Compare |
| WorkBoardworkboard.comSee also Transparency alternatives to WorkBoard | 48/100 | 5 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +2 | 1 Data location stated | Compare |
| Culture Ampcultureamp.comSee also Transparency alternatives to Culture Amp | 48/100 | 4 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Certifications named | Compare |
| Kudoskudos.comSee also Transparency alternatives to Kudos | 48/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Nectarnectarhr.comSee also Transparency alternatives to Nectar | 48/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| Small Improvementssmall-improvements.comSee also Transparency alternatives to Small Improvements | 43/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Quantum Workplacequantumworkplace.comSee also Transparency alternatives to Quantum Workplace | 30/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 2 Data location stated, Certifications named | 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.