Your workloads. A considered cloud.
Bring your applications, dependencies and operating requirements. Build a hosting plan with clear capacity, access, support and recovery responsibilities.
Six layers, one hosting plan.
Select a layer to review the decisions that belong in your hosting plan.
Workload placement and benchmarks
Review workload demand, tenancy needs and available hardware. Benchmark representative applications before committing capacity.
Planning topics; included capabilities and responsibilities must be agreed in the service proposal.
Define the service you need.
Turn workload requirements into an agreed scope and measurable acceptance checks.
Workload placement
Define capacity and tenancy requirements in your proposal.
Storage and keys
Agree capacity, performance targets, encryption and key responsibilities.
Network boundaries
Map permitted connections, administrative access and dependencies.
Runtime fit
Review application dependencies and operational responsibilities.
Operational evidence
Specify event coverage, retention, access and alert ownership.
Service scope
Agree bandwidth, support, backup and change costs in writing.
Compare the whole cost before you leave shared tenancy.
| Review your current estate | Define the proposed scope |
|---|---|
| Current compute and peak demand | Proposed capacity, tenancy and workload benchmarks |
| Transfer and connectivity charges | Allowances, overage terms and dependencies |
| Encryption and key management | Required controls, custody and recovery procedures |
| Logging and retention costs | Agreed coverage, retention and response ownership |
| Application and provider dependencies | Migration effort, portability limits and exit plan |
What private cloud looks like for your industry.
Healthcare
Review data boundaries, access, retention and agreement requirements before handling sensitive workloads.
Finance & tax
Plan seasonal capacity, access, retention and applicable data requirements.
AI startups
Review model workloads, available capacity, data boundaries and benchmarks.
Private cloud, asked + answered.
Compute, storage, connectivity, operations, access and recovery responsibilities, with inclusions and dependencies clearly identified.
Capacity and the agreed service scope determine pricing. Confirm bandwidth, licensing, support, backup, migration and contract terms in the written proposal.
Start with application dependencies and acceptable data loss and downtime. Agree recovery objectives and test restores or failover before relying on the design.
Review connectivity, identity, latency, licensing and transfer requirements for each retained service before implementation.
Document export formats, dependencies, transfer costs, access and deletion responsibilities. Agree the process and notice period before starting service.
Get a TCO comparison against your current cloud.
Start with workload goals and a summary of current costs. Agree a secure exchange method before sharing detailed billing or sensitive information.