Knowledge Distillation Aggregation (FedKD) is a federated model fusion technique where a global student model learns by matching the aggregated soft label predictions or logit outputs from an ensemble of local teacher models, rather than averaging their numerical weights. This transfers the dark knowledge of heterogeneous local models into a single compact global model.
Glossary
Knowledge Distillation Aggregation (FedKD)

What is Knowledge Distillation Aggregation (FedKD)?
A model fusion technique that aggregates local knowledge by matching the logit outputs or soft labels of a global student model to the ensemble of local teacher models, rather than averaging weights.
In FedKD, each client trains a teacher model locally and shares only its output predictions on a public or synthetic dataset with the server. The server aggregates these soft labels via averaging or voting, then trains the global student model to mimic the consensus. This approach handles model heterogeneity—allowing clients to use different architectures—and provides an additional layer of privacy by avoiding direct gradient or weight sharing.
Key Features of FedKD
Knowledge Distillation Aggregation (FedKD) replaces weight averaging with a teacher-student paradigm. A global student model learns from the ensemble of local teacher models by matching their output distributions, enabling heterogeneous model architectures and non-IID data fusion.
Logit-Based Knowledge Transfer
Instead of averaging parameter vectors, FedKD aggregates knowledge by matching the soft labels (logit outputs) of local teacher models. The global student model is trained to minimize the Kullback-Leibler (KL) divergence between its softened output distribution and the aggregated outputs of the teacher ensemble. This operates on a model-agnostic level, allowing teachers and the student to have completely different architectures.
Heterogeneous Model Support
A primary advantage over Federated Averaging (FedAvg) is the ability to fuse models with non-identical architectures. Local clients can train CNNs, RNNs, or Transformers of varying widths and depths. The global server only requires access to their output logits on a public or synthetically generated dataset, abstracting away the internal parameter structure and enabling cross-modal fusion.
Ensemble Distillation on the Server
The server acts as a central distillation hub. It queries all local teacher models with an unlabeled public dataset to collect their predictive distributions. These distributions are aggregated (e.g., via simple averaging) to form a consensus teacher ensemble. The global student model is then trained via standard knowledge distillation to mimic this ensemble, effectively compressing distributed knowledge into a single deployable model.
Privacy Preservation via Output Exchange
FedKD enhances privacy by design because raw model parameters and gradients are never transmitted to the server. Only the model's output logits on a public reference dataset are shared. This breaks the direct link to private training data, providing a natural defense against gradient inversion and membership inference attacks, though it requires careful curation of the distillation dataset to prevent information leakage.
Robustness to Non-IID Data
FedKD demonstrates strong resilience to statistical heterogeneity. Since the global student learns from the aggregated output behavior rather than conflicting parameter directions, it avoids the weight divergence problem common in FedAvg. The distillation process naturally smooths out local biases, converging to a solution that captures the consensus knowledge across diverse, non-IID clinical data silos.
Communication Efficiency Trade-offs
While FedKD eliminates the need to transmit large model weights, it introduces a query-based communication cost. The server must send the public dataset to clients, and clients must return logit vectors for every sample. This is efficient for large models with small output spaces but can become a bottleneck for tasks with high-dimensional outputs. Techniques like logit quantization are often applied to mitigate this overhead.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about how Federated Knowledge Distillation (FedKD) aggregates model knowledge without sharing weights or raw data.
Knowledge Distillation Aggregation (FedKD) is a federated model fusion technique that aggregates local knowledge by matching the logit outputs or soft labels of a global student model to the ensemble of local teacher models, rather than averaging their weight parameters. In a typical FedKD round, each client trains a local teacher model on its private data. These teachers then generate predictions on a public, unlabeled distillation dataset—often a held-out proxy corpus or synthetically generated samples. The central server aggregates these soft predictions, typically by averaging the logits or class probabilities across all teachers, and uses the resulting consensus labels to train a single global student model via standard supervised distillation loss. This approach bypasses the weight-space alignment challenges of Federated Averaging (FedAvg), making it inherently robust to heterogeneous model architectures and non-IID data distributions across clinical sites.
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.
Related Terms
Knowledge Distillation Aggregation (FedKD) represents a distinct paradigm shift from weight-space averaging to output-space alignment. The following related concepts contextualize FedKD within the broader landscape of federated model fusion, robust aggregation, and personalization strategies.
Federated Averaging (FedAvg)
The foundational weight-space aggregation algorithm that constructs a global model by computing an element-wise weighted average of locally trained model parameters. Unlike FedKD, which operates on logit outputs, FedAvg directly merges model weights, requiring all clients to share identical model architectures. This makes FedAvg incompatible with heterogeneous model deployments but highly efficient when architectural homogeneity is guaranteed.
Federated Ensemble Aggregation (FedEnsemble)
A model fusion technique that treats locally trained models as an independent ensemble, combining their predictions via voting or averaging at inference time rather than distilling them into a single global model. FedKD improves upon this by compressing the ensemble's collective knowledge into a compact student model, reducing inference latency and eliminating the need to maintain multiple teacher models in production.
Personalized Aggregation (pFedMe)
An aggregation framework using Moreau envelopes to decouple personalized model optimization from global model learning. While pFedMe focuses on parameter-space personalization through regularization, FedKD achieves personalization through soft label alignment, allowing local models to retain unique predictive characteristics without requiring complex bi-level optimization procedures.
Byzantine Fault Tolerance (BFT) Aggregation
A class of robust aggregation rules—including Krum and Trimmed Mean—designed to ensure convergence when malicious nodes submit corrupted updates. FedKD provides inherent Byzantine resilience because distillation operates on soft labels rather than raw gradients. Anomalous logit distributions from compromised clients are naturally attenuated during the KL divergence minimization process, as they diverge from the ensemble consensus.
Federated Normalization Aggregation (FedBN)
An aggregation strategy that excludes batch normalization layers from global averaging, preserving local batch statistics to combat feature shift across sites. FedKD inherently avoids batch norm mismatch issues because it never transfers parameters—only soft label distributions. This makes FedKD particularly suitable for cross-institutional medical imaging where scanner-specific normalization varies dramatically.
Differential Privacy Aggregation (DP-FedAvg)
An aggregation mechanism injecting calibrated Gaussian noise into model updates to provide formal privacy guarantees. When combined with FedKD, differential privacy can be applied to the distilled logit outputs rather than high-dimensional weight vectors, achieving tighter privacy-utility tradeoffs due to the lower sensitivity of soft labels compared to raw gradients in weight-space aggregation.

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