Skip to content

Cloud & DevOps

Ship every day, on infrastructure that costs what it should.

Migration to AWS, Azure or OCI — in the UAE region where residency demands it — infrastructure as code, pipelines that actually gate, and a cloud bill you can explain line by line.

Book a discovery callBuild your plan
  • Dubai head office, GCC-wide delivery
  • Arabic and English throughout
  • Written scope and fixed timeline before you commit

You walk away with

  • Cloud migration
  • Terraform IaC
  • CI/CD pipelines
  • Cost optimisation

Typical timeline

8–16 weeks

Typical engagements start around

AED 25,000 per project

What good looks like

typical first-pass cloud cost reduction
20–35%typical first-pass cloud cost reduction
of infrastructure defined in code
100%of infrastructure defined in code
command to rebuild an environment from scratch
1command to rebuild an environment from scratch

The problem this solves

Cloud spend doubled and nobody can say why. Deploys happen on Thursday nights because that is when it is safe to break things. There is one person who knows how production is wired, and they are on leave. None of this is a tooling problem — it is the absence of infrastructure as code, and the absence of a pipeline anyone trusts.

Where this usually hurts

  • The bill grew and nobody knows why

    Untagged resources, forgotten environments and oversized instances accumulate quietly, and without per-team attribution nobody owns the number.

  • Deploys happen at night

    Releases go out when it is safe to break things, which means rarely, which makes each one bigger and more dangerous than the last.

  • One person knows how it works

    Production was assembled by hand over three years. The map is in someone's head, and they are on leave.

  • Recovery is a document, not a plan

    There is a DR policy. Nobody has ever rebuilt the environment from scratch, so nobody knows whether it would work.

We move workloads to AWS, Azure or Oracle Cloud and leave behind an environment your team can operate without us: every resource defined in Terraform, every deploy running through a pipeline that can block a bad change, and a cost model that attributes spend to the team that caused it. For regulated workloads we build in the UAE regions, so data residency is a configuration fact rather than a promise.

Residency is an architecture decision

AWS me-central-1, Azure UAE North and OCI Dubai all exist, and picking one is straightforward. What is not straightforward is everything around it — logs shipped to a US observability tenant, backups replicating cross-region by default, a support process where an engineer abroad can read production data. We map the whole data path, not just the database's home region.

  • Primary and backup regions chosen explicitly, never left at provider defaults
  • Log, metric and trace destinations reviewed as data flows in their own right
  • Break-glass access logged, time-boxed and reviewed rather than standing
  • A written data-flow map you can hand to a regulator or an enterprise client's security team

Everything as code, including the things nobody codes

Networking, IAM, DNS, secrets, alerts and dashboards all live in the repository. The test of whether this is real is simple and we run it: delete a non-production environment and rebuild it from the code. If that works, your disaster recovery plan is a plan rather than a document.

Pipelines that are allowed to say no

A pipeline that only ever goes green is theatre. Ours run tests, a security scan, an infrastructure plan review and a performance budget, and any one of them can stop a release. Deploys go out behind feature flags with an automated rollback trigger, which is what makes shipping on a Tuesday morning unremarkable.

The bill, explained

Tagging enforced at provision time so untagged resources fail the plan, dashboards that break spend down by team and environment, rightsizing based on actual utilisation, and savings plans bought against a committed baseline rather than a hopeful one. The first pass on a neglected account typically finds a quarter of the spend doing nothing at all.

20–35%

typical first-pass reduction on an untuned cloud account

What is included

  • Migration plan

    Workload inventory, dependency map, move-group sequencing and a written rollback position for each wave.

  • Terraform baseline

    Networking, IAM, compute, data and observability as reviewable code, with remote state and drift detection.

  • CI/CD pipelines

    Build, test, scan, plan-review and deploy, with feature flags and automated rollback triggers.

  • Observability

    Logs, metrics, traces and actionable alerts, routed to an on-call rota that a human agreed to.

  • Cost governance

    Enforced tagging, per-team dashboards, rightsizing and a commitment strategy reviewed quarterly.

  • Runbooks and handover

    Documented operational procedures plus a live failover exercise your team runs, not watches.

What we build with

  • Platforms

    • AWS
    • Azure
    • Oracle Cloud
    • Kubernetes

  • Infrastructure as code

    • Terraform
    • Helm
    • Ansible
    • Atlantis

  • Operations

    • GitHub Actions
    • Grafana
    • Prometheus
    • PagerDuty

How engagements are sized

Three sizes, so the scope matches the problem rather than the budget matching a template. Every tier is a starting point — the number moves with what we find in discovery, and you see the revised figure before anything is signed.

  • Essential

    One clear problem, scoped tightly and shipped.

    From

    AED 25,000

    per project

    A single application moving to cloud, or a pipeline and cost clean-up.

    • One workload migrated
    • Terraform baseline
    • CI/CD pipeline
    Get a firm number

  • Growth

    The full engagement, with measurement and iteration built in.

    From

    AED 75,000

    per project

    A full estate migration with observability, governance and cost control.

    • Multi-workload migration
    • Full observability stack
    • Cost governance
    Get a firm number

  • Enterprise

    Multi-entity, regulated, or integrated across several systems.

    From

    AED 190,000

    per project

    Regulated workloads, multi-account landing zones, or hybrid and multi-cloud.

    • Landing zone and guardrails
    • In-region residency design
    • DR with tested failover
    Get a firm number

Prices are in AED excluding 5% VAT. Other currencies on the pricing page.

How delivery actually runs

The phases below are what a typical engagement moves through, with the durations we plan against. You always know which phase you are in and what leaves it.

See the full process
  1. 1

    Assess

    1–2 weeks

    Workload inventory, dependency map, cost breakdown and a residency review of the whole data path, not just the database.

  2. 2

    Codify

    3–5 weeks

    Networking, identity, compute and observability written as Terraform, proven by rebuilding a non-production environment from nothing.

  3. 3

    Migrate in waves

    3–8 weeks

    Move groups in dependency order, each with a written rollback position, rehearsing every stateful cutover on a copy first.

  4. 4

    Operate and optimise

    2–4 weeks

    Pipelines that can block a bad release, alerts routed to an on-call rota a human agreed to, and the first cost pass.

  • Assess · You get

    • Workload inventory
    • Data-flow map
    • Cost baseline

  • Codify · You get

    • Terraform baseline
    • Rebuilt staging environment
    • Remote state and drift detection

  • Migrate in waves · You get

    • Wave-by-wave migration
    • Rehearsed cutovers
    • Measured downtime windows

  • Operate and optimise · You get

    • CI/CD with gates
    • Alerting and on-call
    • Cost dashboards and savings plan

Built for the UAE

What working with a Dubai partner actually changes

Most of what follows is invisible until it goes wrong — a supplier who cannot keep data in-country, an invoice the FTA rejects, a support rota that is asleep for half of your working day. These are the questions we answer before they become findings.

In-country regions exist on every major provider — AWS me-central-1, Azure UAE North, OCI Dubai — so residency is achievable. The work is in everything around them: observability tenants, backup replication and support access routinely leave the country by default, and that is what an auditor finds.

  • Data residency, decided up front

    AWS me-central-1, Azure UAE North and OCI Dubai are all in scope. We map the whole data path — backups, logs, metrics and support access — rather than the primary database alone, and put the result in writing.

  • PDPL, and the free zones

    Federal Decree-Law No. 45 of 2021 governs most of the mainland; DIFC and ADGM entities fall under their own data protection laws instead. We establish which applies to your entity before we design anything that touches personal data.

  • VAT and e-invoicing that pass

    Five per cent VAT, FTA-compliant tax invoices, the audit file the authority can request, and readiness for e-invoicing as the mandate phases in. Configured in the build, not patched after the first filing is rejected.

  • Your hours, your languages

    Delivery runs on Gulf hours with real overlap with your team, in Arabic and English. Customer-facing interfaces, documents and training are produced in both where you need them, with RTL treated as a design requirement rather than a translation step.

Sectors we do this in most

Not the only sectors we work in — the ones where we have shipped this service enough times to know the regulatory edges and the usual traps.

  • B2B SaaS

    Marketing sites and product UX that feed qualified pipeline.

  • Fintech

    Onboarding, KYC and dashboards that build trust and convert.

  • E-commerce & Retail

    Fast storefronts and checkouts engineered to lift AOV.

In-house, generalist agency, or us

An honest comparison, including where the other two options are the better call.

Hiring in-houseWorking with us
Time to first outputThree to five months to source, notice-period and onboard, in a market where senior specialists are scarce and expensive.Two to three weeks from signature, with people who have shipped this before.
Cost shapeFixed monthly cost plus visa, insurance, end-of-service and equipment, whether or not there is a full workload.Scoped to the work. Costs stop when the work does.
Breadth of skillOne or two specialisms per hire. Anything outside them gets improvised or outsourced anyway.Design, engineering, security and growth from the same team, without a handoff between vendors.
Institutional knowledgeStays in the building — which is the real advantage, and the reason to hire eventually.Documented and handed over. We write runbooks so you can take it back in-house.
When it is the wrong choiceRarely, once the workload is genuinely full-time and permanent.If you need someone in your standups every day for years, hire. We will say so.

Related work

Questions people ask before starting

Yes. AWS me-central-1, Azure UAE North and OCI's Dubai regions are all in scope, and we extend residency to the whole data path — backups, logs, metrics and support access — rather than the primary database alone. Where a component genuinely cannot run in-region, we tell you which one and what the options are.

Services that pair with this

Most engagements use two or three together.

Ready to talk about Cloud & DevOps?

Tell us what you are building and where it is stuck. We will come back with a scope, a timeline and a number — usually within two working days.

Step 1 of 3 · What you need

Which services are you interested in?