Transparency alternatives to Quartzy
Other Laboratory information systems vendors we measure, sorted by how much we found at them and not at Quartzy. This is a comparison of disclosure, not of features or fitness.
Need a functional replacement? Run a synthetic sample trial before comparing product fit. This disclosure table cannot establish which modules or workflows another product can replace. Follow the sample workflow checklist.
12 shown of 46 that differ from Quartzy on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Quartzy has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Quartzy” is the one that closes them.
| Vendor | Score | Found there, not found at Quartzy | Found at Quartzy, not found there | |
|---|---|---|---|---|
| Nethealth Labnethealth.comSee also Transparency alternatives to Nethealth Lab | 52/100 | 4 Data location stated, Certifications named, Uptime SLA with a figure, +1 | 1 security.txt (RFC 9116) | Compare |
| Benchlingbenchling.comSee also Transparency alternatives to Benchling | 43/100 | 4 Subprocessor list, Data location stated, Certifications named, +1 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| LIMSeylimsey.comSee also Transparency alternatives to LIMSey | 48/100 | 3 Data location stated, Certifications named, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Scispotscispot.comSee also Transparency alternatives to Scispot | 35/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| IGORigorlabapp.comSee also Transparency alternatives to IGOR | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Rspaceresearchspace.comSee also Transparency alternatives to Rspace | 35/100 | 2 Data location stated, Certifications named | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Genemodgenemod.netSee also Transparency alternatives to Genemod | 30/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Dotmaticsdotmatics.comSee also Transparency alternatives to Dotmatics | 26/100 | 2 Data location stated, Named privacy contact | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Magic Touchmagictouchsoftware.comSee also Transparency alternatives to Magic Touch | 26/100 | 2 Data location stated, Named privacy contact | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| SciSurescisure.comSee also Transparency alternatives to SciSure | 26/100 | 2 Data location stated, Named privacy contact | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Dornerdorner.deSee also Transparency alternatives to Dorner | 22/100 | 2 No third-party tracking before consent, Named privacy contact | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Labsteplabstep.comSee also Transparency alternatives to Labstep | 17/100 | 2 Certifications named, Named privacy contact | 3 Status page with history, Public pricing, 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.