Transparency alternatives to Magic Touch
Other Laboratory information systems vendors we measure, sorted by how much we found at them and not at Magic Touch. 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 45 that differ from Magic Touch on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Magic Touch has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, 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 “Found there, not found at Magic Touch” is the one that closes them.
| Vendor | Score | Found there, not found at Magic Touch | Found at Magic Touch, not found there | |
|---|---|---|---|---|
| Genemodgenemod.netSee also Transparency alternatives to Genemod | 52/100 | 5 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +2 | 2 Public pricing, Named privacy contact | Compare |
| Nethealth Labnethealth.comSee also Transparency alternatives to Nethealth Lab | 52/100 | 4 Status page with history, Certifications named, Uptime SLA with a figure, +1 | nothing | Compare |
| Scispotscispot.comSee also Transparency alternatives to Scispot | 43/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data location stated, Named privacy contact | Compare |
| LIMSeylimsey.comSee also Transparency alternatives to LIMSey | 48/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | nothing | Compare |
| Benchlingbenchling.comSee also Transparency alternatives to Benchling | 43/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| IGORigorlabapp.comSee also Transparency alternatives to IGOR | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Data location stated, Named privacy contact | Compare |
| Quartzyquartzy.comSee also Transparency alternatives to Quartzy | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Rspaceresearchspace.comSee also Transparency alternatives to Rspace | 35/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Labsteplabstep.comSee also Transparency alternatives to Labstep | 30/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Public pricing | Compare |
| Dornerdorner.deSee also Transparency alternatives to Dorner | 22/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 Data location stated, Public pricing | Compare |
| LabCuplabcup.netSee also Transparency alternatives to LabCup | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data location stated, Public pricing, Named privacy contact | Compare |
| QbDVisionqbdvision.comSee also Transparency alternatives to QbDVision | 13/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data location stated, Public pricing, 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.