Federated model distillation replaces the exchange of high-dimensional model parameters with the exchange of low-dimensional soft labels (logits) computed on a consensus public dataset. Each client acts as a teacher, generating predictions that reveal the relative similarities between classes learned from its private data. The server aggregates these logits to train a student model, effectively compressing the collective knowledge of the network without requiring homogeneous model architectures or exposing sensitive local gradients.
Glossary
Federated Model Distillation

What is Federated Model Distillation?
Federated model distillation is a communication-efficient aggregation strategy where clients share class scores or logits on a public, unlabeled dataset instead of transmitting large model weights, transferring knowledge from a heterogeneous teacher ensemble to a centralized student model.
This paradigm is critical for cross-silo healthcare networks where institutional models may have incompatible architectures. By decoupling the training objective from the model structure, distillation enables collaboration between sites using different neural network topologies. The process inherently provides a degree of privacy, as raw data and model internals remain local, though the shared logits can still leak information and often require differential privacy noise injection for robust protection against model inversion attacks.
Key Features of Federated Distillation
Federated distillation replaces weight transfer with knowledge transfer, using class scores or logits on a public dataset to aggregate heterogeneous teacher models into a compact student model.
Logit-Based Aggregation
Instead of sharing model weights, clients share soft labels (logits) on a public, unlabeled dataset. The server averages these logits to create a consensus teacher ensemble, which distills knowledge into a global student model. This decouples aggregation from model architecture, allowing clients to use heterogeneous model topologies while still contributing to a unified global model.
Communication Efficiency
Distillation dramatically reduces communication overhead compared to weight transfer. Key benefits include:
- Logit vectors are orders of magnitude smaller than model parameter tensors
- Communication cost scales with the public dataset size, not model size
- Enables participation from resource-constrained edge devices that cannot transmit full model weights
- Typical compression ratios of 100x to 1000x over Federated Averaging
Heterogeneous Model Support
A defining advantage of distillation is architecture-agnostic aggregation. Clients can train models with different:
- Neural network architectures (CNNs, transformers, MLPs)
- Layer counts and widths
- Optimization algorithms and hyperparameters This is critical in healthcare, where institutions may have varying computational resources and legacy model investments.
Privacy Preservation Mechanism
Distillation provides an additional privacy layer beyond federated learning. Clients never expose raw model parameters, only aggregated class predictions on public data. This mitigates:
- Model inversion attacks that reconstruct training data from gradients
- Membership inference attacks that determine if a record was in the training set
- Architectural leakage that reveals proprietary model design choices Combined with differential privacy noise on logits, strong formal privacy guarantees are achievable.
Knowledge Distillation Loss Functions
The student model is trained using specialized loss functions that transfer dark knowledge from the teacher ensemble:
- Kullback-Leibler divergence between softened teacher and student logits
- Temperature scaling (T > 1) to reveal inter-class relationships learned by teachers
- Combined with standard cross-entropy loss on any available labeled data
- Optional attention transfer to align intermediate feature representations
Public Dataset Dependency
A key operational requirement is access to an unlabeled public proxy dataset that approximates the global data distribution. Considerations include:
- Dataset must be representative enough to capture teacher knowledge
- Can be sourced from open medical datasets or synthetically generated
- Domain gap between public and private data reduces distillation quality
- Federated data-free distillation variants eliminate this requirement using generative models
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clear, technical answers to the most common questions about how knowledge transfer works across decentralized clinical networks without sharing patient data or model weights.
Federated Model Distillation is a communication-efficient aggregation strategy where participating clients share only their model's output predictions (logits or soft labels) on a public, unlabeled reference dataset, rather than transmitting private model weights or gradients. A central server aggregates these predictions to train a student model that mimics the behavior of the ensemble of local teacher models. This process transfers the dark knowledge embedded in the teachers' soft probability distributions—capturing inter-class relationships—without exposing the underlying patient data or model architectures. The public dataset acts as a transfer medium, enabling knowledge to flow from heterogeneous, site-specific models into a single, globally robust student.
Related Terms
Explore the core concepts that enable knowledge transfer from heterogeneous teacher ensembles to a compact student model without sharing raw data or model weights.
Knowledge Distillation
The foundational technique where a compact student model is trained to mimic the output distribution of a larger, more complex teacher model. In centralized settings, the student minimizes the divergence between its softened logits and the teacher's. This concept is extended to federated settings by treating the ensemble of local client models as the teacher collective, transferring their aggregated knowledge via predictions on a public, unlabeled dataset rather than sharing proprietary model parameters.
Ensemble Distillation
A variant where multiple teacher models are combined into a single student. In Federated Model Distillation, each client acts as an independent teacher. The server aggregates their logit outputs on a public dataset to form a consensus prediction, which the student then learns from. This approach naturally handles model heterogeneity—clients can have different architectures, capacities, and training objectives—since only output scores are communicated, not internal weights.
Logit Aggregation
The process of combining the class score vectors from multiple client models into a single, knowledge-dense training signal for the student. Common strategies include:
- Arithmetic averaging of logits across clients
- Weighted averaging based on client performance or dataset size
- Majority voting on hard predictions
- Temperature scaling to soften probability distributions before aggregation This step is the communication bottleneck, transmitting only low-dimensional vectors instead of full model weights.
Public Proxy Dataset
An unlabeled or labeled dataset accessible to all participants that serves as the transfer medium for knowledge. Clients generate predictions on this shared data, and the server uses these outputs to train the student. The quality and domain relevance of this dataset critically impacts distillation fidelity. Options include:
- Publicly available datasets (e.g., ImageNet, Wikipedia)
- Synthetic data generated by a separate model
- A held-out portion of unlabeled data agreed upon by the consortium
Communication Efficiency
A primary motivation for federated distillation over weight-sharing approaches like FedAvg. Instead of transmitting millions of model parameters per round, clients send only logit vectors whose size equals the number of output classes. For a 1,000-class problem, this reduces communication from gigabytes to kilobytes per client per round. This makes distillation viable for cross-device federated learning where clients operate on bandwidth-constrained mobile or edge hardware.
Heterogeneous Model Support
Unlike weight-averaging methods that require all clients to share an identical model architecture, federated distillation imposes no architectural constraints. Clients can train CNNs, transformers, or even non-neural models like gradient-boosted trees. This enables participation from institutions with vastly different computational resources and legacy model investments, making it ideal for cross-silo healthcare networks where standardization is impractical.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us