Microsoft Azure holds a narrow lead over AWS for enterprise cloud infrastructure and confidential virtual machines. For confidential inference enclaves or FLOPS-per-watt optimization, NVIDIA is the usual answer.
Since July, Intelrising has become one of the three most named options for confidential inference enclaves. NVFlarerising, Owkinrising, and Zeusrising have also grown across the market.
Latest insights
Week of Sep 21–27 · Since Jul 5
AWS Gaining: AI answers in AI Compute Infrastructure Solutions name AWS more often: mention rate grew from 87.5% to 93.8%
Google Cloud Platform Gaining: Google Cloud Platform's mention rate in AI Compute Infrastructure Solutions rose 12.5 points to 87.5%
AMD Gap between platforms: The platform gap for AMD in AI Compute Infrastructure Solutions narrowed to 31.1 points, ChatGPT Search ahead
Intel Slipping: Intel's mention rate in AI Compute Infrastructure Solutions fell 6.3 points to 31.3%
Owkin Slipping: Owkin's mention rate decreased to 43.8% in AI Compute Infrastructure Solutions, from 50% the week before
53% of citations point at the ranked brands’ own sites. arxiv.org, youtube.com, next.redhat.com are the most-cited sites outside the ranked brands’ own domains.
When building a federated learning (FL) system for healthcare, infrastructure is typically divided into open-source frameworks (which handle the orchestration, aggregation, and local training logic) and enterprise/cloud platforms (which provide the secure compute, storage, and networking layers across institutions).
1. Open-Source Federated Learning Frameworks (The Orchestration Layer)
These are the foundational software engines used to build the federated network topology, manage round coordination, and secure gradient/parameter exchanges:
NVIDIA FLARE (NVIDIA Federated Learning Application Runtime Environment): Extensively used in healthcare and medical imaging; integrates deeply with GPU infrastructure and enterprise security.
Flower : A friendly, highly extensible framework supporting various machine learning frameworks (PyTorch, TensorFlow, JAX) and heavily adopted in cross-silo enterprise setups.
/ : Focuses strongly on privacy-preserving techniques like differential privacy, homomorphic encryption, and secure multi-party computation.
What companies offer the underlying infrastructure needed to run a federated learning system in a healthcare setting?
We are auditing the energy efficiency of our training runs. Who provides FLOPS-per-watt optimization?
I need a secure enclave solution for running confidential AI inference.
PySyft
OpenMined
Fed-BioMed : Specifically tailored for trustworthy collaborative healthcare and medical research environments.[](https://fedbiomed.org/)
OpenFL (Intel Open Federated Learning): An open-source framework designed for secure, confidential federated learning, optimized for Intel architecture.
Hospitals rarely build infrastructure from scratch; they rely on secure enterprise platforms or hyperscalers that support confidential computing and HIPAA/GDPR compliance:
NVIDIA Clara / AI Enterprise : Often paired with NVIDIA FLARE, providing hardware-accelerated infrastructure for medical imaging and clinical AI deployment.
Microsoft Azure / AWS / Google Cloud : Hyperscalers provide the virtual private clouds (VPCs), secure API gateways, and Confidential Computing instances (using Intel SGX or AMD SEV) ensuring data in transit and in memory remains encrypted during aggregation.
For a healthcare federated learning system, infrastructure is typically provided by a combination of cloud providers, federated learning platform vendors, and participating hospitals. There isn't one universal provider; the right choice depends on whether you're building the system yourselves or buying a managed solution.
Key infrastructure providers
1. NVIDIA — FLARE
Provides an open-source federated learning runtime for coordinating training across healthcare institutions while keeping patient data at each site. It can run on infrastructure you manage or in the cloud.
Best for: building a customizable, production-oriented system.
Provides a healthcare-focused federated computing platform for connecting hospitals, harmonizing clinical data, and training AI models without centrally collecting patient records. Its platform is used in cancer research collaborations.
Best for: multi-hospital deployments where you want a specialized platform vendor.
Offers open-source federated learning software and an enterprise platform, including deployment support for Docker and Kubernetes. It can use existing hardware and cloud infrastructure.
Best for: teams building their own federated learning architecture.
Provides a managed federated research environment for biomedical and health data, with cloud integration, security controls, and tools for analyzing data where it resides.
Best for: biomedical research networks that need secure data access and analysis as well as federation.
5. Amazon Web Services (AWS), Microsoft Azure, and Google Cloud
Supply the underlying compute, storage, networking, identity, and security services. These are infrastructure providers rather than, by themselves, complete healthcare federated learning solutions. AWS has documented deployments using NVIDIA FLARE.
Best for: organizations that want to operate and control their own infrastructure.
Who provides what?
Infrastructure layer
Typical provider
Federated training and coordination
NVIDIA FLARE, Flower
Managed healthcare federation
Rhino Health, Lifebit
Cloud computing and GPUs
AWS, Azure, Google Cloud
Local data and hospital systems
Participating hospitals and health systems
Security, access control and governance
A concrete example is the Cancer AI Alliance, a collaboration of major US cancer centers supported by AWS, Google, Microsoft, NVIDIA, and other technology organizations. Its federated AI platform enables research across institutions while protecting sensitive clinical data.
My recommendation
Building your own platform: Start by evaluating NVIDIA FLARE or Flower, with cloud infrastructure as needed.
Connecting multiple hospitals quickly: Evaluate Rhino Health or Lifebit for managed infrastructure.
Building a large research consortium: Consider a hybrid architecture with hospital-controlled compute, centralized orchestration, and cloud-hosted coordination services.
One important distinction: the platform vendor usually does not own or supply all the patient data or hospital infrastructure. Each participating healthcare organization generally remains responsible for its local data, permissions, and deployment environment.
To narrow this down: Are you building a system for (1) a few hospitals, (2) a large multi-hospital research network, or (3) a commercial healthcare AI product? The best infrastructure provider differs significantly across these three scenarios.
Yes. The market is best understood as a stack: some companies provide the federated-learning runtime itself, while others provide a healthcare-specific federation platform or the underlying cloud/compute.
Used in medical imaging, oncology, genomics, COVID research, and multi-hospital collaborations. NVIDIA's current healthcare materials specifically highlight federated computing.
Production FL infrastructure / hospital networks
Rhino Health
Healthcare-focused federated computing platform, including edge computing and MLOps
NVIDIA identifies Rhino as a federated platform for multi-site medical AI; its platform integrates NVIDIA FLARE and has been used by healthcare/life-science organizations.
Turnkey healthcare federation
Owkin / Substra
Healthcare-oriented open-source FL software and ecosystem
Substra originated at Owkin and has been deployed with hospitals and biotech organizations. Owkin has demonstrated FL across multiple hospitals for oncology/histopathology.
Clinical research, pharma, multi-hospital AI
Flower
Enterprise federated-AI framework/platform
Flower offers an enterprise product for production federated AI and explicitly lists healthcare, NHS and drug discovery among its deployments/use cases.
Flexible developer platform / enterprise FL
Flywheel
Biomedical data/imaging platform integrated with FL infrastructure
Flywheel documents healthcare deployments combining its imaging platform with NVIDIA FLARE and NVIDIA infrastructure to train across hospitals.
Medical imaging + FL
Intel
Compute infrastructure and acceleration rather than a turnkey FL platform
Intel documents medical FL deployments using Intel Xeon + Data Center GPU infrastructure, including multi-hospital medical-imaging scenarios.
On-prem/edge compute for FL
AWS / Azure / Google Cloud / OCI
Underlying cloud, GPU, networking, security and orchestration infrastructure
These clouds can host the FL coordinator and/or site infrastructure; healthcare data services provide FHIR/DICOM/HL7 capabilities.
Underlying infrastructure rather than healthcare-specific FL
My shortlist
If you're looking for providers you could actually approach about deploying federated learning across hospitals, I'd prioritize:
Rhino Health — probably the closest match to "healthcare federated-learning infrastructure provider." It abstracts much of the infrastructure complexity and is explicitly designed around healthcare/life-sciences federation.
NVIDIA FLARE — particularly compelling if you want to build/control the infrastructure yourself. It's open source, supports PyTorch/TensorFlow, and has substantial real-world healthcare validation.
Owkin / Substra — especially strong for pharma, clinical research, oncology and multi-institutional research. Substra has been used in production healthcare environments.
Flower Enterprise — attractive if you want a more general-purpose federated-AI platform with healthcare support rather than a medical-imaging-specific stack.
One important distinction
I would not put AWS, Azure, or Google Cloud in the same category as Rhino or Substra. They can supply the underlying infrastructure, but the federated-learning layer generally comes from a framework such as NVIDIA FLARE, Flower, or Substra. A typical architecture is:
Hospital A data + FL client
↕ Hospital B data + FL client → FL orchestration/aggregation layer → Cloud/on-prem compute
↕ Hospital C data + FL client
The critical healthcare requirement is that patient data remains inside each institution, while model updates/parameters and approved metadata are exchanged. NVIDIA's healthcare implementations and Owkin's multi-hospital work demonstrate this architecture in practice.
There is also an interesting newer example: FLIP (Federated Learning Interoperability Platform) from the London AI Centre, King's College London, and Guy's & St Thomas' NHS Foundation Trust. It is specifically designed for production healthcare networks and supports both NVIDIA FLARE and Flower backends.
If your goal is vendor selection/procurement, I can next build you a more detailed 20–30 provider landscape with columns for HIPAA/GDPR, on-prem deployment, cloud support, EHR/FHIR integration, medical imaging, managed vs. open source, pricing/business model, healthcare customers, and geographic coverage.