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