Transparency alternatives to LIMSey
Other Laboratory information systems vendors we measure, sorted by how much we found at them and not at LIMSey. 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 LIMSey on at least one criterion we measured for both. Public transparency score, not a product or security rating.
LIMSey has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at LIMSey” is the one that closes them.
| Vendor | Score | Found there, not found at LIMSey | Found at LIMSey, not found there | |
|---|---|---|---|---|
| Genemodgenemod.netSee also Transparency alternatives to Genemod | 52/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 3 Status page with history, Public pricing, Named privacy contact | Compare |
| Scispotscispot.comSee also Transparency alternatives to Scispot | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| IGORigorlabapp.comSee also Transparency alternatives to IGOR | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 4 Data location stated, Status page with history, Certifications named, +1 | Compare |
| Nethealth Labnethealth.comSee also Transparency alternatives to Nethealth Lab | 52/100 | 1 Uptime SLA with a figure | nothing | Compare |
| Benchlingbenchling.comSee also Transparency alternatives to Benchling | 43/100 | 1 Subprocessor list | 2 Status page with history, Public pricing | Compare |
| Quartzyquartzy.comSee also Transparency alternatives to Quartzy | 30/100 | 1 security.txt (RFC 9116) | 3 Data location stated, Certifications named, Named privacy contact | Compare |
| Dornerdorner.deSee also Transparency alternatives to Dorner | 22/100 | 1 No third-party tracking before consent | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Ilisilis.deSee also Transparency alternatives to Ilis | 22/100 | 1 No third-party tracking before consent | 5 Status page with history, Public pricing, Certifications named, +2 | Compare |
| Citrine Informaticscitrine.ioSee also Transparency alternatives to Citrine Informatics | 13/100 | 1 No third-party tracking before consent | 5 Data location stated, Status page with history, Public pricing, +2 | Compare |
| Nexus Labnexus-ag.deSee also Transparency alternatives to Nexus Lab | 9/100 | 1 No third-party tracking before consent | 6 Data location stated, Status page with history, Public pricing, +3 | Compare |
| Opus Lsysmex.deSee also Transparency alternatives to Opus L | 9/100 | 1 security.txt (RFC 9116) | 5 Data location stated, Status page with history, Public pricing, +2 | Compare |
| Sciformationsciformation.comSee also Transparency alternatives to Sciformation | 9/100 | 1 No third-party tracking before consent | 6 Data location stated, Status page with history, Public pricing, +3 | 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.