operating model · version 2026.1

Federated Cloud Governance Model

A hub-and-spoke pattern that separates enterprise guardrails from business-domain ownership and platform execution.

Federated Cloud Governance Model. A hub-and-spoke pattern that separates enterprise guardrails from business-domain ownership and platform execution.
PNG preview2400 × 1003 px27 KBVersion 2026.1 · reviewed 2026-09-08
Explore semantic layers
Federated Cloud Governance Model previewdelegates guardrailsdelegates standardssets economicssets sourcingconditionspatternsunit economicsevidenceevidenceevidenceEnterprise cloud governance: Guardrails and portfolioEnterprise cloud governanceGuardrails and portfolioSecurity authority: Control requirementsSecurity authorityControl requirementsArchitecture authority: Reference patternsArchitecture authorityReference patternsFinOps: Economics and allocationFinOpsEconomics and allocationVendor management: Commercial governanceVendor managementCommercial governanceDomain platform A: Domain-owned outcomesDomain platform ADomain-owned outcomesDomain platform B: Domain-owned outcomesDomain platform BDomain-owned outcomesDomain platform C: Domain-owned outcomesDomain platform CDomain-owned outcomes
Accessible diagram transcript

Objects

  • Enterprise cloud governance: Guardrails and portfolio (Governance)
  • Security authority: Control requirements (Authorities)
  • Architecture authority: Reference patterns (Authorities)
  • FinOps: Economics and allocation (Governance)
  • Vendor management: Commercial governance (Governance)
  • Domain platform A: Domain-owned outcomes (Engineering)
  • Domain platform B: Domain-owned outcomes (Engineering)
  • Domain platform C: Domain-owned outcomes (Engineering)

Directed relationships

  • enterprisesecurity: delegates guardrails (authority)
  • enterprisearchitecture: delegates standards (authority)
  • enterprisefinops: sets economics (handoff)
  • enterprisevendor: sets sourcing (handoff)
  • securitydomain-a: conditions (authority)
  • architecturedomain-b: patterns (authority)
  • finopsdomain-c: unit economics (handoff)
  • domain-aenterprise: evidence (feedback)
  • domain-benterprise: evidence (feedback)
  • domain-centerprise: evidence (feedback)
01

When to use it

Use when several business units need autonomy without fragmenting policy, architecture and control evidence.

02

What to challenge

  • Separate accountable authority from delivery execution.
  • Make every important handoff directional and reviewable.
  • Treat this reference pattern as a starting point, not a prescription.
03

Adapt it responsibly

  1. Rename functions to match the organization vocabulary.
  2. Remove elements that are genuinely out of scope.
  3. Validate decision rights and handoffs with accountable stakeholders.
04

Model contents

8 objects and 10 directed relationships. Every object keeps a stable semantic ID.

One model, multiple representations

The browser view and editable file are generated from the same canonical graph, so labels, roles and relationship direction stay aligned.

Clear visual grammar

Shape, color and connector style distinguish actors, governance, authorities, services, engineering, operations and providers.

Make this model your own.

Rename objects, adjust the scope and download an editable version. Your changes stay in this browser; no account is required.

Customize this diagram