technooloo®Cloud TOM Studio
Talk to an expert

Explore Cloud TOM Studio

Cloud TOM Studio · by Technooloo

Your cloud operating model.
A clearer starting point.

Who owns the decision? Who delivers the service? Where does the handoff happen? Start with practical diagrams and guides, then make the model yours.

Browse 12 diagrams Get the starter model
Free to exploreEditable downloadsNo account needed
Inside the libraryBuild → run
Cloud Build-to-Run Handover previewevidencecontrol evidenceacceptance packconditionsrelease decisionoperational findingsprioritized changePlatform Engineering: Build and testPlatform EngineeringBuild and testReadiness evidence: Runbook, SLOs, recoveryReadiness evidenceRunbook, SLOs, recoverySecurity assurance: Control validationSecurity assuranceControl validationService owner: Release accountabilityService ownerRelease accountabilityCloud Operations: Operational acceptanceCloud OperationsOperational acceptanceImprovement backlog: Learning and remediationImprovement backlogLearning and remediation
A better handoff starts here.Explore roles, readiness and acceptance.

Find a diagram

Editable models for your next working session.

Clarify responsibilities

22 functions, their mandates and handoffs.

Work through a guide

Practical steps for cloud operating-model decisions.

The open library

A useful model.
Ready for your next conversation.

Explore all diagrams
6 diagrams
Generic Cloud Infrastructure Operating Model previewqualifyrouterequirementsdirectionaccepttriggereconomicsexecuteperformanceProduct & application teams: Demand and business outcomesProduct & application teamsDemand and business outcomesCloud Governance / CCoE: Governance routingCloud Governance / CCoEGovernance routingCloud Service Management: Service lifecycleCloud Service ManagementService lifecycleCloud Architecture: Technical directionCloud ArchitectureTechnical directionPlatform Engineering: Reusable productsPlatform EngineeringReusable productsCloud Operations: Run and improveCloud OperationsRun and improveSecurity & Assurance: Risk and control authoritySecurity & AssuranceRisk and control authorityFinOps: Economics and actionFinOpsEconomics and actionMSP / technology providers: Delegated executionMSP / technology providersDelegated execution
Operating models · 2026.1

Generic Cloud Infrastructure Operating Model

A vendor-neutral demand-to-operations view with governance, assurance, economics and provider boundaries.

Explore Draw.io
Cloud CCoE Function Map previewrouteroutecoordinateenablemeasureCloud Governance / CCoE: Operating model and orchestrationCloud Governance / CCoEOperating model and orchestrationCloud Architecture: Architecture authorityCloud ArchitectureArchitecture authoritySecurity & Assurance: Risk authoritySecurity & AssuranceRisk authorityService Management: Service ownershipService ManagementService ownershipPlatform Engineering: Delivery executionPlatform EngineeringDelivery executionFinOps: EconomicsFinOpsEconomics
Functions · 2026.1

Cloud CCoE Function Map

A clear boundary between governance orchestration, specialist authority and delivery execution.

Explore Draw.io
Cloud Governance Interaction Model previewrequestrefershape serviceconditionsrequirementshandoverevidenceDemand intake: Qualified needDemand intakeQualified needGovernance: Route and coordinateGovernanceRoute and coordinateSpecialist authority: Decision and conditionsSpecialist authorityDecision and conditionsService ownership: Service lifecycleService ownershipService lifecyclePlatform delivery: Build and evidencePlatform deliveryBuild and evidenceOperations: Accept and operateOperationsAccept and operate
Interactions · 2026.1

Cloud Governance Interaction Model

A bounded interaction flow from demand through specialist decisions into delivery and run.

Explore Draw.io
Cloud Platform Operating Model previewneedsprioritiesdirectionroadmaphandoverservice levelscapabilityfeedbackProduct teams: Consume paved roadsProduct teamsConsume paved roadsPlatform product management: Outcomes and roadmapPlatform product managementOutcomes and roadmapCloud Architecture: Patterns and constraintsCloud ArchitecturePatterns and constraintsPlatform Engineering: Build reusable capabilitiesPlatform EngineeringBuild reusable capabilitiesService Ownership: Catalogue and lifecycleService OwnershipCatalogue and lifecycleCloud Operations: Run and improveCloud OperationsRun and improveTechnology providers: Products and supportTechnology providersProducts and support
Operating models · 2026.1

Cloud Platform Operating Model

A platform-product lifecycle connecting consumers, architecture, engineering, service ownership and operations.

Explore Draw.io
Internal Team vs MSP Responsibility Model previewdelegatessets constraintssets conditionsreportsperformanceretained oversightInternal service owner: Outcome accountabilityInternal service ownerOutcome accountabilityInternal architecture authority: Technical decisionsInternal architecture authorityTechnical decisionsInternal risk authority: Risk acceptanceInternal risk authorityRisk acceptanceVendor management: Performance and escalationVendor managementPerformance and escalationManaged service provider: Delegated build / run executionManaged service providerDelegated build / run executionProvider evidence: Performance, controls, actionsProvider evidencePerformance, controls, actions
Sourcing · 2026.1

Internal Team vs MSP Responsibility Model

A retained-organization view that separates internal accountability from delegated provider execution.

Explore Draw.io
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
Operating models · 2026.1

Federated Cloud Governance Model

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

Explore Draw.io
Make it your own

From a reference pattern
to a working conversation.

Every diagram includes context, assumptions and editable source. Use it as a starting point, then validate it with the people who own the work.

Read our approach
  1. 01

    Find your starting point

    Choose a model for governance, sourcing, service ownership or delivery.

  2. 02

    Explore and adapt

    Inspect the relationships. Rename or hide objects in the browser.

  3. 03

    Take it into the room

    Download editable Draw.io source or a ready-to-use image.

From reference to reality

Make the model work for your organization.

Work directly with Technooloo experts to clarify ownership, challenge the design and turn it into a practical next step.

Discuss your cloud challenge