A rack, the power to fill it, and a cross-connect that lands tomorrow.
Quarter, half and full racks across our Lahore and Islamabad facilities, with A+B feed power, BICSI-aligned cabling and 24-hour cross-connects to any of the carriers in the meet-me-room — including, but not limited to, our own AS137492.
Cabinets you don't have to argue with the facility team about.
Our colocation footprint runs out of three carrier-neutral facilities — two in Lahore (Cantt and Johar Town) and one in Islamabad (I-9). Cabinets are 47U, 600 mm wide, with rear cable management and front-door perforated steel. Power lands as A+B feeds from independent UPS strings backed by N+1 generators; the default is 4 kW per rack metered, with 8 kW and breaker-fed options for high-density customers.
The interesting part of colocation is what's on the other end of the cross-connect, not the rack itself. Our facilities are carrier-neutral by policy: any licensed operator can land in our MMRs, and we charge a fixed cross-connect fee whether the customer is connecting to us or to a competitor. On-net customers get cross-connects to AS137492 in 24 hours; carrier-to- carrier connects are quoted within the standard turn-up window.
Customer profiles in our cages.
Other carriers landing in Punjab
Domestic and international carriers placing edge routers and transponders in our MMRs to terminate fibre and cross-connect to local operators.
SaaS / fintech with private infra
Companies running a hybrid stack — public cloud for elastic compute, our colo for data-residency-bound workloads.
Banks running their own infra
Tier-1 banks with stringent data-residency obligations and a preference for owning their hardware in carrier-neutral space.
Content / OTT delivery nodes
CDN appliances and origin servers placed inside our facilities for direct cross-connect to AS137492 and PKIX.
Government / defence systems
Tenancies that require a reviewed access policy, isolated cages, and audit-grade entry logs.
Hyperscaler edge / CDN POPs
Cache nodes from international content networks placed inside Punjab to reduce upstream transit.
Cage and cabinet details.
| Metric | Target | Notes |
|---|---|---|
| Sites | LHE × 2, ISB × 1 | Carrier-neutral |
| Cabinet size | 47U × 600 × 1100 mm | Rear cable manager standard |
| Power (default) | 4 kW metered A+B | 8 kW breakered on request |
| PUE design | 1.45 – 1.55 | Hot-aisle containment |
| Cooling | InRow chilled water | 23°C ± 1, 50% RH ± 5 |
| Fire suppression | Pre-action + clean agent | VESDA detection |
| Metric | Target | Notes |
|---|---|---|
| Power availability | 99.99% | 2N UPS / N+1 gen, fuel for 72 h |
| Access | 24×7 escorted / unescorted | Per customer policy |
| Cross-connect, on-net | 24 h delivery | Single-mode LC default |
| Cross-connect, off-net | 5 business days | Inter-MMR or carrier-to-carrier |
| Smart hands | Pay-as-used | PKR-billed, 30-min minimum |
| Compliance | ISO 27001 aligned | Access logs retained 12 mo |
From contract to first ping.
- 01
Cage walk
Day 0 – 3. Tour, capacity confirmation, security model agreed.
- 02
Provisioning
Day 3 – 7. Cabinet allocated, power feeds tagged, access list configured.
- 03
Install + cabling
Day 7 – 14. Customer hardware racked, structured cabling, cross-connects ordered.
- 04
Acceptance
Day 14 – 21. Power test, cross-connect light levels, access drill, billing starts on cutover date.
Common operational questions.
Are you carrier-neutral or do I have to use AS137492?
What's the noise / power policy on dense racks?
How is access controlled?
Do you offer managed services on top?
Can I bring my own carrier into your MMR?
What about disaster recovery between your sites?
How is power billed?
Tell us how many U, how many kW, and which city.
We'll come back with availability across our three sites, a price, and a delivery date. Cage walks happen the same week, in person.