If most of your deployment experience comes from platforms like Render, Railway, or Vercel, your mental model of "deploying" probably looks like this:
Push your code to GitHub.
Paste some environment variables into a clean dashboard.
Watch a build log scroll by for three minutes.
Click a *.onrender.com URL that already has HTTPS. It's fast, predictable, and asks you to know almost nothing about what happens underneath your code. I loved it. Then I built something that PaaS couldn't host, and I got a crash course in everything it had been quietly doing for me.
The Project That Broke My Comfort Zone
I was deploying dns-blocker , a project with a Go backend ( nullify ) and a React dashboard, onto an Oracle Cloud Infrastructure (OCI) Always Free VM.
The reason was simple: a DNS resolver needs port 53 and persistent control over the network. Web-focused PaaS platforms aren't built to give you that. So moving to Infrastructure-as-a-Service (IaaS) wasn't an experiment.β¦