All services

Cloud, IT & support

IT, networking and cloud across the UAE

We design office networks and cloud infrastructure, then keep both running against response times we put in the agreement. Nothing is mounted before the site is surveyed.

Soukone, a concept build: the storefront admin showing AED 184,320 of revenue over thirty days with a trend sparkline, a live order feed from Deira, JLT, Business Bay and Al Barsha, and a product grid priced in AED.

Concept build — Soukone, engineered in-house

1h

Response when a site is down

4h

Response on degraded service

2

UAE cloud regions available

0

Markup on hardware

What we build

Eight pieces of the job, quoted separately

Eight jobs, split between projects and the monthly retainer.

How we build it

Three decisions we make early

Three habits that separate an audit from a shopping list.

Survey before spend

Nothing is specified until someone has walked the site with a meter and read the existing configuration. Coverage problems are usually walls, not access points, and half the switches quoted in a typical proposal are replacing hardware that was never the fault. The survey costs a day and routinely removes a five-figure line.

Configuration is code

Firewall policy, VLANs, landing zones and identity rules live in a version-controlled repository that is yours, reviewed before they are applied and reversible afterwards. It means a change has an author and a date, a failed cutover rolls back in minutes, and nothing important is stored only in an engineer's memory.

Restores, not backups

A backup job that reports success proves nothing. We restore from it on a schedule, to a clean environment, and time how long it takes — because the number you actually need in an incident is how many hours until people can work again. That figure goes in the quarterly review.

What you get

What the audit and the first month produce.

  • A network map and a written risk list
  • Firewall policy, VLANs and guest isolation
  • A Wi-Fi survey before anything is mounted
  • An AWS or Azure landing zone, defined in code
  • Single sign-on with multi-factor everywhere
  • Backups with a restore we have actually tested
  • Monitoring with alerts that reach a person
  • Named response times in the agreement
  • Monthly patching and a quarterly review
  • Hardware bought at distributor price, no markup

Stack

What this work actually runs on

What we run, monitor and hand over.

Where it runs, and how it gets there.

10 tools

  • AWS
  • Vercel
  • Cloudflare
  • Docker
  • Terraform
  • GitHub Actions
  • Nginx
  • Ubuntu
  • Grafana
  • Sentry

A drawing of a deploy pipeline: four stages — commit, build, test, deploy — lighting up in sequence as a line fills across them.

Names, not logos. Everything listed is something we build with or integrate, not a category page we copied.

Where it lands

Six sectors this work is bought in

Sites and workloads we are usually called into.

  • Professional services

    Practice management, billing and client portals.

  • Hospitality

    Booking engines, guest apps and property dashboards.

  • Education

    Enrolment portals, course platforms and parent apps.

  • Government

    Service portals, bilingual forms and accessibility work.

  • Logistics

    Dispatch boards, driver apps and proof of delivery.

  • Energy

    Field reporting, asset registers and offline-first tools.

All ten sectors we build for

Process

Five stages, and what you hold at each

Five stages, and nothing cut over during business hours.

  1. 01

    Scope

    A site walk, a network map, a written risk list.

    Audit report

  2. 02

    Prototype

    The new design proven on a test VLAN or account.

    Test environment

  3. 03

    Build

    Configuration written as code, reviewed before it is applied.

    Config repository

  4. 04

    Launch

    A staged cutover out of hours, with rollback ready.

    Cutover plan

  5. 05

    Run

    Monitoring, patching and a quarterly review with real numbers.

    Quarterly review

How we quote it

We quote projects and support separately — the retainer monthly, the project work only after the audit.

  • Projects and support are quoted separately, never bundled
  • Response times sit in the agreement, not in a brochure
  • Hardware is bought at distributor price with no markup

Quoted as support & care: monitoring, patching, small changes, agreed response times. We publish no bands — pick the pieces you need and one itemised quotation comes back within 48 hours, free either way.

Get a quote

Questions

Before you send the brief

Projects, support, or both?

Both, quoted separately, because bundling them hides which one is expensive. Project work is quoted after the audit, when we know what is actually on the network. Support is a monthly retainer with named response times, a monthly patch cycle, and a quarterly review built on real ticket numbers rather than a satisfaction score. You can take one without the other.

Can our data stay in the UAE?

Yes. AWS and Microsoft both operate UAE regions, so workloads with residency requirements stay onshore. We map which systems genuinely need it — usually a smaller set than people expect — because pinning everything to one region costs more, limits which managed services you can use, and does not by itself satisfy a PDPL obligation. The map goes in the audit report, in writing.

How quickly do you respond?

One business hour when a site is down, four hours for degraded service, one business day for a single-user issue. Cover is Sunday to Thursday, nine to six Gulf time, with escalation to a named engineer rather than a queue. Out-of-hours cover is available as a separate line. These numbers are in the agreement, and the quarterly review reports how often we hit them.

Do you resell hardware?

No. We specify it and manage the procurement, but you buy at distributor price with no margin coming to us. It removes the obvious conflict: the recommendation stays about your site rather than our resale spread. It also means you own the support contracts directly, so a warranty claim does not have to route through us and wait for our ticket queue.

What happens if we replace you?

You keep everything needed to run without us. The configuration repository is yours, cloud accounts are in your company's name with our access removable in one click, credentials sit in your password manager, and the network map is a document rather than knowledge in someone's head. We will also hand over to an incoming provider directly if you ask us to.

Related

Where this shows up

Two builds we host, monitor and patch ourselves.

  • E-commerce storefront

    Soukone

    An AED storefront with card and instalment payments, VAT-correct invoices and a steady checkout.

    LCP on a product page
    1.0s
    Cumulative layout shift
    0.00
  • Clinic booking system

    Nadra Clinics

    A four-branch booking system with held slots, WhatsApp confirmations and a front-desk console.

    Lighthouse accessibility
    100
    LCP on the slot picker
    1.1s

Bought alongside

What we are usually keeping running for people.

  • Custom software

    CRM and internal systems shaped around how you already work.

    Explore
  • AI implementation

    Retrieval and assistants wired into the data you already hold.

    Explore
  • Web development

    Marketing sites and web apps in Next.js, ready for Arabic.

    Explore

Book the audit, then decide.

A site walk and a written risk list come first. Project work is quoted after that, never before.