Platform/Connectivity/DirectConnect

A dedicated line into your cloud.

Dedicated fibre circuits with deterministic latency — for the estates where 'usually fast' isn't a number.

Dedicated fibreDeterministic latencyCarrier liaison included

Talk to us All Connectivity

Capabilities

Guaranteed paths, guaranteed accountability

Performance you can count on. Accountability you can prove.

Dedicated capacityYour circuit, your bandwidth — no contention, ever.Your circuit, nobody else’s

Deterministic latencyFixed paths give the latency numbers your SLAs can quote.A figure, in the contract

Carrier liaisonOrdering, escalation and SLA enforcement with telcos handled by us.

One throat for the circuit

Redundant designsDiverse paths and dual circuits for zero-single-point estates.

Diverse paths, documented

Contracted SLAAvailability and latency carry contractual credits.

Accountability in writing

Reaches every zoneOne circuit terminates into the transit fabric and reaches all your pools.

Connect once, reach all

Private by constructionTraffic never touches the internet; encryption is optional on top.

Compliance-friendly path

Upgrades in placeGrow circuit capacity without re-provisioning the physical path.

Scale on the same fibre

Hybrid topologiesPairs with CloudConnect for encrypted failover over carrier paths.

Belt and braces

Monitored end to endLight levels, errors and utilisation watched by the NOC.

Problems seen first

Compare the circuits

Single, redundant, or diverse

Dedicated fibre in every shape, with latency written into the agreement — the difference is how many ways the traffic can get there.

ProductionEdgeComing soon

CIRCUIT 01

Single Circuit

A dedicated path

One dedicated fibre circuit into your cloud networks with deterministic latency and committed throughput.

Best for

Datacentre extensionReplication linksLatency-bound apps

Where it runs

Dubai AZ1RiyadhBahrainMumbaiDubai AZ2Nairobi

Plans

Circuit1 Gbps dedicated · latency SLASign in →Circuit Plus10 Gbps dedicated · latency SLASign in →CustomAny bandwidth and termination pointSign in →

CIRCUIT 02Production default

Redundant Pair

No single fibre

Two circuits on separate paths with automatic failover, for estates where the link itself cannot be a single point of failure.

Best for

Core bankingTrading linksPrimary replication

Where it runs

Dubai AZ1RiyadhBahrainMumbaiDubai AZ2Nairobi

Plans

Redundant2 × 1 Gbps · separate pathsSign in →Redundant Plus2 × 10 Gbps · separate paths · BGP failoverSign in →CustomAny pair sizing and failover policySign in →

CIRCUIT 03

Carrier Diverse

Different everything

Circuits across separate carriers and separate building entries — the shape regulators ask for when downtime is systemic risk.

Best for

Systemically important servicesRegulated financial linksSovereign programmes

Where it runs

Dubai AZ1RiyadhLagosDubai AZ2

Plans

Diverse2 carriers · 2 entries · latency SLASign in →Diverse Plus2 carriers · 2 entries · 2 zonesSign in →CustomAny diversity and resilience requirementSign in →

Two ways to buy

Point to point, or into the fabric

Both come with a latency number in writing. The difference is what sits at the far end.

Point to PointSite to zone

A circuit from your datacentre or office into a specific zone, terminating on your networks there.

✓Deterministic latency, contractually stated

✓Committed throughput end to end

✓Straightforward to model and audit

Best for a single critical path.

Into the FabricSite to estate

A circuit terminating on your transit fabric, reaching every pool and zone in your estate.

✓One circuit, many destinations

✓Routing policy held centrally

✓Add pools without new circuits

Best for multi-pool estates.

Who decides, who runs it

What each group gets from DirectConnect

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“Performance is contractual”

Latency and throughput are written into the agreement, which is what regulated and time-sensitive businesses need to commit.

GovernedSovereignPredictable

FAQs

What latency can you commit to?

A specific figure per route, written into the agreement after the path is designed — not a best-effort range.

How long does provisioning take?

Weeks rather than days, since it involves carrier delivery and cross-connects. We give you a dated plan up front.

Can we start with one circuit and add a second?

Yes — a single circuit can be upgraded to a redundant or carrier-diverse pair later.

Does it reach every zone?

Terminating into your transit fabric lets one circuit reach every pool and zone in your estate.

Is the traffic encrypted?

The circuit is private and dedicated; encryption can be layered on where your policy requires it.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

Can we drive it from Terraform and CI?

Yes. Every operation is exposed through the REST API, CLI and a maintained Terraform provider, with scoped API keys per team. If the console can do it, your pipeline can do it.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together