Transparency alternatives to Compleat Software
Other Procurement vendors we measure, sorted by how much we found at them and not at Compleat Software. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from Compleat Software on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Compleat Software has 9 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Compleat Software” is the one that closes them.
| Vendor | Score | Found there, not found at Compleat Software | Found at Compleat Software, not found there | |
|---|---|---|---|---|
| Keelvarkeelvar.comSee also Transparency alternatives to Keelvar | 70/100 | 5 Subprocessor list, Data location stated, Certifications named, +2 | nothing | Compare |
| Pactumpactum.comSee also Transparency alternatives to Pactum | 39/100 | 5 Data location stated, Public pricing, Certifications named, +2 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Procurifyprocurify.comSee also Transparency alternatives to Procurify | 52/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 Notice before subprocessors change | Compare |
| Precoroprecoro.comSee also Transparency alternatives to Precoro | 39/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Mediusmedius.comSee also Transparency alternatives to Medius | 30/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Onventisonventis.comSee also Transparency alternatives to Onventis | 48/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Zipziphq.comSee also Transparency alternatives to Zip | 39/100 | 3 Subprocessor list, Status page with history, Certifications named | 1 Data processing agreement | Compare |
| Yordexyordex.comSee also Transparency alternatives to Yordex | 35/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Turbineturbinehq.comSee also Transparency alternatives to Turbine | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Levelpathlevelpath.comSee also Transparency alternatives to Levelpath | 26/100 | 2 Data location stated, Status page with history | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Weprocweproc.comSee also Transparency alternatives to Weproc | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Archletarchlet.ioSee also Transparency alternatives to Archlet | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | 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.