Most companies ask the cloud question once, for everything: are we a cloud company or not? That framing is the problem. Each system you run has its own costs, its own users and its own risks, and the right home for one is often the wrong home for another.
Where the cloud earns its keep
Renting makes sense when a workload grows and shrinks, when people need to reach it from anywhere, or when running it yourself would mean patching and babysitting something that isn't core to your business. Email and collaboration are the clearest examples: a service like Microsoft 365 will be more reliable than a mail server in a closet, and usually cheaper once you count the time it takes to run one.
Where owning hardware wins
Steady, predictable workloads are a different story. File archives, line-of-business databases and backups stay roughly the same size month after month, and that's exactly where monthly fees, per-seat licensing and data-transfer charges add up. Over a few years, they can pass the cost of buying the hardware outright.
Some workloads also belong close to the people using them: applications that are sensitive to delay, data that clients or regulators expect you to keep under your direct control, and AI that works on confidential documents.
Four questions for each system
For every system on your list, compare both options on the same four things:
- Cost over several years, not just this year's bill. Include licensing, data transfer, hardware refreshes and the staff time to run it.
- Performance for the people who use it. Where are they, and what does a slow response cost them?
- Compliance and client requirements. Security questionnaires and contracts increasingly ask where data lives and who can reach it.
- What happens when it fails. Who gets the call, how fast can it be restored, and when did anyone last test that?
The answers rarely point the same way for every system, and that's fine. Most organizations end up with a mix.
On-premises isn't automatically safer
A server in a closet with missed patches and untested backups is a bigger risk than a well-run cloud service. Keeping a system in-house only pays off when someone is actually running it well: monitoring it, patching it, and restoring from backup on a schedule to prove the backups work.
Revisit the answer
The right mix changes as you grow, as prices change and as clients ask new questions. Moving a workload back from the cloud, sometimes called cloud repatriation, is a normal planned project, not an admission that the original move was a mistake. A yearly look at what you run, what it costs and where it lives is usually enough to keep the mix honest.