Colocation and infrastructure growth for a nationwide retail network

A long-running infrastructure portfolio combining colocation with dedicated-server and cloud/VPS layers. The current register contains 23 active service positions; the oldest active position started on 3 March 2009.

Nationwide retail and distribution network ยท anonymised case study

Verified infrastructure scope

A long-running infrastructure portfolio combining colocation with dedicated-server and cloud/VPS layers. The current register contains 23 active service positions; the oldest active position started on 3 March 2009.

23active positions
2009-03-03oldest active service
3verified service layers

Infrastructure objective

Problem and operating context

The active portfolio indicates a need to keep multiple infrastructure layers in one operational environment as the organisation develops. This objective is inferred from the verified mix of active services and is not presented as a customer quotation.

Development path

How the service portfolio evolved

The oldest active service dates from March 2009. The colocation layer is documented from August 2009, the dedicated-server layer from January 2014 and the cloud/VPS layer from March 2015. This sequence shows an infrastructure portfolio expanded in stages.

Active architecture

Layers confirmed in the service register

LayerActive positionsFirst active start
Colocation92009-08-14
Dedicated servers12014-01-22
Cloud / VPS12015-03-01

Category counts may overlap when one active service description covers more than one infrastructure layer. The total number of active positions is therefore the primary portfolio measure.

Measured result

The outcome documented in current data

The measurable outcome is a current portfolio of 23 active service positions, including 9 classified as colocation, 1 as dedicated-server service and 1 as cloud/VPS. The oldest active position remains recorded from 2009; this is evidence of service longevity, not an uptime declaration.

Related services

Build a similar infrastructure scope

ColocationDedicated serversCloud ProVPS servers

Methodology and privacy

What is verified and how to read the figures

  • Source: the internal eCRM active-service register, snapshot dated 18 August 2026.
  • The customer is identified only by industry; names, initials, contract numbers, IP addresses, prices and ticket contents are not published.
  • Service layers are classified from active service descriptions. Category counts may overlap and must not be added together.
  • The pages do not claim uptime, zero-downtime migration, RTO, RPO or business results that are not present in the verified source.