🎬 This article is a companion to my YouTube video. Watch it here:
Introduction
Every great web application with millions of users has an even greater back end — and it has to be. Accessing your app over a prolonged period of time will test the integrity, availability, and speed of your back end. Backend technology can be inexpensive, or it can cost you thousands of dollars. So what's the deal here?
Let me warn you that this channel is highly opinionated. I am sharing the tools that I use and how I use them.
For my back end that powers my web apps, I use Directus for my headless CMS, supported by a PostgreSQL and Redis database, hosted on a VPS, and managed by Coolify. Wow, that is a mouthful — and in this series we will explore how they all work together.
So let's tackle each technology one at a time, starting with the VPS.
What is a VPS?
A Virtual Private Server, known as a VPS, is a virtual environment created on a physical server. Think of it like an apartment building — everyone shares the same physical structure, but each unit has its own private space, utilities, and security.
While multiple VPS instances share a physical server, be careful not to confuse this with shared hosting. Each VPS is allocated its own dedicated resources, which are restricted to that VPS for as long as it is active. Therefore, the performance of a VPS is not directly affected by the usage of other VPS instances, but rather by the underlying performance of the physical server itself.
What are the Benefits of a VPS?
There are several benefits to consider when deciding on virtual private server hosting:
- Greater control — Compared to shared hosting, you have root access and can fully customize your server environment.
- Dedicated resources — Allocated CPU, memory, and storage help ensure consistent performance.
- Scalability — You can easily scale resources up or down to accommodate changing traffic and application demands.
- Cost-effectiveness — A VPS typically offers a balance between the affordability of shared hosting and the power of a dedicated server.
- Improved security — Isolation from other users on the same physical server enhances security.
- Choice of operating system — You can choose the operating system that best suits your needs, such as Linux or Windows.
How Does it Stack Up Against Vercel or Netlify?
Vercel
Vercel offers minimal setup with Git integration and fast deployment right out of the box. It has a free Hobby plan, but it is strictly for personal, non-commercial use. Once your app grows and needs to scale, you will need to move to a paid plan.
The Pro plan starts at $20 per user per month, and also covers serverless functions. Despite the name, serverless code still runs on a physical server — however, the infrastructure management, such as scaling, security patching, and provisioning, is handled entirely by the cloud provider.
The main factor to watch carefully is cost. Vercel uses usage-based billing, and costs can escalate quickly — especially since Turbo build machines became the default for new Pro projects in February 2026, at $0.126 per build minute. A moderate team workflow can generate over $400 per month in build costs alone, before bandwidth and compute charges. I have seen some alarming Vercel bills shared online by customers, which means you need to fully understand the pricing model before you commit.
Netlify
Netlify has historically been more suited to static sites and composable web applications. Composable applications are software systems built from independent, interchangeable modules rather than a single rigid codebase. Netlify also has Git integration, customizable build plugins, and serverless functions.
Netlify moved to a credit-based pricing model in September 2025, designed to simplify metered billing. As of April 2026, the Pro plan costs $20 per month and now includes unlimited team member seats, which is an improvement over the previous per-seat model. However, teams working on active projects with real traffic can burn through their credit allocation quickly, and credit pack add-ons at $10 per 1,500 credits mean teams can regularly spend $40 to $80 or more per month beyond the base subscription. Your overall control is also more limited compared to a VPS, and you will still face a monthly cost as your app grows.
The VPS
VPS prices can grow as your app grows, but in my experience at a slower and more predictable rate — with no surprise charges. However, if you manage a VPS yourself, it requires understanding web servers, firewalls, operating systems, caching, and more. It can get complex very quickly and may cause you to spend more time managing the server than building and scaling your app.
That is why some developers and business owners hire a team to handle it. Small teams may not have the budget for a dedicated infrastructure team, so they often opt for a more convenient managed solution.
Coolify — The Game Changer
There is one tool that I think is worth mentioning and is a genuine game changer — and that is Coolify.
Coolify is a self-hostable platform that makes managing your VPS significantly easier. It offers:
- ✅ Git integration
- ✅ Dockerized container deployments
- ✅ Automatic HTTPS
- ✅ Built-in web server with no manual configuration required
This makes the VPS a very real and competitive option worth considering. If you choose a solid hosting provider and pair it with the right tools, you can make this an absolute dream to work with.
Now don't get me wrong — even with Coolify there are some configurations you will have to make. But I do believe a VPS is a great solution for a startup, mid-size, or enterprise scaled app with the right tools.
Conclusion
Stay with me in this series and we will definitely explore the possibilities. See you in the next video.
References
- Google Cloud — What is a VPS
- AWS — What is a VPS
- IBM — VPS
- Scala Hosting — VPS Explained
- DreamHost — Beginner's Guide to VPS
- Vercel Pricing
- Netlify Pricing
- Bejamas — Self Hosting vs Vercel and Netlify
🔔 Subscribe to my YouTube channel for the full series on building a modern web app back end from scratch.
Top comments (0)