For the past few years, it feels like if you aren’t deploying your app on Vercel, Heroku, or using twenty hyper-managed AWS services, you’re falling behind. Everyone sells you “serverless” as the magic bullet to launch your product without complications, without worrying about infrastructure, and with the promise of paying only for what you use.
Honestly, I’m getting tired of it.
The “pay only for what you use” theory looks great in pitch decks and funding rounds. It’s the perfect sales pitch. You push your code to a magic platform, click “deploy,” and voilà, your app is live without you having to configure a single server. It feels like magic, and that’s exactly what they’re selling you.
The Hangover
But then, reality hits. Your product starts gaining traction, traffic spikes, and you start getting thousands of visits. You should be celebrating, but instead, you’re terrified thinking about the invoice that’s coming at the end of the month.
You’re paying for every executed function, for every database query, for every gigabyte of bandwidth. You are paying the “Cloud Tax.” And that tax isn’t cheap. It can eat up a massive chunk of your revenue, especially if your product is successful.
“Serverless” is just a very clever marketing term meaning your code runs on someone else’s computer, and they are going to charge you a premium for every single interaction your app has with their infrastructure. Ultimately, you are penalizing your own success. Your profit margin has a hard ceiling imposed by your hosting provider.
The Silent Hijacking of Your Architecture
But it doesn’t end there. There is also the architecture issue. When you use serverless services, you are coupling your app to a proprietary architecture. You are designing your product to run in a highly specific environment, with its own set of limitations and costs.
If they decide to hike their rates tomorrow, you can’t simply switch providers; instead, you find yourself having to refactor your codebase to adapt it to a new platform. You’ve outsourced your architecture and tied your own hands, leaving yourself at the mercy of a vendor who can change the rules of the game at any moment.
I’m not saying we should go back in time and rack physical servers in the office. But I do believe it’s critical to be aware of the limitations and hidden costs of “serverless.” It is a convenient solution for launching quickly, but it’s not a silver bullet for every scenario. If your product succeeds, chances are you’ll have to rethink your architecture and migrate to a more traditional solution to keep your costs under control.
The ROI of Getting Your Hands Dirty and Digital Sovereignty
A well-configured VPS, a Dockerized environment, and a finely tuned Nginx, on a €40-€80/month server, can handle the exact same traffic as a magic one-click platform that would cost you significantly more. Yes, it requires rolling up your sleeves, fighting with the terminal, understanding systems, dealing with containers, and forgetting about shortcuts. But the peace of mind of knowing your operating costs are fixed, no matter how much you sell, is priceless.
Extreme convenience is a luxury you can afford when validating an idea with zero users. But when things get serious, predictability and absolute control over your data and infrastructure are everything. If your server bill is growing at the same rate as your customer base, you don’t need to increase your revenue; you need a real architecture.
If you own your brand, start owning your infrastructure.