The TCO debate, cloud versus on-premises infrastructure, is a legitimate and important one. But it's largely irrelevant to the clients I work with.
My practice focuses on small businesses and startups. By definition, these companies are starting fresh. They have no existing servers to amortize, no data centers to maintain, and no legacy systems locking them into a particular architecture. For them, on-premises infrastructure isn't a competing option. It's a non-starter. The upfront capital expenditure alone would be a serious liability for a company that should be directing every dollar toward growth and product.
Cloud infrastructure, by contrast, offers exactly what early-stage companies need: low barrier to entry, predictable operating costs, instant scalability, and zero hardware maintenance burden. I have never recommended buying on-premises infrastructure to a small business or startup client, and I don't anticipate ever doing so.
This brings me to where the TCO conversation actually belongs: established enterprises with existing on-premises infrastructure. For these organizations, the calculus is genuinely complex. They're weighing sunk costs, migration expenses, long-term licensing, staffing, and security overhead against cloud subscription costs at scale. That's a real debate worth having, and one with no universal answer.
The one exception
I'll acknowledge one genuine exception: critical infrastructure. I worked with an electrical utility company where on-premises deployment was a legitimate operational consideration. When you're dealing with power grid systems, there are security, latency, and regulatory realities that can't always be solved in the cloud. Even so, my approach was to develop the application in the cloud and migrate on-premises for production. Cloud development is simply faster, more collaborative, and more cost-effective, and those advantages don't disappear just because the final destination is on-prem. Build smart, then deploy where the environment demands.
For everyone else, the question isn't cloud versus on-prem. The question is simply which cloud, and how to use it well.