Alternatives to Weproc
Other Procurement vendors we measure, sorted by how much they publish that Weproc does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 16 that differ from Weproc on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Weproc has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, 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. The column “publishes and Weproc does not” is the one that closes them.
| Vendor | Score | Publishes, and Weproc does not | Weproc publishes, and they do not | |
|---|---|---|---|---|
| Keelvarkeelvar.com | 70/100 | 6 Data processing agreement, Subprocessor list, Certifications named, +3 | nothing | Compare |
| Procurifyprocurify.com | 52/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | nothing | Compare |
| Pactumpactum.com | 35/100 | 4 Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 1 Named privacy contact | Compare |
| Mediusmedius.com | 30/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Onventisonventis.com | 48/100 | 3 Data processing agreement, Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| Archletarchlet.io | 35/100 | 2 Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| Ivaluaivalua.com | 30/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | nothing | Compare |
| Baswarebasware.com | 22/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Levelpathlevelpath.com | 26/100 | 1 Status page with history | nothing | Compare |
| Fairmarkitfairmarkit.com | 9/100 | 1 HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| GEPgep.com | 9/100 | 1 HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| IntegrityNextintegritynext.com | 9/100 | 1 HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | 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.