A Hybrid MPC-HE Protocol is a cryptographic framework that strategically partitions computation between Homomorphic Encryption (HE) and Multi-Party Computation (MPC) to achieve optimal performance for privacy-preserving machine learning. The protocol leverages HE for efficient linear operations like matrix multiplications and convolutions directly on ciphertext, while delegating non-linear functions such as activation layers to an MPC protocol, avoiding the deep noise budget consumption and high latency of polynomial approximations.
Glossary
Hybrid MPC-HE Protocol

What is a Hybrid MPC-HE Protocol?
A design pattern combining the linear-operation efficiency of Homomorphic Encryption with the non-linear evaluation efficiency of Multi-Party Computation to optimize end-to-end encrypted inference latency.
This architecture addresses the core limitation of pure HE inference, where evaluating non-linearities requires costly bootstrapping or imprecise polynomial approximations. By switching to a secret-shared MPC domain for ReLU or MaxPool operations, the hybrid design minimizes the multiplicative depth of the HE circuit. The result is a protocol that achieves lower amortized latency and higher inference accuracy than either primitive alone, making it a practical solution for encrypted inference on complex neural networks.
Key Features of Hybrid MPC-HE Protocols
Hybrid protocols strategically decompose computation to leverage the arithmetic efficiency of Homomorphic Encryption and the non-linear efficiency of Multi-Party Computation, minimizing end-to-end encrypted inference latency.
Linear vs. Non-Linear Decomposition
The protocol partitions a neural network into linear layers (convolutions, matrix multiplications) and non-linear layers (ReLU, MaxPool, Softmax).
- HE Domain: Linear operations are executed on packed ciphertexts using SIMD operations, achieving high throughput without interaction.
- MPC Domain: Non-linear functions are evaluated using secret-shared inputs and optimized circuits (e.g., Garbled Circuits or OT-based comparisons), avoiding costly polynomial approximations.
Ciphertext-to-Secret-Sharing Conversion
A critical bridging primitive that transitions data between cryptographic domains without decryption.
- HE-to-MPC: The party holding the HE ciphertext additively secret-shares the plaintext under the encryption and distributes shares to MPC parties, who then interactively remove the HE mask.
- MPC-to-HE: MPC parties collectively encrypt their output shares under a target public key, combining them homomorphically to produce a single ciphertext for further linear processing.
Input Privacy Guarantees
The hybrid model ensures the model owner's weights and the client's input remain private.
- Client Input: Encrypted under HE and never revealed in plaintext to the model host or MPC parties.
- Model Weights: Stored as secret shares among non-colluding MPC servers, preventing any single server from reconstructing the proprietary model.
- Output: Only the designated recipient can decrypt the final result, typically via threshold decryption.
Communication-Computation Trade-off
Protocol designers balance local computation against interactive rounds.
- HE-Heavy Designs: Minimize interaction by performing as many layers as possible under HE, switching to MPC only for deep non-linearities. This reduces bandwidth but increases local compute.
- MPC-Heavy Designs: Switch to MPC early to leverage efficient bit-wise operations, reducing ciphertext noise management overhead but increasing communication rounds between MPC servers.
- Optimal Hybrid: Typically places the first few linear layers in HE to compress input dimensionality before the MPC switch.
Adversarial Model & Trust Assumptions
Security depends on the non-collusion of distinct parties.
- Honest-Majority MPC: Assumes a majority of MPC servers follow the protocol, enabling high-throughput secret-sharing schemes.
- Dishonest-Majority MPC: Tolerates arbitrary corruption but incurs higher overhead; often used when the model owner operates all MPC nodes.
- HE Assumption: Relies solely on the hardness of lattice problems (e.g., RLWE), independent of the MPC trust model.
Protocol Instantiations
Real-world implementations combine specific schemes.
- Gazelle (CKKS + GMW): Uses packed CKKS for linear layers and a custom GMW-based MPC protocol for ReLU and MaxPool, optimizing for low-latency CNN inference.
- Delphi (TFHE + ABY): Employs TFHE for initial layers and switches to the ABY framework for mixed arithmetic, boolean, and Yao-based MPC.
- CHET (CKKS + ABY): A compiler framework that automatically partitions TensorFlow models between CKKS and ABY, optimizing the cut point for minimal latency.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about combining Multi-Party Computation and Homomorphic Encryption for privacy-preserving machine learning inference.
A Hybrid MPC-HE Protocol is a cryptographic design pattern that strategically combines Multi-Party Computation (MPC) and Homomorphic Encryption (HE) to execute privacy-preserving computations more efficiently than either primitive alone. The core mechanism leverages a fundamental performance asymmetry: HE is highly efficient for linear operations like matrix multiplications and convolutions, while MPC excels at non-linear operations like ReLU, MaxPool, and division. In a typical hybrid protocol, the model owner encrypts the model weights and sends them to compute parties. The input data owner encrypts their data using HE. The compute parties then perform the linear layers of a neural network directly on the ciphertext using HE's SIMD arithmetic. When a non-linear activation function is encountered, the protocol switches to an MPC phase—often using secret sharing and lookup tables—to evaluate the function. The result is re-encrypted into HE ciphertext for the next linear layer. This alternating execution avoids the prohibitive latency of evaluating deep non-linear circuits in pure HE while eliminating the high communication overhead of performing large matrix multiplications in pure MPC. The protocol's security guarantees hold as long as the underlying HE scheme (typically CKKS or TFHE) and the MPC protocol (often based on replicated secret sharing) remain secure against the defined adversary model.
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
The Hybrid MPC-HE Protocol is a composite architecture. Understanding its individual components and adjacent privacy-preserving techniques is essential for evaluating its security and performance trade-offs.
Multi-Party Computation (MPC)
A cryptographic protocol enabling multiple parties to jointly compute a function over their private inputs without revealing those inputs to each other. In a hybrid context, MPC handles non-linear operations (like ReLU or MaxPool) that are computationally expensive in pure HE.
- Secret Sharing: Inputs are split into random shares distributed among computing parties.
- Garbled Circuits: A two-party protocol where a function is represented as a boolean circuit and evaluated without revealing inputs.
- Security Guarantee: Provides information-theoretic or computational security depending on the adversary model (honest-majority vs. dishonest-majority).
Fully Homomorphic Encryption (FHE)
A cryptographic scheme enabling arbitrary computation directly on encrypted data. In the hybrid protocol, FHE handles the linear layers (matrix multiplications, convolutions) where its Single Instruction Multiple Data (SIMD) packing excels.
- CKKS Scheme: Optimized for approximate arithmetic on real numbers, ideal for neural network weights and activations.
- Noise Budget: Ciphertexts accumulate error with each operation; bootstrapping refreshes this budget.
- Computational Cost: Linear operations are fast, but non-linear functions require expensive polynomial approximations.
Garbled Circuits
A two-party MPC protocol where a function is represented as a boolean circuit. The circuit generator 'garbles' each gate by encrypting its truth table, and the evaluator decrypts only the path corresponding to their inputs.
- Constant Round Complexity: Requires a fixed number of communication rounds regardless of circuit depth.
- Non-Linear Efficiency: Excels at evaluating comparison, bitwise operations, and activation functions.
- Hybrid Role: Often used in the MPC portion of hybrid protocols to evaluate non-linear layers that are inefficient in FHE.
Threshold FHE
A multi-key variant of homomorphic encryption requiring a threshold of parties to collaborate during decryption. This prevents any single entity from unilaterally accessing the plaintext result.
- Distributed Decryption: Each party holds a share of the secret key and produces a partial decryption.
- Hybrid Synergy: Combines the output privacy of FHE with the access control of MPC.
- Use Case: Enables scenarios where a model owner and data owner jointly decrypt inference results without either gaining full access.

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