Capability: Cloud & Infrastructure
Sovereign cloud for the workloads you cannot move abroad.
Private, hybrid and in-Kingdom cloud with residency by design — together with the datacenter, network and migration engineering that makes it real.
- In-Kingdom residency
- Private & hybrid cloud
- Datacenter engineering
- Migration waves
What we build
Design and build engagements with a defined end state — scoped by workload, not by headcount.
Sovereign private cloud
Virtualised and software-defined private cloud in your own facility or a Saudi datacenter, with tenancy, quotas and residency boundaries agreed before the first rack is racked.
Datacenter & network foundations
Rack, power and cooling planning; structured network, segmentation, routing and out-of-band access — designed and documented to the standard an auditor expects.
Migration & modernisation
Application dependency mapping, wave planning, rehearsed cutovers and a rollback path for every workload that is not allowed to fail.
Resilience & continuity engineering
Disaster-recovery topology, recovery objectives agreed with the business, backup architecture and failover procedures that have actually been tested.
How we engage
Assess, design, migrate, verify.
- Phase 01
Assess & map
Inventory, dependency discovery, residency and regulatory constraints, and an honest read on what should not move at all.
- Phase 02
Design & cost
Target architecture, tenancy and network model, DR topology, bill of materials and a wave plan with a price against each wave.
- Phase 03
Build & migrate
Platform build, wave-by-wave migration, rehearsal of every cutover and a rollback that is proven before go-live.
- Phase 04
Verify & hand over
DR test, performance validation, as-built documentation and enablement for the team that will run it.
Workloads and backups stay in the Kingdom, with documentation that proves it.
Recovery objectives are engineered and tested, not assumed in a policy document.
Migration waves are planned around your business calendar, not against it.
What you receive
- Current-state assessment and application dependency map
- Target architecture, tenancy and network segmentation model
- Costed migration plan, wave by wave, with rollback criteria
- Disaster-recovery design and tested failover runbooks
- Datacenter, power and network documentation pack
- As-built records and enablement for your operations team
How it maps to the frameworks
- NCA ECC-2:2024
- Asset management, network security, cryptography, backup and resilience control domains.
- CITC cloud framework
- Workload classification and hosting obligations reflected in the target design.
- SAMA CSF
- Resilience, recovery and change requirements for financial-sector estates.
- PDPL
- Residency and cross-border transfer constraints written into the architecture.
Why Next Step for cloud
One design authority
Compute, network, storage and security decided by one team, so the seams between them are nobody else's problem to discover.
Vendor-neutral, partner-deep
Direct partner status with the platform vendors, and no obligation to land any of them where they do not fit.
Documented to audit standard
The pack you get at handover is the pack your assessor asks for — diagrams, configurations, decisions and their reasons.
Let us cost the move properly.
Send us the estate — applications, dependencies, constraints. You get a target architecture and a migration plan priced by wave.