Rapha Protocol vs Rhino Health
Rhino Health vs Rapha Protocol — the honest comparison
Both platforms address clinical AI data access. But they take fundamentally different paths — and the difference determines whether your project launches in weeks or dies in legal review.
How Rhino Health works (and why it fails)
Rhino Health uses federated learning — each hospital trains locally, then sends model gradients to a central aggregation server. These gradients are mathematically invertible to reconstruct original training data. The "privacy" promise of FL is false: gradients leak information.
Rhino Health's critical weakness: Rhino Health transmits gradients that can be inverted to patient data. Requires all sites online simultaneously. Container-based software isolation — the hospital OS can still access your training process. No SGX/TDX hardware enclave. No kernel-level air-gap. Legal teams will not approve gradient transmission of PHI.
Why Rapha Protocol wins — 4 decisive advantages
1. Access to Way More Real Clinical Datasets — Instantly
Rapha Protocol connects you to real hospital imaging, EHR, and clinical text data — orders of magnitude more datasets than any competitor. Rhino Health's approach requires per-hospital contracts, per-trust legal review, and per-site technical integration. Each hospital takes 6-18 months to onboard. Each additional hospital requires the same cycle again.
Rapha Protocol: hospitals deploy one edge appliance. All AI companies connect through the same infrastructure. One hospital onboarding unlocks datasets for every AI researcher on the network. Rhino Health's model is linear — your data access grows one painful contract at a time. Rapha's model is networked — each new hospital multiplies the available datasets for every existing user.
Rapha eliminates the per-hospital procurement cycle entirely. One API key. Three commands. Immediate access to any configured hospital node.
2. Access the Entire Network in 3 Commands — Not 18 Months of Procurement
Rhino Health's timeline: initial contact → legal review → data sharing agreement → DPIA → compliance assessment → technical integration → pilot → production. Typical outcome: 12-18 months, $200K+ in legal fees, and the project may still be rejected by the hospital's DPO or Caldicott Guardian.
Rapha Protocol's timeline:
npm install rapha-airapha submit --model ./my-model.pt --dataset uk.nhs.edinburgh.oncology_mri --budget 5000rapha download --weights ./trained-weights.pt
Three commands. Your model trains on real clinical data inside the hospital's SGX/TDX enclave. You receive trained weights, not patient data. The entire procurement cycle — legal, compliance, technical, financial — is handled by the Rapha Protocol infrastructure layer, not by your team.
With Rhino Health, every one of these steps is your problem. With Rapha, they are solved before you send your first command.
3. Infinitely Easier to Use — Designed to Just Work
Rhino Health requires you to understand federated learning architectures, gradient aggregation, non-IID convergence issues, and multi-site coordination.
Rapha Protocol is designed so an AI researcher who has never touched healthcare infrastructure can submit a training job in under 5 minutes. The SDK handles authentication, job submission, status polling, and artifact download. The secure API manages ZK-TLS sessions, developer keys, and proof verification server-side. You focus on your model. We handle the healthcare complexity.
- No hospital contracts to negotiate. No DUAs to draft. No DPIA to write.
- No cloud infrastructure to provision. No GPUs to rent. No networking to configure.
- No FL coordination. No gradient leakage mitigation. No non-IID convergence debugging.
- One SDK. Three commands. Trained model weights as output.
4. Military-Grade Security — So Your Company Does Not Get Sued Into Oblivion
Healthcare AI companies face existential legal risk. One PHI breach — one misconfigured S3 bucket, one compromised API key, one de-identified dataset that gets re-identified — and your company faces regulatory fines, civil lawsuits, criminal liability, and reputational destruction. Rhino Health's model: gradients leave the hospital. If those gradients are inverted to reveal patient data (demonstrated in multiple published attacks), your company transmitted PHI — even if you called it a "gradient."
Rapha Protocol's security architecture eliminates PHI liability:
- Data never leaves the hospital. Not encrypted. Not de-identified. Not "pseudonymised." Never exported. Period. No PHI custody = no PHI breach liability.
- SGX/TDX hardware enclave. Intel CPU-level memory encryption. Even the hospital's own IT staff with root access cannot inspect data during training.
- Rust kernel air-gap. The WAN interface is physically severed at the kernel level during training. Data cannot be exfiltrated because there is no network path.
- Go OPA compliance guard. Every training script and Docker container is statically analysed for network-capable dependencies before execution. socket, requests, urllib, http.client — all blocked.
- Output validation. Only approved file types (.safetensors, .pt, .json) can leave the enclave. Raw data files (.csv, .dcm, .jsonl, .fhir, .parquet) are blocked at the filesystem level.
- On-chain proof receipts. Every training job produces a cryptographic proof receipt anchored on Polygon mainnet. You can prove — to regulators, to auditors, to your board — that no PHI was exported.
The bottom line: Rhino Health's architecture creates PHI exposure. Rapha Protocol's architecture eliminates it. When the regulator asks for your PHI exposure assessment, which answer would you rather give?
Head-to-head comparison
Rapha Protocol
- Data stays in hospital — never exported
- 3 commands to start training
- SGX/TDX hardware enclave
- Kernel-level WAN air-gap during training
- OPA policy enforcement
- On-chain proof receipts
- Per-job USDC settlement
- 70% hospital revenue share
- No legal procurement cycle
- Access to growing hospital network
Rhino Health
- Gradients leave hospitals — invertible to data
- Multi-site coordination required
- No hardware enclave (software-only)
- Network connected during training
- No kernel-level isolation
- No on-chain proof receipts
- No per-job settlement
- No hospital revenue sharing
- 12-18 month procurement cycle
- Linear hospital onboarding (one at a time)
Community discussion
"We spent 14 months trying to negotiate data access through federated learning with two hospitals. Our security team flagged the gradient transmission as equivalent to PHI export. They cited the Deep Leakage from Gradients paper (Zhu et al. 2019) in their formal rejection. Rapha's model — full training inside the hospital with only weights leaving — passed their review because there is literally no data transmission to attack."
Rapha Protocol is private-alpha infrastructure. This comparison is based on publicly available documentation and architectural analysis. Platform capabilities may change. Evaluate all options independently for your specific requirements.