Cloud capacity baseline
2–3 weeks
Model the workload, current estate and commercial options before making a longer commitment.
All services
Estma service / Cloud capacity
Cloud capacity programmes
Turn forecast compute, GPU, storage and managed-service demand into an annual cloud capacity plan, then provision, monitor and optimise the environment around it.
Where this starts
A good fit when…
- A growing product needs a predictable annual cloud or AI infrastructure budget
- GPU, general compute, storage or managed database demand is expected to increase
- A team needs to establish cloud resources without building a full platform function
- Existing cloud commitments need stronger monitoring, allocation or FinOps discipline
The operating problem
The difficult part is rarely the headline technology.
The engagement focuses on the surrounding system: boundaries, evidence, permissions, exceptions, people and the decisions the implementation must support.
- 01
A commercial commitment is made before the workload and architecture are understood
- 02
Compute, storage, networking and managed-service costs have different growth drivers
- 03
Resources are provisioned without budgets, alerts, ownership or environment boundaries
- 04
Capacity planning ignores deployment, reliability, security and recovery requirements
What leaves the engagement
Concrete output, not advisory residue.
- 01Workload architecture and base, growth and peak demand model
- 02Capacity plan across compute, GPU, storage, databases, networking and AI services
- 03Provider-aligned procurement and resource provisioning support
- 04Environment, identity, budget, quota and tagging controls
- 05Monitoring, alerting, backup and cost-allocation baseline
- 06FinOps review cadence, optimisation backlog and renewal decision record
Ways to start
Choose the smallest engagement that resolves the next decision.
Provision and control
3–6 weeks
Establish the agreed resources, environments, access, monitoring, budgets and operating documentation.
Annual capacity programme
12 months
Combine agreed cloud capacity with usage review, allocation, optimisation and operating support through the term.
What Estma needs from your team.
- Current cloud bills or a forecast workload
- Application architecture and environment requirements
- Security, region, availability and recovery constraints
- A technical and commercial owner for capacity decisions
Inside the work
See the decisions behind the service.
Representative engagements show how this capability connects to the product, workflow, controls, and people around it.
Service questions
What teams usually ask.
What resources can a programme cover?
Depending on the agreed provider and scope, it can include general or GPU compute, object and block storage, managed databases and vector search, containers, serverless services, networking, CDN and cloud AI services.
Do you only work with one cloud provider?
No. The provider and commercial structure should follow the workload, existing estate, regional availability and support requirements. Any final offer states the specific provider, resources, term and exclusions.
Start with context
Is this the work you need?
Describe the current system, the decision ahead and the constraint that is making progress difficult.