Skip to main content
Infrastructure · KSA & GCC

Infrastructure Services

Enterprise infrastructure across servers, storage, network, virtualisation, data-centre and monitoring — vendor-neutral, capacity-planned, NCA-ECC and PDPL aligned from the rack diagram up.

99.99%platform availability SLA
24/7monitoring · 2 hubs
Vendor-neutralworkload-led design
// 01 · What we build

Six domains. One reference architecture.

Compute, storage, network, virtualisation, data-centre, and observability — the six pieces every enterprise estate has to get right, picked workload-by-workload, not vendor-by-vendor.

INF.01

Server & compute

Dell PowerEdge, HPE ProLiant, Cisco UCS, Lenovo ThinkSystem. Sized against real workload data — IOPS, memory pressure, CPU pinning — not a vendor template.

INF.02

Storage

All-flash, hybrid, object. NetApp, Pure, Dell PowerStore, HPE Alletra, Huawei OceanStor. Tiered against access patterns — hot, warm, archive.

INF.03

Network

Cisco, Arista, Juniper, Fortinet, Aruba. Spine-leaf, SD-WAN, micro-segmentation. Designed for the traffic flows you actually have, not the ones the brochure assumes.

INF.04

Virtualisation

VMware vSphere, Nutanix AHV, Hyper-V, Azure Stack HCI, Red Hat OpenShift Virtualization. Pick by skill base and exit cost — not feature checklist.

INF.05

Data-centre design

Tier-rated facility design, power, cooling, cabling, rack & stack. On-prem, colocation, or hybrid — NCA-ECC ready and PDPL-aware from the floor plan up.

INF.06

Monitoring & observability

Prometheus + Grafana, Datadog, Zabbix, vRealize. Capacity tracking, anomaly alerting, and dashboards that an on-call engineer actually uses.

// 02 · Deployment models

Four shapes the estate can take.

On-prem, colocation, hybrid, or fully managed. The shape depends on residency, capex appetite, and how comfortable the team is with rack-level work.

01

On-prem

Your facility, your gear, your team — with NAS design, deployment, and optional managed services on top.

  • Optimise for · control · capex
02

Colocation

Your gear, third-party Tier-III/IV facility. We design, rack, and operate from inside the colo. KSA-resident options included.

  • Optimise for · uptime · power
03

Hybrid most common

Sensitive workloads on-prem, burst capacity in cloud, single operating model across both. The most common shape for KSA regulated estates.

  • Optimise for · residency · scale
04

Managed-DC

NAS-managed data centre operations — physical access, power, cooling, monitoring, patching, capacity. You see a monthly scorecard and an open ticket queue.

  • Optimise for · full delegation
// 03 · Reference architectures

Three blueprints. Picked by workload shape.

Most engagements end up landing on one of three reference architectures — classic 3-tier, hyperconverged, or hybrid edge-to-cloud. Vendor-neutral, scaled per workload, with named exit costs.

Pattern · 01

Classic 3-tier

The textbook shape. Separated web/app/db tiers on dedicated compute, SAN-backed storage. Predictable, well-understood, audit-friendly.

  • Best for · regulated workloads, ERP, banking core
  • Scales · vertically per tier
  • Exit cost · low (commodity)
  • Operational complexity · medium
Pattern · 02

Hyperconverged (HCI)

Compute, storage, and network virtualised on shared-nothing nodes. Linear scale-out, single management plane. Nutanix, VxRail, Azure Stack HCI.

  • Best for · VDI, mid-size virtualised estates
  • Scales · horizontally per node
  • Exit cost · medium (vendor lock)
  • Operational complexity · low
Pattern · 03

Hybrid edge-to-cloud

Edge sites for latency-sensitive ops, core DC for steady-state, cloud for burst and DR. Most common for retail, telecom, and multi-site enterprises.

  • Best for · distributed orgs, OT/IT split
  • Scales · per tier independently
  • Exit cost · varies per tier
  • Operational complexity · high
// 04 · Capacity planning

Tracked monthly. Not just in a crisis.

A typical capacity scorecard we keep live for managed-infrastructure clients. Trend it, not just spot-check it. Buying decisions are made against the curve — not the moment.

Capacity Scorecard · May 2026

Client · Saudi Telecom · Riyadh DC

Live tracking · 90-day forecast · refreshed monthly

Compute · vCPU

340 vCPU provisioned
67%
Green

Memory · vRAM

1.4 TB provisioned
79%
Watch

Storage · usable

120 TB AFA + 480 TB hybrid
52%
Green

Network · core utilisation

2 × 100G uplinks
42%
Green

Power · UPS load

2N redundant · 120 kW
88%
Order now

Cooling · rack thermal

21–24°C target
22.4°C
In range
// 05 · SLA tiers

Three SLA tiers. Choose per workload.

Different workloads carry different value at risk. We let you tier — Bronze for non-critical, Silver for business-critical, Gold for mission-critical — so the SLA matches the budget, not the brochure.

Bronze · Tier 3

Standard

For non-critical workloads — dev/test, internal tools, batch processing. Reliable, but not 24/7-life-or-death.

99.5%
~ 4 hours / month downtime
  • First-response time < 4 h
  • MTTR target < 24 h
  • Patch cadence Monthly
  • Coverage Business hrs
Gold · Tier 1

Mission-critical

For core banking, healthcare critical systems, regulator tier-1. Active-active or hot-standby with sub-minute detection.

99.99%
~ 4 minutes / month downtime
  • First-response time < 5 m
  • MTTR target < 60 m
  • Patch cadence Per change
  • Coverage 24/7 + on-site
// 06 · Methodology

Four phases. Design to ongoing operate.

Assess, design, deploy, operate. The last phase is the longest one — every infrastructure programme is judged on how well it ages, not on the deploy day.

  1. 01

    Assess

    Current-state inventory, workload profile, growth forecast. Right-sizing against measured data — not the vendor sizing guide.

  2. 02

    Design

    Reference architecture pick, vendor selection, capacity sizing, network design, BOM. Signed off with the BoQ before any procurement.

  3. 03

    Deploy

    Rack & stack, cabling, firmware baselining, virtualisation, network config, monitoring stand-up, security baseline. UAT, then production.

  4. 04

    Operate

    Monitoring, patching, capacity reviews, lifecycle planning. The phase that runs for 5 years; the one that decides whether the build was worth it.

// 07 · Vendor partners

Vendor-neutral. Credentialed across the field.

// 09 · FAQ

Common questions.

Q.01Are you tied to a specific vendor?

No. We hold credentials with Dell, HPE, Cisco, Fortinet, NetApp, Pure, Nutanix, and others — and we recommend against any of them on the days the workload and the data say we should.

Q.02Do you handle physical data-centre work?

Yes — design, rack & stack, cabling, power, cooling. We work in your facility, in a colocation site, or in our partner facilities in Riyadh, Cairo, and Muscat.

Q.03Can you do hyperconverged?

Yes. Nutanix, VxRail, and Azure Stack HCI are common picks. We size HCI honestly — there are workloads it suits and ones it doesn't, and we name both before the order goes in.

Q.04What about 24/7 monitoring?

Standard with any managed-infrastructure engagement. Prometheus/Grafana or Datadog, capacity tracking, anomaly alerting, and an on-call rota out of Riyadh and Cairo.

Q.05Can the infrastructure stay inside KSA?

Yes. We design and operate KSA-resident infrastructure across on-prem, colocation, and KSA-region cloud — under NCA-ECC and PDPL controls by default.