Analytical use of cookies
IT integration and managed solutions ยท anonymised case study
Verified infrastructure scope
A hybrid portfolio built around colocation and dedicated servers, supplemented by a cloud/VPS layer. The current register contains 21 active service positions; the oldest active position started on 17 May 2012.
Infrastructure objective
Problem and operating context
The verified mix points to an environment where an integrator can combine physical placement, dedicated compute and a virtual layer without reducing the portfolio to a single platform. This is an architectural interpretation of active services, not a quoted customer requirement.
Development path
How the service portfolio evolved
The oldest active position dates from May 2012. Colocation and dedicated-server layers are both documented from 18 May 2012, followed by a cloud/VPS layer from June 2012. The current portfolio demonstrates parallel use of physical and virtual resources.
Active architecture
Layers confirmed in the service register
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 21 active service positions. The register classifies 16 positions as colocation, 11 as dedicated-server services and 1 as cloud/VPS. Overlap between categories reflects multi-layer service descriptions and is disclosed instead of being hidden.
Related services
Build a similar infrastructure scope
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.