A few weeks ago, one of the AI tools I use almost every day announced another pricing change.
Nothing dramatic.
Just one of those emails that starts with:
“We’re updating our plans to better serve our growing community.”
Which usually means:
“You’ll be paying more soon.”
I closed the email and kept working.
But later that night, I started thinking about how many services I was subscribed to.
Not just AI tools.
Everything.
Notes.
Storage.
Productivity apps.
Developer tools.
Design software.
Automation platforms.
Even simple utilities somehow wanted monthly subscriptions now.
At some point, I stopped feeling like I owned software.
I felt like I was renting access to my entire digital life.
And weirdly, I think a lot of developers are starting to feel the same thing.
We Accidentally Outsourced Everything
The modern internet made software incredibly convenient.
Need a database?
Click a button.
Need authentication?
Use a service.
Need analytics?
Use a service.
Need AI?
Use a service.
Need deployment?
Use a service.
For years, this felt like progress.
And in many ways, it was.
But convenience has a strange side effect.
You slowly stop understanding the systems underneath.
I Started Noticing a Pattern
Every few months, something would happen.
A product would:
raise prices
remove features
get acquired
shut down
lock useful functionality behind a higher tier
And every time it happened, I realized I had no control.
The software wasn't mine.
The workflow wasn't mine.
The infrastructure definitely wasn't mine.
I was just borrowing it.
Then AI Made Me Reconsider Everything
This is where things got interesting.
Like most developers, I started experimenting with AI tools heavily.
At first I used entirely hosted services.
Then I discovered things like:
Ollama
Open WebUI
local models
self-hosted workflows
Suddenly a question appeared in my head:
Why am I paying monthly fees for tools that can run on my own infrastructure?
That question led me into a rabbit hole.
The Weekend That Changed My Perspective
One Saturday, mostly out of curiosity, I rented a tiny VPS.
Nothing expensive.
Just a basic Linux server.
Honestly, I expected the experience to be painful.
For years I had convinced myself that servers were for “real infrastructure people.”
Not regular developers.
Not people building side projects.
Not people like me.
I was wrong.
Docker Changed Everything
The biggest surprise wasn't the VPS.
It was Docker.
Five years ago, self-hosting felt intimidating.
Now most things can be deployed with a few commands.
A modern self-hosted stack can include:
AI tools
dashboards
APIs
automation workflows
databases
blogs
Without needing a full DevOps team.
The barrier collapsed.
The First Time Something Worked
I still remember opening my browser and seeing my own service running publicly.
Not on somebody else's platform.
Not through a free tier.
Not behind a startup's pricing model.
My server.
My deployment.
My infrastructure.
That feeling was strangely satisfying.
Much more satisfying than I expected.
Self-Hosting Is Not About Saving Money
This is probably the biggest misconception.
People assume self-hosting is about being cheap.
For some people, sure.
But I think the real reason goes deeper.
Self-hosting gives you something many modern platforms quietly removed:
Ownership.
Not perfect ownership.
But more ownership.
And that feeling matters.
Developers Are Starting to Miss Understanding Their Tools
I think this is one reason self-hosting is growing again.
Not because developers suddenly love configuring Linux.
Nobody wakes up excited to debug firewall rules.
But many developers miss understanding how things actually work.
Modern cloud platforms became incredibly powerful.
But they also became increasingly abstract.
Sometimes it feels like we're building software on top of software on top of software on top of software.
Eventually you start wondering what's underneath.
The Rise of the “Small Server”
One thing I didn't expect was how little infrastructure most projects actually need.
A huge percentage of side projects can run comfortably on a basic VPS.
Especially:
APIs
blogs
AI interfaces
automation tools
personal dashboards
developer utilities
You don't need a cloud architecture diagram.
You need one server.
Maybe Docker.
And some patience.
Why I Still Think VPS Hosting Matters
Not because everybody should become a sysadmin.
Not because SaaS is bad.
Not because cloud platforms are evil.
But because running your own services teaches you something important.
It reconnects you with the internet.
The internet stops feeling like a collection of products.
And starts feeling like infrastructure you can actually participate in.
Recently I've been experimenting with small self-hosted projects on platforms like DigitalOcean and Vultr, and honestly both made the process much easier than I expected.
DigitalOcean:
Vultr:
Maybe That's What Developers Are Really Looking For
Not cheaper software.
Not more dashboards.
Not another AI subscription.
Maybe we're looking for something simpler.
A feeling that we still understand the technology we're building on.
A feeling that some part of our digital life still belongs to us.
Maybe that's why self-hosting is growing again.
Not because developers are moving backward.
But because they're trying to reconnect with the systems they've spent years abstracting away.
And honestly?
The moment you deploy your first service on a server you control, that feeling starts making a lot more sense.
Top comments (0)