Alternatives to Viamedici
Other Product information management vendors we measure, sorted by how much they publish that Viamedici does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Viamedici on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Viamedici 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 Viamedici does not” is the one that closes them.
| Vendor | Score | Publishes, and Viamedici does not | Viamedici publishes, and they do not | |
|---|---|---|---|---|
| Alationalation.com | 52/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Ataccamaataccama.com | 43/100 | 4 Public pricing, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Reltioreltio.com | 39/100 | 4 Status page with history, Certifications named, Uptime SLA with a figure, +1 | 1 Named privacy contact | Compare |
| data.worlddata.world | 39/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Akeneoakeneo.com | 35/100 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | nothing | Compare |
| Castorcastordoc.com | 30/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| GoDataFeedgodatafeed.com | 30/100 | 3 Subprocessor list, Public pricing, HTTPS enforced with HSTS | 2 Data location stated, Named privacy contact | Compare |
| Atlanatlan.com | 26/100 | 3 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Collibracollibra.com | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| inriverinriver.com | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Sales Layersaleslayer.com | 30/100 | 2 Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Bluestone PIMbluestonepim.com | 26/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 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.