Riyadh · Karachi · Delaware soon 07:00 – 15:00 UTC  ·  contact@coalescence.me

Solutions

Cloud & Infrastructure Services

Cloud architecture, migration and managed operations for regulated organisations.

Platforms
Azure and AWS
Residency
In-country regions where required
Handover
IaC repository you own

The approach

Establish the controls, then move the workloads.

We establish account topology, network boundaries and cost allocation before workloads are migrated. Defining these controls at the start keeps residency obligations verifiable and makes monthly cloud expenditure attributable to the teams that generate it.

Microsoft AzureAWSTerraformBicepKubernetesDockerAzure DevOpsGitHub ActionsEntra IDCloudflareGrafanaAzure Monitor
landing zone — controls
2Hyperscalers
100%In-region
24/7Managed

Capabilities

What the practice covers

  1. 01

    Landing zones

    Subscription and account structure, network segmentation, identity design and policy guardrails, implemented before workload migration begins.

  2. 02

    Migration

    Assessment, wave planning and cutover for on-premises estates, including legacy systems with limited documentation or restart history.

  3. 03

    Infrastructure as code

    Terraform and Bicep modules that make environments reproducible and surface configuration drift during the build rather than during an incident.

  4. 04

    Data residency

    The residency obligations that apply to you mapped to the appropriate regions and controls, with supporting evidence prepared for audit. Where a regime carries a deadline, as the UAE PDPL executive regulations do, the work is sequenced against it.

  5. 05

    Managed operations

    Monitoring, patching, backup verification and incident response against contractually agreed response windows.

  6. 06

    Cost engineering

    Right-sizing, reservation strategy and per-team showback reporting, with monthly expenditure attributable line by line.

On handover

What you receive

Every engagement ends with the client holding the artefacts needed to run, extend and re-tender the system without us.

  • Target architecture with documented rationale for each significant decision
  • Infrastructure-as-code repository under your ownership
  • Disaster recovery plan validated by a tested restore
  • Cost baseline, showback model and monthly review cadence

Common questions

Frequently asked

Can our data remain inside our own country?
Where a hyperscaler operates an in-country region, yes. We apply the residency boundary to backups, log shipping and disaster-recovery copies in addition to the primary workload, which is where residency most often fails.
What does UAE PDPL require of our cloud architecture?
Federal Decree-Law No. 45 of 2021 does not mandate in-country hosting for all personal data. Cross-border transfer requires an adequacy decision or appropriate safeguards such as standard contractual clauses. Sector rules are stricter: UAE Central Bank standards require customer and transaction data to remain in country.
Do you assume responsibility for an existing cloud estate?
Yes. Transition begins with a security and cost audit, followed by remediation of the highest-risk findings before any architectural change.
What is covered by managed support?
Monitoring, patching, backup verification, incident response and monthly reporting. Scope, escalation paths and response times are defined in the service agreement.

Begin with a two-week discovery

Discovery produces a domain model, a risk register and a written estimate, retained by the client regardless of whether the build proceeds.