From Shared Hosting to a Slice of Pizza: How AI Made Running My Own VPS Practical (Part 1)

For years, shared hosting made perfect sense for me.

I have several websites. Most of them run WordPress. I’m not operating Netflix, Amazon or some giant web application. I’m a guy with a collection of websites for my businesses, projects, writing and assorted ideas that seemed like a good idea at the time.

Shared hosting was inexpensive, convenient and, most importantly, somebody else worried about the server.

Then I started wanting more.

More performance. More control. Fewer mysterious slowdowns. The ability to actually see what was happening when something went wrong instead of opening a support ticket and waiting for someone on the other side of the world to investigate it.

That eventually led me down the VPS rabbit hole.

And oddly enough, it started with pizza.

I Just Wanted a Slice

While comparing VPS providers, I came across InterServer. Instead of describing its VPS plans strictly in terms of packages, it sells resources in what it calls “slices.”

I immediately loved the analogy.

Think of a big physical server as a pizza. Virtualization allows that machine to be divided into smaller virtual servers. I don’t need the entire pizza. I just need my slice. 🍕

InterServer currently sells its basic VPS resources that way, starting with a small slice and letting customers add more as they need them. It even offers storage-optimized slices with 1 TB of storage for $3 per month, specifically intended for things such as backups and archives.

I ultimately did not choose InterServer for my production VPS.

But the pizza-slice idea stuck in my head.

I had decided I wanted my own slice of the Internet.

Why Leave Shared Hosting?

There is nothing inherently wrong with shared hosting.

For millions of websites, it is exactly the right product. It handles server administration, operating-system maintenance and much of the ugly infrastructure work while giving you a convenient control panel.

For someone running a small business or a personal website, that has traditionally been a fantastic trade.

The problem is that you are sharing more than just a server.

You’re also sharing decisions.

The hosting company decides how the server is configured, what limits are imposed, how resources are allocated and what you are allowed to change. When something goes wrong below the WordPress level, you frequently have to ask the hosting company to fix it.

And then you wait.

I had also reached the point where I understood enough about WordPress, DNS, Cloudflare, caching and web hosting to know when the server itself was becoming part of the problem.

A VPS offered something shared hosting couldn’t give me:

control.

Of course, control comes bundled with responsibility.

Not Easy. Manageable.

I don’t want to give anyone the impression that moving from shared hosting to a VPS is easy.

It isn’t.

But I’ve discovered that it is manageable.

Those are two very different things.

I deliberately took my time. I have several websites, and moving all of them at once would have been easy enough technically. That wasn’t the goal.

The goal was to make sure I understood what I was building well enough to maintain it after the excitement wore off.

So I started small.

I set up the VPS. I installed the control panel. I learned how the web server was configured. I moved one website. I watched it. I tested things. I worked on security. I built backups. I made mistakes. I fixed them.

Then I left it alone long enough to see whether it stayed healthy.

Only after I became comfortable with the system did I start thinking about moving more sites.

That methodical process matters to me.

I don’t want a server full of clever things I don’t understand. I want something I can look at six months from now and still know why it was configured that way.

My rule has become the old KISS principle: Keep It Simple.

Production should be boring.

If I get the urge to experiment with something strange, I can always buy a $3 pizza slice somewhere and break that instead.

AI Changed the Equation

Here is the part I think is genuinely significant.

I would not have attempted this five or ten years ago.

Running your own Linux VPS isn’t a new idea. Linux isn’t new. Nginx isn’t new. SSH, firewalls, databases, DNS and SSL certificates certainly aren’t new.

What changed is my ability to get help understanding all of them.

AI tools have made VPS administration practical for someone like me in a way that it simply wasn’t before.

That does not mean I tell an AI, “Run my server,” and blindly accept whatever it does.

Quite the opposite.

AI has become a translator between me and systems that previously required considerably more specialized knowledge.

I can show it an error message and ask what it means. I can ask why a configuration file contains a certain directive. I can have it explain a firewall rule before I enable it. I can ask it to check a command before I run it. I can paste logs into it and have it help identify what actually matters.

Instead of spending three hours bouncing among documentation, Stack Overflow posts from 2014 and forum discussions where half the answers contradict the other half, I can start with a conversation.

I still have to make the decision.

I still have to understand enough to know whether the answer makes sense.

And ultimately, if I break the server, it’s my server.

AI didn’t make system administration easy.

It made learning system administration while actually doing it practical.

For small businesses and technically curious home users, I think that changes the economics of web hosting in a meaningful way.

Apache, Nginx and the Sphinx in My Head

One of the changes I made was moving from Apache to Nginx.

Then I learned Nginx is pronounced “Engine X.”

I had been calling it “N-jinx.”

Apparently I wasn’t alone. The Nginx community even has a cat mascot named Jinx, named after that common mispronunciation.

So technically I was wrong, but apparently wrong enough to have an official mascot.

The difference between Apache and Nginx gets technical quickly, but the short version is that they approach web traffic differently.

Nginx uses an event-driven model designed to handle many connections efficiently. Its own documentation describes a master process managing worker processes, with those workers using event-based mechanisms to process requests.

Apache is extremely flexible and has traditionally been especially convenient in shared-hosting environments because individual websites can modify behavior through .htaccess files without needing access to the main server configuration. Apache’s documentation specifically describes .htaccess as decentralized, per-directory configuration.

With Nginx, more of that responsibility moves into the server configuration itself.

That initially feels a little more “server administrator-ish.”

But once I understood what was happening, I actually liked it.

Apache was familiar and flexible.

Nginx felt more direct.

And now that I know how to pronounce it, I have one fewer mythical creature involved in running my websites.

A Little More Money, a Lot More Hosting

I originally hoped moving away from shared hosting might save me a little money.

It didn’t.

I was paying Hostinger about $13.99 a month. My new setup works out to roughly $18.80 a month once I include the VPS, rolling backups, snapshots, off-site backup storage and a separate email service.

So I’m spending about $5 more per month, or roughly $60 more per year.

I can live with that.

Cheap hosting is easy to find. There is always somebody willing to sell you another hosting plan for a few dollars a month.

Good hosting is harder.

What I really wanted was a setup that worked well and made things smoother. I wanted the sites to load quickly, backups I could trust, email handled separately, and enough control that when something went wrong I could actually figure out what was happening.

Somewhere along the way, the goal stopped being “spend less on hosting” and became “build a hosting setup that works better.”

For that extra $60 a year, I get dedicated VPS resources, more control over the server, multiple layers of backup, independent email service and noticeably better performance.

Sometimes an upgrade isn’t about spending less.

Sometimes it’s about getting a lot more for a little more.

Why Not Just Use Hostinger’s VPS?

The obvious next step would have been to stay with Hostinger and move from shared hosting to one of its VPS plans.

And to be fair, I don’t have any major complaints about Hostinger. I had a few minor reservations here and there, but the same could be said for every shared-hosting company I’ve used over the years.

My biggest concern was pricing—especially the long-term renewal price and the commitment required to get the attractive advertised rates.

I was still figuring out whether I even wanted to manage a VPS. Committing to 12 or 24 months just to get a good price didn’t make much sense when there was a very real possibility I could spend a few weeks doing this and decide, “Nope. Put me back on shared hosting.”

I wanted a decent monthly price without a long commitment. That gave me room to experiment, learn, and walk away without feeling like I had paid for a year or two of something I didn’t want.

Once I started comparing providers on that basis—not just the introductory headline price—OVHcloud became much more attractive.

If I was going to take on the responsibility of managing a VPS anyway, I wanted to choose the provider and setup that made the most sense for me, not simply the one that was easiest to upgrade to from my existing account.

So this wasn’t really about leaving Hostinger because they were bad. They aren’t.

It was about giving myself the freedom to try something different without locking myself into it.

When Things Go Wrong

A VPS is not for the faint of heart, and I would be cautious about choosing one based on price alone.

Cheap VPS hosting is everywhere. The harder question is what happens when the shit hits the cooling fan.

What happens when a drive fails? When the host node has a hardware problem? When the network goes down? When there is a power issue? When you accidentally break your own configuration at two in the morning?

That is when the difference between cheap hosting and good hosting becomes important.

With a VPS, some problems are yours to solve. That comes with the territory. But I still want the infrastructure underneath my virtual server to be professionally operated, redundant and backed by a company that knows what it is doing.

I do not need the cheapest server on the Internet.

I need one I can reasonably expect to still be there when something goes wrong.

Would I Recommend a VPS?

Not to everyone.

If you want to install WordPress, write posts and never think about Linux, Nginx, firewalls, databases or backups, shared hosting remains an excellent product.

There is real value in paying somebody else to worry about the server.

A VPS carries more risk.

I can make a mistake that I simply could not make on shared hosting. I can misconfigure the web server. I can lock myself out. I can break PHP. I can mess up permissions. I can run a command with far more authority than I intended.

That responsibility is real.

But so are the benefits.

I have more control over performance and security. I can see what the server is doing. I can choose how things are configured. If something goes wrong, I can investigate it instead of immediately waiting for a support ticket.

And because I have built a backup system I understand, even a catastrophic server failure should ultimately become a restoration problem rather than a losing-everything problem.

The cost isn’t dramatically different from what I was already paying for good shared hosting.

The difference is that I now own the responsibility along with the control.

Five or ten years ago, that trade would not have made sense for me.

Today, with AI tools helping me learn, troubleshoot and understand the systems I’m administering, it does.

I still wouldn’t call running a VPS easy.

But I will call it manageable.

Where Does the Internet Actually Live?

Once the VPS was running, I started wondering where all of this actually lived—the production server, the backups, the data centers, all of it.

What I found was fascinating enough to become its own article: Part 2: Where My VPS Actually Lives — and the Nuclear-Powered One I Want.

For now, though, I finally have what I set out to get:

my own little slice of Internet pizza. 🍕