In Data Vault modeling, a hub refers to a specific type of table that stores the unique business key for a core business concept, such as a customer, account, or product. Hubs are intentionally simple structures—they contain only the business key, a surrogate key, and minimal metadata like the load timestamp and source system. They do not include descriptive attributes or transactional data. Those details are stored in related satellite tables, while relationships between different business keys are captured in separate link tables. The purpose of a hub in Data Vault is to provide a consistent, scalable, and audit-friendly anchor point for integrating and tracking core entities across different systems. Because hubs store only the identifying keys, they remain stable over time and support historical tracking and modular growth across the data warehouse.
More broadly, outside of Data Vault, the term hub is sometimes used informally in data architecture to describe a central integration point or system of record. In this general sense, a hub is a centralized platform or repository that acts as the core for managing models, metadata, and collaboration across teams. It brings together technical and business perspectives into a unified environment, helping organizations ensure consistency, avoid duplication, and support governed access to shared data definitions. This usage of “hub” doesn’t refer to a table structure, but rather a functional role in enterprise data management—something that acts as the nexus of collaboration, standardization, and oversight.
ER/Studio supports both interpretations of a hub. In the context of Data Vault modeling, ER/Studio enables the creation of hub tables within logical and physical models, ensuring that business keys are clearly defined and separated from descriptive data. With the 20.6 release, ER/Studio introduced automation features—including wizards and macros—that help teams design Raw Vault components like hubs, links, and satellites more efficiently, directly from business-aligned models. This enforces best practices while reducing manual effort.
In the broader, architectural sense, ER/Studio acts as a hub for enterprise data modeling and metadata management. The ER/Studio Repository provides a centralized environment where multiple users can collaborate on shared models, track changes, and manage versions. Team Server extends this by offering a web-based interface for accessing business glossaries, viewing models, and navigating metadata across the organization. Together, these tools position ER/Studio as a central hub for aligning data architecture with business needs—supporting consistency, collaboration, and governance across the enterprise data landscape.
