Scale · Cloud services
Cloud consulting and architecture, with the cost model first.
Cloud consulting and architecture for Indian enterprises deciding what to move to the cloud, or asking why the bill is higher than planned. NetScale inventories the workloads, builds a cost model for each and designs the landing zone, network and identity around measured use. The strategy and design are written down and handed over as yours.
- Last updated
What it is
Cloud Consulting
Cloud consulting decides what moves to the cloud, what stays and what retires, with a cost model per workload, before anything is migrated.
Cloud architecture is the design those workloads land in: the landing zone, network, identity and subscriptions. We size it from measured use, not from the hardware it replaces.
Multi-cloud planning decides whether a second provider earns its cost, and which workloads would run there. The recommendation comes in writing, and the decision stays yours.
Cutting the bill of an estate already running sits under Managed cloud and cost optimisation.
Moving the workloads once the design is signed off sits under Cloud migration and modernisation.
What it covers
- Cloud strategy
- Cost modelling
- Scalable infrastructure design
- Multi-cloud planning
In this line: Cloud services
- Cloud consulting and architecture
- Cloud migration and modernisation
- Cloud security and compliance
- Managed cloud and cost optimisation
- KloudMate observability
Sound familiar?
- 01
Cloud was adopted to cost less than the data centre. The bill says otherwise. What does the business case look like now?
Our answer: Cost modelling
- 02
A second cloud was added for one project. Who decided it was worth running two?
Our answer: Multi-cloud planning
- 03
The cloud estate grew faster than its governance. Who decides what goes where now?
Our answer: Scalable infrastructure design
- 04
The plan is to move everything. Has anyone asked which workloads should stay?
Our answer: Cloud strategy
What we do.
Cloud strategy, cost modelling, scalable infrastructure design and multi-cloud planning.
- 01
Cloud strategy
A decision for each workload to move, stay or retire, ordered by what each system depends on and what the business can carry.
- 02
Cost modelling
Today’s running cost against the cloud cost for each workload, covering compute, storage, licences, data transfer, backup and support, set before the first bill arrives.
- 03
Scalable infrastructure design
Landing zone, network, identity and subscription design, sized from measured use, with room to grow written into the architecture.
- 04
Multi-cloud planning
Where a second provider earns its cost and where it does not, with the connectivity, skills and governance each option needs.
How an engagement runs.
Each phase adds a layer to the same estate.
You can stop at any phase boundary. The assessment is free, and each phase is priced in writing before it starts.How we engage
India specifics and cost.
India specifics
- Data residency
The DPDP Act does not require all personal data to stay in India, but sector rules can. The RBI’s direction of 6 April 2018 requires payment system data to be stored only in India. Legal interpretation stays with your counsel.
Source: RBI direction on storage of payment system data, 6 April 2018 (external site)
- Indian capacity
Where residency applies, the architecture places those workloads in Microsoft Azure’s India regions or in India-based capacity with Yotta. The cost model prices that choice before it is made.
- CERT-In
The Directions of 28 April 2022 require logs of ICT systems to be kept within India for a rolling 180 days. Log storage and retention are part of the cost model.
What drives the cost
- 01
Workload count, and how many need a cost model of their own.
- 02
Usage data: the billing history and measured use available to size from.
- 03
Architecture scope: a landing zone, network and identity, or a multi-cloud plan as well.
- 04
Residency requirements that limit the regions and providers to choose from.
The technology we run for this.
Cloud platform and identity
Data centre and cloud in India
Our own information security and privacy management systems, run under both standards.
Certifications and technologyQuestions buyers ask about this.
Related services
Why is the cloud bill higher than the business case?
Usually for one of three reasons: workloads were sized for the data centre and moved as they were, nobody turned off what was no longer used, or the region was chosen before the cost model. The assessment compares the bill with what you run and lists what to resize, reserve or retire.
Should we run more than one cloud?
It depends on whether a second provider earns its cost. Each extra cloud adds skills, connectivity and governance to run. It suits a workload with a clear reason to be elsewhere, such as a service only one provider offers. The plan sets out each option and its running cost, in writing.
What does a cloud cost model include?
The running cost of each workload today and in the cloud: compute, storage, licences, data transfer, backup and support. It also covers the one-time cost of moving and the effect of reserved capacity. Each figure is tied to measured use, and the model is yours to keep.
What is a cloud landing zone?
A landing zone is the prepared cloud environment that workloads move into: subscriptions, network, identity, security policies and logging, set up before the first workload arrives. Designing it first means each migration lands in the same governed structure, not one built per project. The design is signed off and handed over as yours.
Can you review a cloud strategy we already have?
Yes. The assessment checks an existing strategy against what you run and pay today, and lists where the two differ and what to change. You keep the written findings whether we ever work together or not, and your team can act on them with or without us.
Book a cloud readiness assessment.
It costs nothing and commits you to nothing. You get a written list of where your IT environment is exposed, and your team can act on it with or without us.
What we put in writing
- The written findings are yours whether we ever work together or not.
- Each phase is fixed-scope and signed off separately.
- You can stop at any phase boundary.
- Runbooks, configurations and credentials are yours.