The company’s own server room is not automatically wrong. But it should be a conscious decision.
objectale clarifies whether self-operation, colocation or a hybrid model fits the operating reality — technically, economically and organisationally.
When the company’s own server room reaches its limits, cloud services become business-critical or several sites need to be connected securely, more than rack space is required.
objectale helps classify the operating model, location, colocation partner, connectivity, security and responsibilities clearly — from the existing server room through professional colocation to hybrid infrastructure with cloud connectivity, backup and recovery.
Colocation is rarely decided for purely technical reasons. Usually there is a concrete trigger: a server room is no longer sufficient, a site is changing, cloud and SaaS services are becoming more important, or availability and recovery need to become more resilient.
A typical Swiss SME operates central systems at its main site. Two additional sites access them. Microsoft 365 and selected SaaS services are already in use. The question is not: which datacenter is the best? The question is: which operating architecture fits the situation?
This overview does not replace an architecture decision. It shows which questions should be clarified early before offers are compared or infrastructure is moved.
| Criterion | Server room | Colocation | Hybrid model |
|---|---|---|---|
| Site dependency | high | lower | controllable |
| Cloud integration | possible | easy to plan | central component |
| Internal operating effort | high | can be reduced | can be clearly distributed |
| Migration | low | required | possible step by step |
| Future viability | limited to good | good | high if planned properly |
Datacenter, cloud connectivity and disaster recovery only work reliably when the connections between these layers are planned end to end.
The architecture shows where critical dependencies emerge: between headquarters and datacenter, between datacenter and cloud, and between headquarters, production datacenter and backup site.
In a short architecture discussion, we clarify which systems, sites and cloud accesses are business-relevant — and which connectivity model is appropriate for them.
Assess whether colocation makes sense, which requirements are relevant and which alternatives should be considered.
Structure which systems remain on site, which belong in colocation and which are operated via cloud or SaaS.
Connect datacenter, sites, internet, cloud connectivity and, where needed, SD-WAN or SASE into a viable architecture.
Classify requirements for redundancy, recovery, site separation and resilience realistically and economically.
Make performance, cost, responsibility, contract logic and operating model of datacenter, carrier and implementation partners comparable.
Prepare migration, clarify dependencies and support coordination between customer, provider, datacenter and technical partners.
No large infrastructure audit as a starting point. Instead, a structured classification of which operating architecture fits the need, the risk and the next investments.
Capture systems, sites, providers, cloud services, contracts, operating risks and known bottlenecks.
Professionally compare server room, colocation, cloud and hybrid model — including connectivity, security and responsibility.
Obtain provider options, make services comparable and support the next steps through to implementation.
Datacenter and colocation projects rarely fail because of rack space. The harder part is unclear handovers between customer, datacenter, carrier, cloud provider, security partner and internal IT operations.
Datacenter and colocation sit between infrastructure, connectivity, cloud and recovery. These pages help with the next step.
Colocation is rarely just rack space. The decisive factors are location, access, WAN, cloud connectivity, operating responsibility and recovery.
You do not need to have a finished datacenter project defined yet. Often a concrete trigger is enough: a server room reaching its limits, a site move, a cloud decision, a recovery topic or the sense that the existing infrastructure should be reassessed.