10 posts tagged with "paas"

Usage-based pricing always looks cheap on the signup page. "Pay only for what you use." "Starts at $5." Then a few months in, your bill is double what you guessed, and you can't really point at the one thing that did it.

I've been comparing platforms a lot lately – partly because I run one, partly because people keep emailing me to ask whether X or Y is cheaper than Hostim. So here's the actual math on why metered hosting drifts upward over time, and the honest version of when it's the better deal anyway.

Most small teams hit the same question at some point: should we move to Kubernetes? The honest answer for the majority of them is no, but that answer alone is not very helpful. So here is the longer version, with real prices and a clear line where the answer flips to yes.

Heroku just said it's moving to a "sustaining engineering" model.

That's corporate speak for:

• No big new features
• Focus on stability and security
• No new enterprise contracts
• Maintain what exists

Heroku isn't shutting down.

But it's not a growth product anymore.

I haven't posted updates for a while, but several core features landed on Hostim.dev recently.

Instead of shipping from a fixed roadmap, I'm following support-driven (customer-driven) development: features move to the top of the queue once users actively need them.

Over the past month, this resulted in three practical additions around Docker CI/CD, GitHub Actions deployment, and secure bastion host access.

📌 Last week, I wrote about Cloud Rent in Action – how layers of middlemen drive up the cost of running a simple SaaS stack. Netlify's new pricing update feels like the same story, playing out live.

When you pay for cloud hosting, you're not just paying for compute. You're paying rent. And it adds up fast.

Building a PaaS as a solo founder means making choices. Some deliberate, some accidental, all of them tradeoffs.

Every tool comes with pros and cons, and the deciding factor is usually the most expensive resource of all: time.

If I can get the job done with something I already know, I'll take that path. I'll learn new tools when the project pays for it. Until then, it's all about moving forward with what works.

Here's how Hostim.dev is put together today – the stack that runs every app, database, and service behind the scenes.

Most side projects start the same way. You grab a VPS from Hetzner or DigitalOcean, install Docker, run docker compose up, and boom – you're live.

It feels cheap. It feels simple. Until it isn't.

When you talk to enough developers about how they deploy projects, a few patterns start to emerge. Some are obvious in hindsight, others caught me completely off guard.

Here are my biggest takeaways so far.

These days, hosting your app often means choosing between complexity, lock-in, and sky-high pricing. Whether it's a shiny new platform or a slick developer tool, most of them are just wrappers around the same old giants: AWS, GCP, and Azure.

And those giants are expensive by design.