Transparency alternatives to Xavo
Other Laboratory information systems vendors we measure, sorted by how much they publish that Xavo does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 44 that differ from Xavo on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Xavo 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, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Xavo does not” is the one that closes them.
| Vendor | Score | Publishes, and Xavo does not | Xavo publishes, and they do not | |
|---|---|---|---|---|
| Nethealth Labnethealth.com | 52/100 | 5 Status page with history, Public pricing, Certifications named, +2 | nothing | Compare |
| LIMSeylimsey.com | 48/100 | 4 Status page with history, Public pricing, Certifications named, +1 | nothing | Compare |
| Benchlingbenchling.com | 43/100 | 3 Subprocessor list, Certifications named, Named privacy contact | nothing | Compare |
| IGORigorlabapp.com | 39/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 1 Data location stated | Compare |
| Quartzyquartzy.com | 30/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Rspaceresearchspace.com | 35/100 | 2 Public pricing, Certifications named | nothing | Compare |
| Genemodgenemod.net | 30/100 | 2 Data processing agreement, Notice before subprocessors change | 1 Data location stated | Compare |
| Scispotscispot.com | 30/100 | 2 Data processing agreement, Notice before subprocessors change | 1 Data location stated | Compare |
| Magic Touchmagictouchsoftware.com | 26/100 | 2 Public pricing, Named privacy contact | 1 HTTPS enforced with HSTS | Compare |
| Labsteplabstep.com | 17/100 | 2 Certifications named, Named privacy contact | 1 Data location stated | Compare |
| Citrine Informaticscitrine.io | 9/100 | 2 Certifications named, Named privacy contact | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Opus Lsysmex.de | 9/100 | 2 security.txt (RFC 9116), Named privacy contact | 2 Data location stated, HTTPS enforced with HSTS | 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.