Alternatives to Nanox AI
Other Medical imaging and radiology vendors we measure, sorted by how much they publish that Nanox AI does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Nanox AI on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Nanox AI has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Nanox AI does not” is the one that closes them.
| Vendor | Score | Publishes, and Nanox AI does not | Nanox AI publishes, and they do not | |
|---|---|---|---|---|
| RamSoftramsoft.com | 48/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | nothing | Compare |
| Merativemerative.com | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Sectrasectra.com | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Aidocaidoc.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 No third-party tracking before consent | Compare |
| eRADerad.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Gleamergleamer.ai | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| HeartFlowheartflow.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Jacobianjacobian.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Milvuemilvue.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| PaxeraHealthpaxerahealth.com | 26/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Qure.aiqure.ai | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| RapidAIrapidai.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | 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.