The server room was flooding. Water dripping through the ceiling tiles, three inches deep on the floor, and our primary database server sitting right in the splash zone. My boss was on vacation. The backup server was two states away. And here I am at 2 AM with a shop vac and a prayer.
That was 2019. These days, when people ask me about cloud versus self-hosting, I think about that night. Not because the cloud would have saved me—flooding happens to data centers too—but because it crystallized something important: where you run your infrastructure matters less than understanding the trade-offs.
The real question isn’t “cloud or self-hosting?” It’s “who’s taking responsibility for what, and at what cost?”
The Landlord Reality Check
Let’s get something straight: AWS, Azure, and Google Cloud aren’t your infrastructure. They’re your landlord’s infrastructure. You’re renting compute and storage with a month-to-month lease that can change without your input.
Landlords can be great. They fix the plumbing. They maintain the building. They handle property taxes. But they also control rent prices, decide what modifications you can make, and ultimately own the asset that your business depends on.
Self-hosting is like owning your house. More control, more responsibility, and when something breaks at 2 AM, it’s your problem. But it’s also your equity, your rules, and your timeline.
Neither approach is inherently superior. They’re tools for different jobs.
“The best infrastructure decision is the one that matches your risk tolerance, technical capabilities, and business model—not the one that sounds coolest at conferences.”
When Cloud Makes Perfect Sense
Cloud providers excel in specific scenarios that play to their strengths: scale, speed, and shifting operational burden.
Variable workloads are cloud’s sweet spot. If your application sees traffic spikes during Black Friday or tax season, paying for compute by the hour beats maintaining servers for peak capacity year-round. Auto-scaling isn’t magic, but it’s math that works in your favor.
Geographic distribution becomes trivial with cloud providers. Spinning up servers in Singapore, Frankfurt, and São Paulo to serve global users? That’s an afternoon project in AWS, not a multi-year infrastructure expansion.
Rapid prototyping and startups benefit from cloud’s pay-as-you-go model. When you’re testing product-market fit, the last thing you need is a $50,000 server purchase sitting idle because your pivot killed that feature.
Specialized services often justify cloud adoption even when basic compute doesn’t. Machine learning inference, managed databases, and content delivery networks represent years of engineering work. Unless that’s your core competency, buying it makes sense.
When Self-Hosting Wins the Long Game
Self-hosting isn’t about nostalgia for physical servers. It’s about control, predictable costs, and avoiding vendor lock-in that can kill your margins.
Predictable workloads with steady resource requirements often cost less self-hosted. If you’re running the same workload 24/7 for years, paying cloud premiums for flexibility you don’t use is like buying a sports car for commuting in traffic.
Data sovereignty and compliance requirements can make cloud adoption legally impossible or prohibitively complex. Some industries and geographies have regulations that effectively require self-hosting, regardless of cost or convenience.
Tight margin businesses can’t absorb cloud markups indefinitely. If you’re competing on price and cloud costs are 40% of revenue, those economics don’t work long-term. Self-hosting might be the difference between profitability and venture capital dependency.
Technical teams with existing expertise shouldn’t ignore their competitive advantage. If you have senior engineers who understand hardware, networking, and systems administration, that knowledge has value. Cloud simplifies operations, but it doesn’t eliminate them—it just moves them to a different abstraction layer.
Privacy-focused applications face an inherent tension with cloud providers who profit from data analysis and advertising. If your value proposition includes “we don’t spy on you,” running on infrastructure owned by companies whose business model is surveillance creates credibility problems.
The Hybrid Reality Most People Live In
Here’s what nobody talks about: most successful companies end up with hybrid approaches that evolved organically rather than being architected from day one.
You might run your core application self-hosted for cost and control while using cloud providers for content delivery, email services, and disaster recovery. Or start everything in the cloud for speed, then migrate high-volume, predictable workloads to owned hardware as you scale.
The key is avoiding ideology and focusing on the actual costs—both obvious and hidden ones.
“Hidden costs aren’t just financial. They’re also opportunity costs, operational complexity, and vendor dependencies that might not matter today but could strangle your business tomorrow.”
Making the Decision That Sticks
The best infrastructure decisions aren’t based on what’s trendy or what worked for someone else’s completely different business. They’re based on honest assessment of your constraints, capabilities, and goals.
Ask yourself: What happens if your costs double? What happens if a critical service gets discontinued? What happens if you need to scale 10x in six months? What happens if you need to comply with new regulations?
The right answer is the one that gives you the most options when those scenarios play out. Sometimes that’s cloud flexibility. Sometimes it’s self-hosted control. Often it’s a mix that hedges your bets.
But here’s the thing about that flooded server room: we had backups, redundancy, and a recovery plan. The infrastructure choice didn’t cause the problem or solve it. Good engineering practices did. Whether you’re clicking “Launch Instance” or racking servers, the fundamentals remain the same.
Same rules for everyone. Make choices based on evidence, not evangelism. Your business will thank you for the boring practicality.
Scrivener.PRO 