IN BRIEF
Cloud 3.0 describes the step from "cloud first" to a deliberately designed mix of own data centre, sovereign cloud, public cloud and edge, in which each workload is placed according to clear criteria. A cloud strategy defines those criteria and connects them with the platform, operating model and cost management.
When to involve us.
When cloud use has grown over the years, costs are hard to attribute, or data sovereignty and resilience requirements call a cloud-first policy into question, placement decisions need a new foundation.
We assess your workloads by criticality, data sovereignty, cost and energy demand and derive a target location for each. Placement is aligned with the target architecture from enterprise architecture management, so cloud decisions are not made apart from the rest of the landscape. For operations, we define the shared platform, FinOps accountability and standards your teams need.
What the work produces.
We agree on the scope around your goals, starting point and available capacity. The following elements illustrate what an engagement can include.
WHAT WE ADDRESS
- Cloud strategy and placement criteria
- Workload assessment and target platform recommendations
- FinOps model and cost accountability
- Platform design and cloud operating model
POTENTIAL OUTPUTS
A basis for workload placement decisions, a platform design and an operating model with clear cost accountability. These help you plan migration and platform development and assess the effort involved.
A focused starting point.
An overview of your applications and where they run today, current cloud invoices and existing contracts. Owners from architecture, operations, information security and finance should take part in the assessment.
The question first. Then the scope.
The first conversation clarifies the objective, deliverables and people involved. We agree whether the engagement covers design, pilot support or technical implementation, who takes on each task and how the deliverables will be assessed.
Discuss a starting point by emailShould we move applications back out of the public cloud?
This can only be answered workload by workload, not across the board. Moving back can make sense when an application has steady utilisation, moves large volumes of data or faces strict data sovereignty requirements. Applications with highly variable load or heavy use of managed services, on the other hand, often continue to benefit from the public cloud. A fair comparison includes not only running costs but also migration effort, staffing, operational risk and available capacity in your own data centre. It often pays to look first at cost management in your existing cloud, such as unused resources and suitable pricing models. Repatriation should be the result of an assessment, not its starting point.
Last updated: