Your Side Project Shouldn’t Cost More Than Your Netflix Subscription

If you’ve been deploying web apps for a year or two, you’ve probably noticed something: your hobby project with 200 monthly visitors costs $40 to host. Your streaming services cost less. Your phone bill costs less. Something feels off, but you’re not sure what the alternative is. Here’s what nobody told you: there’s another way to run your apps, and it’s been hiding in plain sight.

Two Paths to the Same Place

There are two distinct types of web developers today, and they might as well be speaking different languages. Your journey probably looked like this: learned HTML and CSS, picked up JavaScript, built something in React, deployed to a platform with a few clicks. Infrastructure meant clicking “Deploy” and adding environment variables in a dashboard. You’ve shipped real projects. You understand components, state management, API design, databases. You’re a capable developer.

But you’ve never opened a terminal to SSH into a server. You’ve never installed Postgres from the command line or set up a cron job manually. You’ve never thought about firewalls or backup scripts. And why would you? The platforms you learned on abstracted all of that away.

Then there’s another group of developers who grew up on shared hosting, cPanel, and bare servers. They’ve been running ssh root@server and apt-get install for years. To them, platforms are nice wrappers around things they already understand. When they see posts about managed platforms, they think: “That’s just a Linux server with a pretty interface.”

How You Ended Up Here (And Why That Made Sense)

This isn’t about anyone making the wrong choice. The path you took was actually quite rational. Bootcamps and tutorials optimized for speed. Their goal was to get you from zero to deployed application as fast as possible. Teaching you React and deployment platforms got you there. Teaching you SSH, systemd, and server management would have taken months longer.

The abstraction worked. You built real things. You learned valuable skills. You got jobs. The fact that you didn’t learn server administration wasn’t holding you back—until maybe now, when you’re looking at your hosting bills. The defaults pointed you here. Framework documentation integrates with managed platforms. The “Deploy” button is right there in your dashboard. The alternative—renting a server and configuring it yourself—isn’t mentioned in tutorials. It’s buried in blog posts and documentation that assumes you already know what you’re looking for.

Fear seemed reasonable too. When you heard terms like “VPS” or “self-hosted,” you probably thought about security hardening, manual updates, backup strategies, and the nagging worry that if something breaks, it’s your fault. That sounds scary when you’ve never done it. Managed platforms sold you peace of mind, and that was worth paying for.

What the Other Path Knows

Here’s what that other group of developers understands that you might not: a server is just a Linux computer you rent by the month. That’s it. A VPS (Virtual Private Server) is not magic. It’s not dramatically different from running Ubuntu on an old laptop. You get a Linux machine, you install the software you need, and you run your application.

The cost difference is real. A typical setup on managed platforms might run you $20-40 for hosting, another $15-25 for a managed database, and $5-10 for object storage. That’s $40-75 per month total. The same stack on a budget VPS costs $10-20 per month for a server with 4GB RAM and 2 CPUs, and everything else runs on that same server. For a side project or small application, you’re paying three to four times more for convenience.

The “scary” parts aren’t that scary either. You already know how to read documentation, follow tutorials, debug problems, and search Stack Overflow when stuck. Server management is just another technical skill. It’s not mysterious. You learned React—a constantly-shifting ecosystem with breaking changes every few months. You can learn Docker and basic Linux commands.

And it’s not all-or-nothing. You don’t have to become a systems administrator. You don’t have to manage production infrastructure for a thousand users. You can run your side projects on a VPS, keep your day job deployments on managed platforms, and learn gradually, one service at a time.

Why This Gap Exists (And Why It Matters)

Every few months, someone posts about moving their stack from managed platforms to a budget server, and the internet loses its mind. Half the replies are asking “Wait, you can do that?” while the other half wonders “How did people not know this?”

These posts go viral because they’re speaking to two audiences at once. One group discovers that the default path isn’t the only path, that they’ve been paying a premium for convenience they might not need, and that they’re allowed to run their own infrastructure without it being as impossible as it seemed. The other group finally sees validation that what they’ve known all along is worth talking about. They get to be helpful, share knowledge, and maybe feel a little bit smug. Both groups feel seen. The post validates their perspective while revealing that another perspective exists.

There’s a business opportunity hidden in this gap. Smart people have noticed this divide and built products around it. They’re telling developers they don’t have to overpay for managed services, offering an opinionated and safe path to running their own infrastructure, and promising to handle the scary parts like backups, SSL certificates, and updates. Tools like Coolify, CapRover, and Dokku exist in this exact space. They’re not trying to replace server knowledge—they’re packaging it into an interface that feels familiar to the platform generation.

This is why the gap matters. There’s value in understanding both approaches, even if you stick with what you know.

When It Makes Sense to Cross Over

Stick with managed platforms if you’re building something for customers and need reliability guarantees, if your time is worth more than the money you’d save, if you’re already profitable and the monthly cost doesn’t matter, if you want someone else on call when things break, or if you need features like one-click rollbacks and built-in monitoring.

Consider learning the VPS route if you’re running side projects that are bleeding money, if you want to understand what’s actually happening under the hood, if you’re curious about how the pieces fit together, if you want marketable skills that differentiate you, or if you like having full control over your stack. The real answer is that you can do both. Use managed platforms for work. Run your side projects on a server. Learn gradually. There’s no purity test here.

What You’d Actually Need to Learn

If you’re curious about the VPS path, here’s what the learning curve actually looks like.

You’d need to get comfortable with basic Linux commands for navigation and file management, learn SSH and key-based authentication, understand Docker and docker-compose for running services, pick up Nginx or Caddy for routing traffic, work with environment variables and configuration files, and grasp basic security concepts like firewalls, updates, and SSH hardening. Beyond that, knowledge of backup strategies, monitoring and logging, database management, and SSL certificate automation would be helpful but not immediately necessary.

The time investment is a few weekends to get comfortable and a few months to feel confident. It’s a marathon, not a sprint. Start by renting a cheap server from any provider, follow a tutorial to deploy a simple app, break things and fix them, and add one service at a time. The infrastructure knowledge you’d gain doesn’t replace what you already know—it adds to it. And honestly, learning how servers work makes you appreciate managed platforms more when you do use them.

The Real Takeaway

Neither path is wrong. If you’re building a business and managed services let you focus on your product instead of your infrastructure, that’s often the right call. If you have the time and curiosity to learn server management, that’s valuable too.

The issue isn’t that you chose managed platforms. The issue is that you might not have realized there was a choice at all. You’re allowed to run your own infrastructure. You’re allowed to SSH into a server, install what you need, and deploy your apps. You’re allowed to save money. You’re allowed to learn these skills.

You’re also allowed to stick with what works. But now you know: there’s a door that was always unlocked. Whether you walk through it is up to you. And in the gap between these two worlds between the developers who know this and the developers who don’t there’s opportunity, education, and a lot of strongly-worded threads on the internet. Welcome to both sides of the conversation.