Cloud & Hosting
Choosing hosting for a web app: managed platform, VPS or full cloud
Three ways to host a web application, what each one really costs you, and how to tell which fits your project.
Codexan
6 min read
Hosting decisions are usually made in the first week of a project and regretted in the second year. The options look similar on a pricing page and behave very differently once real users arrive. Here is how we explain the choice to clients.
The three options
A managed platform (Vercel, Netlify, Render, Railway and similar). You push code, the platform builds and serves it. There are no servers to patch.
A virtual private server (a VPS from providers such as Hetzner, DigitalOcean or Linode). You rent a machine and run everything on it yourself.
A full cloud account (AWS, Azure or Google Cloud). You assemble your own platform from dozens of building blocks: compute, databases, queues, networking.
What each one costs you
The monthly bill is the smallest part of the cost. The larger part is the time somebody spends keeping it running.
| Managed platform | VPS | Full cloud | |
|---|---|---|---|
| Setup time | Hours | Days | Days to weeks |
| Ongoing maintenance | Almost none | Yours: updates, backups, security | Yours, plus the platform you built |
| Cost at small scale | Low or free | Very low | Low, but easy to get wrong |
| Cost at large scale | Can climb steeply | Predictable | Efficient if managed well |
| Flexibility | Limited to what the platform supports | Anything a server can do | Almost anything |
When a managed platform is right
For marketing sites, content sites and most early-stage web apps, start here. Deployment is automatic, previews exist for every change, and scaling is somebody else's problem.
Watch for two things. First, usage-based pricing: a traffic spike or a badly written loop can turn into a bill. Set spending limits on day one. Second, background work: long-running jobs, websockets and heavy processing often do not fit the platform's model and need a second home.
When a VPS is right
A VPS suits steady, predictable workloads where you want a fixed price: an internal tool, a small product with known traffic, anything that needs a long-running process. It is the cheapest way to run real software.
The trade is responsibility. Operating-system updates, firewall rules, backups and restoring from those backups are now your job. If nobody on the team owns that, the server will quietly become a risk.
When full cloud is right
Choose AWS, Azure or Google Cloud when you have requirements a platform cannot meet: private networking, strict data-residency rules, unusual workloads, or a scale where owning the architecture pays for itself. It is also the right choice when your customers' security questionnaires expect it.
Do not choose it because it sounds more serious. A cloud account with no one managing it is more expensive and less secure than a managed platform.
A sensible default
- Start on a managed platform with a managed database.
- Keep the application portable: standard runtimes, configuration in environment variables, no platform-specific tricks you cannot replace.
- Move the parts that outgrow the platform, when they outgrow it, not before.
Most projects never need step three. The ones that do will know exactly why, which makes the move far easier to plan.
Questions worth answering first
- Who will be woken up if it goes down, and can they fix it?
- Where does the data have to live?
- What does a month with ten times the traffic cost?
- How do you restore yesterday's data, and has anyone tried?
If those four have clear answers, the hosting choice usually makes itself.
- hosting
- cloud
- aws
- vercel
- vps