The Hub-and-Spoke Instance Architecture Pattern enables large enterprises to manage multiple ServiceNow instances across different business units, regions, or subsidiaries while maintaining centralized oversight and governance. In this pattern, spoke instances handle local operations and data specific to their business units, while a central hub instance aggregates critical data, provides enterprise-wide reporting, and enforces standardized processes.

This pattern solves the challenge of balancing local autonomy with enterprise governance. Business units get the flexibility to customize their ServiceNow instances for local needs while the enterprise maintains visibility into cross-organizational metrics, compliance, and strategic initiatives. The hub instance typically contains master data like employee records, organizational hierarchies, and standardized catalogs that get synchronized to spokes.

Data flows bidirectionally between hub and spokes through REST APIs, scheduled imports, or real-time integrations. The hub aggregates incident volumes, service metrics, and compliance data from all spokes, while pushing out policy updates, catalog items, and organizational changes to maintain consistency across the enterprise.