Cloud, own server or hybrid? An honest comparison for institutions
The choice between the cloud and your own server is rarely black and white. Each path has its own costs and risks. Below we compare the three options most often considered by public offices, schools, cultural centres and small offices.
Three paths in one table
| Everything in the cloud | Own server in the building | Hybrid | |
|---|---|---|---|
| Start | quick, no hardware purchase | hardware purchase and setup | setup of some hardware |
| Annual cost | subscription per user | support and electricity | smaller subscription and support |
| Without internet | work stops | files and local tools keep working | the most important things keep working |
| When the provider has an outage | you wait for the fix | not applicable | email waits, the rest works |
| Control over data | with the provider, on its terms | full, in the building | sensitive data in the building |
| Responsibilities | on the provider's side | updates, backups, power | shared |
| Most powerful AI models | available | weaker local models | both, depending on the data |
When the cloud makes sense
The cloud works well where access from many places and a quick start matter: email, a shared calendar, documents without sensitive data. Large providers declare high security standards, and Google states that it does not train its models on Workspace customers' data1.
The details still need checking. Google guarantees that data will be stored in the European Union only in higher plans or with a paid add-on, not in the basic packages2. Personal data also requires a data processing agreement, which is worth reviewing with your data protection officer.
When your own server makes sense
Your own hardware wins with sensitive data, a steady workload and wherever an internet outage must not stop work. It gives full control over where the data is and who can access it, and after a few years it often works out cheaper than a per-user subscription.
It also comes with responsibilities that need to be stated honestly: updates, backups kept also outside the building, backup power and someone who looks after all of it. Without ongoing care, your own server quickly becomes a risk rather than a safeguard.
The hybrid model in practice
For most institutions, the most sensible split is:
- in the cloud: email on your own domain, a shared calendar and everyday documents without sensitive data,
- in the building: a file server with backups, documents with personal data and local AI for letters, minutes and children's data,
- a backup internet connection, so that an outage at one operator does not cut you off from the cloud.
When the provider has an outage, the institution still has files and tools in the building. When hardware in the building fails, it still has email and calendar in the cloud. From 2027 it will also be easier to change cloud provider, because the EU Data Act bans charges for switching to another company3.
Questions before you decide
- What data do we process, and which of it should not leave the building?
- How many hours without email and files can we get through?
- How much will we pay in total over five years in each option?
- Who on our side will be responsible for updates and backups?
To see what such outages look like in practice, read When the cloud goes down.