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