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