Leaving the cloud: every objection answered (even 'who runs it at 2am?')
Read any “should I leave the cloud?” thread and you’ll watch the same objections roll in — I just went through a 96-comment r/devops one, and every single one was there:
Here’s what’s true and what’s missing: every one of those objections is correct — and every one is an objection to running a server in a closet, one box you personally babysit. They quietly assume a false binary: the hyperscaler, or a machine under your desk. There’s a third option the objections skip, and it answers all of them. Let me take them one at a time, honestly.
”Who patches it? Patching is daily now.”
Real — and mostly not your problem in the setup I’m describing. The win isn’t running everything by hand; it’s flat-rate managed services (managed Postgres, managed OS, zero-egress storage) plus a person who does the patching for you. For the rest, a small business genuinely does run fine on automated updates and a scheduled reboot — one commenter’s “cron job and a weekly reboot” ran servers for years. You don’t need a NASA change-management process to keep a website and a database patched.
”The 2am disk swap — hardware fails.”
Also real. Over five to seven years a drive will die; that’s a near-certainty, not bad luck. The answer isn’t “hope” — it’s redundancy (RAID, a spare) and a provider whose job is the physical layer. On a rented OVH/Hetzner box, they swap the failed drive under SLA — you’re renting a datacenter, not driving to a closet at 2am. The “you’ll be the one swapping drives” objection is an objection to owning the metal. Don’t own the metal; rent it.
”Single point of failure, no redundancy, no multi-AZ.”
True if you run one box in a closet. A tier-3 datacenter box has redundant power and network by default, and 99.9% is very achievable. Need more? A second box, or — as the sharpest comment in that thread put it — use the cloud as your DR target, so you get a fallback without paying for standby compute 24/7. You keep the cheap flat-rate box for the steady load and rent resilience only where you actually need it.
Don't own the metal; rent it.
”You need expensive staff — and if they leave, brain drain.”
This is the biggest real one, and the honest one — the person who posts these threads is usually also the single point of failure, doing the designing, deploying, and maintaining alone. The answer is not “hire and retain a platform engineer” (expensive, and they can leave). It’s rent the owner — that’s the whole managed model. One person whose job is to run it, keep it boring, and hand you documented, standard, open-source infrastructure you own outright. No brain drain, cancel anytime, no lock-in to me.
”Ops time isn’t free even if you don’t bill it.”
Correct, and I say it louder than the skeptics: “zero ongoing cost” is a myth — someone always runs the servers. That someone’s time is a real cost. The difference is that in a managed plan it’s priced explicitly and it’s mine, not an invisible tax on your evenings. You’re not pretending the work disappeared; you’re paying a fixed, honest number for it instead of an unbounded, growing cloud bill.
The objection they never quite say out loud
Underneath all of them is a real one: cloud is flexibility, not savings. And that’s exactly right — if your workload is bursty or seasonal, if you need multi-region, if you can genuinely scale to zero, cloud can be cheaper and you should stay. This whole argument is only about steady workloads — the website, the database, the file storage, the traffic that just needs to be up. For those, the room’s own consensus was blunt: on-prem or flat-rate wins, especially anywhere you’d pay egress fees repeatedly.
The third option
So: not hyperscaler, and not a closet. Flat-rate managed infrastructure — a datacenter box someone else owns, powers, cools, and fixes, that I run for you. Every objection on that list is an objection to the closet, and every one is answered by managed. The reason the answer is managed and not DIY isn’t that the objections are wrong. It’s that they’re right — so you shouldn’t be the one holding them.
If you’ve been told leaving the cloud means babysitting a server at 2am, that’s the objection I exist to remove — I run flat-rate managed infrastructure so the objections are mine, not yours. And if your workload is spiky or the risk isn’t worth it, I’ll tell you to stay. Every message comes straight to me — I read and reply to each one myself, usually within a day, and what readers send shapes what I build next. It’s just me for now, so that’s genuinely true; it won’t be forever. Send me your setup and I’ll tell you honestly whether the objections outweigh the savings for you — free, within a business day.