Transparency alternatives to Thread
Other Clinical trial software vendors we measure, sorted by how much we found at them and not at Thread. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Thread on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Thread has 9 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. The column “Found there, not found at Thread” is the one that closes them.
| Vendor | Score | Found there, not found at Thread | Found at Thread, not found there | |
|---|---|---|---|---|
| 4G Clinical4gclinical.comSee also Transparency alternatives to 4G Clinical | 30/100 | 2 Subprocessor list, Certifications named | 1 Data location stated | Compare |
| OpenClinicaopenclinica.comSee also Transparency alternatives to OpenClinica | 30/100 | 2 Public pricing, Certifications named | 1 HTTPS enforced with HSTS | Compare |
| Florenceflorencehc.comSee also Transparency alternatives to Florence | 26/100 | 2 Status page with history, Certifications named | 1 Data location stated | Compare |
| Cluepointscluepoints.comSee also Transparency alternatives to Cluepoints | 22/100 | 2 Status page with history, Certifications named | 2 Data location stated, Named privacy contact | Compare |
| Suvodasuvoda.comSee also Transparency alternatives to Suvoda | 30/100 | 1 Subprocessor list | 1 HTTPS enforced with HSTS | Compare |
| TrialKitcrucialdatasolutions.comSee also Transparency alternatives to TrialKit | 30/100 | 1 Certifications named | nothing | Compare |
| Viedocviedoc.comSee also Transparency alternatives to Viedoc | 22/100 | 1 Status page with history | 1 Data location stated | Compare |
| Wcgclinicalwcgclinical.comSee also Transparency alternatives to Wcgclinical | 17/100 | 1 Subprocessor list | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Montriummontrium.comSee also Transparency alternatives to Montrium | 13/100 | 1 Certifications named | 2 Data location stated, Named privacy contact | Compare |
| Trialdatatrialdata.deSee also Transparency alternatives to Trialdata | 13/100 | 1 security.txt (RFC 9116) | 2 Data location stated, Named privacy contact | Compare |
| Cloudbyzcloudbyz.comSee also Transparency alternatives to Cloudbyz | 9/100 | 1 Certifications named | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Insteminstem.comSee also Transparency alternatives to Instem | 9/100 | 1 Certifications named | 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.