---
title: "Hosting — your systems run where the numbers say so"
description: "Three paths for your servers: public cloud (Azure, AWS), our EU data centre, or staying in your house — decided by numbers, not cloud brochures. Operated with the same care."
canonical: "https://corevatis-redesign.pages.dev/en/services/hosting/"
lang: en
schema_type: WebPage
---
# Hosting — your systems run where the numbers say so

Three paths for your servers: public cloud (Azure, AWS), our EU data centre, or staying in your house — decided by numbers, not cloud brochures. Operated with the same care.

## The short version

- **What:** The place for your server workloads: public cloud, our EU data centre, or still your house — with the same managed operations everywhere.
- **Why:** The server room costs space, power and worry — but the cloud is not automatically cheaper. The decision deserves numbers.
- **For whom:** Companies whose hardware is at its end, whose server room should go — or who simply want to know the best place.
- **Billing:** Per workload per month; platform costs passed through transparently, operations stay the same managed-server block.

A good fit if:

- The server hardware is written off and the replacement question looms
- The server room should become office, storage or simply quiet
- Someone said 'to the cloud' — and nobody did the maths

## What does hosting mean with us — in one sentence?

Hosting answers **where** your server workloads run — by numbers, not fashion: public cloud, our EU data centre, or still in your house. The [operations](/en/services/managed-server) are the same in all three places.

## The three paths

| Path | When it fits | What to know |
|---|---|---|
| **Public cloud** (Azure, AWS) | Fluctuating loads, modern applications, global access, tight Microsoft integration | Flexible, but running costs grow with usage — constant full load gets expensive |
| **EU data centre** — our virtualisation environment | Constant workloads, plannable costs, data sovereignty, no hyperscaler tie | Fixed monthly costs per workload; location and contract partners in the EU |
| **In your house** | Machine-adjacent systems, large local data volumes, good existing hardware | Remains a first-class option — we operate what is there |

Most environments end up **mixed** — the ERP in the data centre, collaboration in the cloud, machine control in-house. That is exactly why we price [per instance, wherever it lives](/en/services/managed-server).

## Why we have no cloud religion

"To the cloud" is a brochure sentence, not a strategy. The honest per-workload calculation has four items: platform costs, licence consequences, connectivity, and compliance. We put that calculation openly on the table — and recommend against a move when the numbers say so.

## What we take on

- The placement decision per workload — with a three-year cost comparison, not a first-month one
- The migration as a project: planned, with a maintenance window and a way back
- Operations afterwards: monitoring, patch windows, [backup with restore tests](/en/services/backup) — the same block as before, only the place is new
- Platform costs passed through transparently: you see what the place costs and what the operations cost

## FAQ

**Do we have to go to the cloud?**
No. "In your house" is an equal answer with us — we earn on operations, not on the move. What we no longer recommend: buying new own hardware without having run the alternatives once.

**Where exactly does the data sit in the EU data centre?**
In an EU data centre with EU contract partners — the concrete locations and the privacy documentation are disclosed in the offer, not on request.

**Can we move back or elsewhere later?**
Yes — workloads we operate are documented and portable. No place is a one-way street; that too is part of "no lock-in".

## Related topics

- [Managed Server — the operations, wherever](/en/services/managed-server)
- [Backup — the off-site copy](/en/services/backup)
- [Add-ons at a glance](/en/services/add-ons)