"Let's move to the cloud" has become almost a reflex. But for a small business, a professional practice or even a personal project, the choice between cloud services and on-site servers has no answer that fits everyone. It depends on what you need to run, who manages it, how predictable the load is and how your Internet connection behaves.
What we are talking about
- On-premise: servers and equipment you own, installed on your premises or in a cabinet on site. You buy the hardware, power it and maintain it.
- Colocation: your hardware, but housed in a data centre that provides space, power, cooling and connectivity.
- Public cloud: compute, storage and services rented on a pay-as-you-go basis from a provider.
- Hybrid: a combination, for example an on-site file server with email and backups in the cloud.
The cloud itself comes in different layers:
| Model | What the provider gives you | What you manage | Example |
|---|---|---|---|
| IaaS | Virtual machines, networks, disks | Operating system, applications, data | A virtual server |
| PaaS | A ready platform for the application | Code and data | Managed database |
| SaaS | A complete application | Users, configuration, data | Subscription email |
Shared responsibility
A common misconception is that in the cloud "the provider takes care of security". In reality the shared responsibility model applies: the provider protects the physical infrastructure and the layers it manages, while you remain responsible for configuration, accounts, permissions and data.
A cloud storage bucket accidentally left public, an admin account without a second factor, a virtual machine never updated: these are the customer's problems, not the provider's. The further you move towards SaaS, the less you have to manage, but accounts and data always remain yours.
Costs, without illusions
On-premise means upfront spending (servers, drives, UPS, licences) and ongoing costs that are often underestimated: electricity, hardware replacement after a few years, the time of whoever manages it, call-outs when something breaks.
Cloud means no initial investment and pay-per-use, but with items that grow quietly:
- resources left running and forgotten;
- storage that accumulates, including snapshots and backups;
- outbound traffic, often billed separately and significantly;
- add-on services such as public IP addresses, load balancers, log retention.
For steady, predictable workloads that run all year, on-site or colocated hardware can cost less in the long run. For variable, seasonal or experimental workloads, the cloud is hard to beat.
Concrete decision criteria
Connectivity
If users work in the office on large files, an on-site server serves them at local network speed. With the cloud every file open goes over the Internet line: with good fibre that is fine, with a slow or unstable connection it becomes a bottleneck, and if the line drops everything stops. A second backup line then becomes a requirement.
Available skills
An on-site server needs someone to update it, check the drives, verify backups and step in when something fails. If nobody in the company can do this and you have no trusted provider, a well-configured SaaS service is often safer than a neglected server.
Data
Consider where the data resides, who can access it and what the contracts say. For personal data the GDPR requires you to know who processes it and where; many providers let you choose the European region where it is stored. Also think about how you would recover the data if the service shut down or changed its terms.
Vendor lock-in
The more you use a provider's proprietary services, the more expensive migration becomes. Open formats, regular exports and standard components such as virtual machines and containers reduce this risk.
Sensible hybrid setups
For many small organisations the most balanced combination is:
- email, calendars and collaboration in SaaS, where the provider's reliability exceeds what you could achieve yourself;
- heavy working files and local applications on an on-site server or NAS;
- backups of the on-site server to the cloud, so a copy exists off the premises;
- accounts protected by multi-factor authentication everywhere.
In short
- On-premise, colocation, cloud and hybrid meet different needs.
- In the cloud, security is shared: configuration, accounts and data remain your responsibility.
- Assess costs over several years, including power, time, outbound traffic and forgotten resources.
- Connectivity, available skills and data location weigh as much as price.
- A well-designed hybrid setup often combines the best of both worlds.
