A feature space is the complete set of dimensions or variables used to represent each data sample in a machine learning problem, formally defined as the vector space spanned by all input features. In Vertical Federated Learning (VFL), the global feature space is partitioned, meaning different subsets of features (columns) for the same entities are held by distinct feature owners. The model's task is to learn patterns across this distributed, collective space without centralizing the raw data.
Glossary
Feature Space

What is Feature Space?
In machine learning, the feature space is the mathematical domain defined by all input variables used to describe the data. In Vertical Federated Learning (VFL), this space is partitioned and distributed.
The structure of the partitioned feature space directly dictates the VFL system architecture. Each owner computes on its local subspace, and the model must securely integrate these partial views, often via a split neural network. Managing this distributed feature space introduces core challenges: aligning entities across parties, minimizing vertical communication overhead from sharing intermediate results, and applying vertical secure aggregation to protect each owner's feature contributions during training.
Key Characteristics of Feature Space
In Vertical Federated Learning (VFL), the feature space is the complete set of input variables describing the entities, but it is uniquely partitioned and distributed across multiple, non-collaborating data owners.
Distributed Ownership
The defining characteristic in VFL is that the complete feature space is not held by a single entity. Instead, different features (columns) for the same set of entities (rows) are owned by different parties.
- Example: A bank holds a customer's credit history (features: credit score, loan history), while an e-commerce platform holds their purchase behavior (features: avg. cart value, product categories).
- Implication: No single party has a complete feature vector for any entity, making centralized training impossible and necessitating collaborative protocols.
High-Dimensional & Sparse
The aggregate feature space across all parties is often extremely high-dimensional, as it combines attributes from diverse domains. However, the local feature space held by any single party is a lower-dimensional, dense subset.
- This creates a global sparsity pattern: for any given sample, most feature values are zero from the perspective of a single owner, because they belong to other parties.
- Engineering Challenge: Protocols must efficiently handle operations on these conceptually complete but physically distributed high-dimensional vectors.
Statistically Heterogeneous
The feature distributions held by different owners are inherently non-Identically Distributed (non-IID). Each party's local feature subspace comes from a different data generating process and operational context.
- Example: Hospital medical images (pixel data) vs. pharmacy prescription records (categorical codes). Their statistical properties (mean, variance, modality) are entirely different.
- Consequence: Standard federated averaging (FedAvg) from horizontal FL fails. VFL requires specialized optimization that accounts for this cross-silo feature heterogeneity.
Requires Secure Alignment
For VFL to function, the distributed feature spaces must be aligned sample-wise. Parties must identify which of their local records correspond to the same real-world entity (e.g., the same customer) without exposing their full datasets.
- This is solved using cryptographic protocols like Private Set Intersection (PSI) for entity alignment.
- Critical Precondition: The aligned intersection set defines the effective training dataset. Its size and quality directly limit model performance.
Defines the Split Model Architecture
The partitioned nature of the feature space dictates the split neural network architecture used in VFL. The model is divided at a cut layer, with each party hosting a bottom model that processes its local features.
- Forward Pass: Each party computes an intermediate output (embedding) from its local features. These are sent to a coordinator (often the label owner) to compute the top model and final prediction.
- Architectural Constraint: The split must be designed considering feature semantics, privacy leakage from intermediates, and communication costs.
Primary Source of Communication Overhead
In VFL, the feature space partition is the root cause of communication overhead. Unlike horizontal FL where entire model weights are exchanged, VFL requires transmitting intermediate outputs and gradients for every sample in every training batch.
- Bandwidth Cost: Scales with batch size * embedding dimension * number of rounds, not model size.
- Optimization Focus: A major research area is designing communication-efficient VFL protocols using compression, selective synchronization, and in-network computation.
Role in Vertical Federated Learning
In Vertical Federated Learning (VFL), the feature space is not a unified whole but a partitioned resource. This entry defines its critical role as the distributed input domain that enables collaborative model training without data centralization.
In Vertical Federated Learning (VFL), the feature space is the complete set of input variables used to describe a shared set of entities, which is partitioned and distributed across multiple data-owning parties. Unlike centralized machine learning, no single party holds the full feature vector for any entity. This partitioned structure is the foundational data architecture that VFL protocols are designed to operate on, enabling collaborative model training while keeping raw feature data decentralized and private.
The role of the feature space dictates the core computational and communication patterns of VFL. Each feature owner computes on its local subset of the space, producing intermediate outputs that are securely aggregated or passed to a label owner. The collective, yet partitioned, feature space is what the federated model learns from, making secure entity alignment and private set intersection (PSI) prerequisite steps to ensure all parties are referring to the same entities across their respective feature subspaces.
Feature Space vs. Related Concepts
A comparison of the Feature Space with other key structural and data concepts in Vertical Federated Learning (VFL).
| Concept | Definition | Primary Role in VFL | Relationship to Feature Space |
|---|---|---|---|
Feature Space | The complete set of input variables or attributes used to describe the entities in a dataset. | The total set of predictive signals, which is partitioned and distributed across multiple data owners (feature owners). | This is the core concept being defined. All other concepts relate to how this space is partitioned, owned, or utilized. |
Vertical Data Partition | A dataset split where different features (columns) of the same samples (rows) are held by different parties. | The foundational data structure that creates the distributed feature space across participants. | Describes the physical and logical distribution of the feature space across owners. |
Label Space | The set of possible output values or target variables for the aligned entities. | Typically held by a single label owner; defines the supervised learning objective for the collaborative model. | The label space is the target for predictions made using the combined, distributed feature space. |
Entity Alignment | The process of identifying matching records (entities) across the vertically partitioned datasets held by different parties. | A prerequisite step to ensure all parties are computing on the same set of samples before training begins. | Aligns the rows so that the distributed feature space and label space refer to the same entities. |
Feature Owner | A participant in a VFL system that possesses a specific subset of the features for the aligned entities. | Holds and computes on a segment of the overall feature space. Responsible for its local model part and data privacy. | An actor that controls a partition of the total feature space. |
Split Neural Network | A model architecture divided into multiple parts, with each part residing on a different party (e.g., feature owners and label owner). | The computational embodiment of the distributed feature space, where each party's model segment processes its local features. | The model's architecture is explicitly designed to operate over the partitioned feature space. |
Frequently Asked Questions
In Vertical Federated Learning (VFL), the feature space is a foundational concept describing the complete set of input variables used to describe entities. It is uniquely partitioned and distributed across multiple data owners.
In machine learning, a feature space is the multi-dimensional mathematical space defined by the complete set of input variables or features used to represent each data sample. Each feature corresponds to one axis (dimension) of this space, and each data sample is represented as a single point, or vector, within it. The structure of this space is critical for algorithms to learn patterns; operations like classification involve finding decision boundaries that separate different clusters of points. The dimensionality of the feature space is equal to the number of features, and techniques like dimensionality reduction (e.g., PCA) are often used to project data into a lower-dimensional space for visualization and computational efficiency.
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
In Vertical Federated Learning (VFL), the feature space—the complete set of input variables—is partitioned across multiple data owners. These related terms define the core components and protocols that enable collaborative training on this distributed data.
Vertical Data Partition
A vertical data partition is a dataset split where different features (columns) pertaining to the same set of entities (rows) are held by different, non-overlapping parties. This structure is the foundational data assumption for VFL.
- Key Distinction: Contrasts with horizontal partitioning, where different parties hold different rows (samples) with the same features.
- Example: In a financial-medical collaboration, Bank A holds a customer's transaction history (features), while Hospital B holds the same customer's diagnostic codes (different features).
Entity Alignment
Entity alignment is the privacy-preserving process of identifying the overlapping set of entities (e.g., users, devices) across the vertically partitioned datasets held by different parties. It is a critical prerequisite for VFL, as training can only occur on the aligned samples.
- Core Challenge: Must be performed without revealing the full list of entities from any party.
- Primary Tool: Typically achieved using cryptographic protocols like Private Set Intersection (PSI).
Split Neural Network
A split neural network is the standard model architecture for VFL, where the neural network is divided into multiple segments. Each segment resides on a different party that holds the corresponding subset of the total features.
- Typical Setup: Feature owners hold the bottom models (initial layers) that process their local features. A label owner holds the top model (later layers) that consumes combined intermediate outputs to produce a prediction.
- Cut Layer: The specific layer where the model is split, defining the boundary of computation and communication.
Vertical Training Protocol
A vertical training protocol defines the exact sequence of secure communication and computation steps that coordinating parties follow to execute a single training round in a VFL system.
- Standard Steps: 1) Feature owners compute forward passes to a cut layer. 2) They send encrypted intermediate outputs to the label owner. 3) The label owner completes the forward pass, computes loss, and backpropagates gradients. 4) Relevant gradients are sent back to feature owners for their local model updates.
- Governs: The flow of data, encryption methods, and aggregation routines.
Secure Aggregation (Vertical)
Vertical secure aggregation refers to cryptographic protocols used to combine model updates (e.g., gradients or intermediate outputs) from multiple feature owners without revealing any single party's contribution. This protects against privacy leakage and inference attacks.
- Mechanisms: Often employs Secure Multi-Party Computation (MPC) or Homomorphic Encryption (HE).
- Purpose: Ensures the label owner (or aggregator) only sees the summed update, not individual data.
Communication Overhead
Vertical communication overhead is the significant bandwidth cost and latency introduced by the need to exchange intermediate outputs and gradients between parties during every forward and backward pass of training. This is a primary systems challenge in VFL.
- Scalability Bottleneck: Overhead grows with the number of aligned samples, the dimensionality of the cut layer, and the training frequency.
- Optimization Focus: Drives research into communication compression, selective participant updates, and efficient cryptographic protocols.

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