Why I Left Managed Hosting

For years I used managed WordPress hosting. The pitch is simple: we handle the server, you handle the website. Sounds reasonable. And for a while, it was.

Then I started building things that needed more than a WordPress admin panel.


The hotel problem

Managed hosting is like a hotel. Everything is taken care of. The bed is made, the wifi works, the lights turn on. You don't think about plumbing.

Until you need to change something.

I needed to reset PHP's opcode cache after a deploy. Couldn't. The host locked it down. I needed to restart a process after a code change. Couldn't. I needed to SSH in and run a single command. Couldn't -- or could, but through a support ticket that took hours.

Every time I hit a wall, the answer was the same: "That's not available on your plan." Or: "We'll look into it." Or silence.

I was paying for convenience, but the convenience disappeared the moment I needed anything beyond the basics.


What I actually needed

I run multiple WordPress sites. I also run Node.js applications, APIs, and background services -- all on the same machine. Managed hosting doesn't do that. You get WordPress and nothing else.

What I needed was a server I could actually use. Full SSH access. Install what I want. Run what I want. Restart what I want.

The word for that is "unmanaged VPS." And for most people, that's where the story ends. Nobody wants to configure Nginx and PHP-FPM by hand. Nobody wants to manage SSL certificates and database backups and firewall rules and PHP version upgrades manually.

That's where SpinUpWP comes in.


The layer that changes everything

SpinUpWP is a server management panel built specifically for WordPress. You point it at your VPS, and it handles the things that would otherwise require a sysadmin: PHP configuration, SSL certificates, database optimization, automatic backups, security hardening.

Here's what the stack looks like:

Your stack
Your websites WordPress, Node.js, anything
SpinUpWP SSL, backups, PHP, security
Unmanaged VPS Full root access, run anything
Cloudflare DNS, CDN, protection

The key insight: SpinUpWP is not hosting. It's a management layer. It connects to a VPS you own and handles the WordPress-specific complexity. You still have full root access underneath. You can still SSH in, install packages, run whatever you want alongside your WordPress sites.

You get the control of unmanaged with the convenience of managed. That's the whole trick.


What actually changed

BEFORE: MANAGED
Can't reset PHP cache
No real SSH access
WordPress only
No CLI deploys
Support ticket for everything
~EUR 15/mo per site
AFTER: VPS + SPINUPWP
Full cache control
Full SSH access
Run anything
Deploy from terminal
Fix things yourself, instantly
~EUR 42/mo for everything

The managed plan cost me about EUR 15 per month per site. That's fine for one site. I run eleven WordPress sites, plus a handful of Node.js apps and APIs. The VPS handles all of it for EUR 42 total. And I can do whatever I want with it.


Why mijn.host

I wanted a Dutch provider. GDPR compliance matters when your business is in the Netherlands, and I'd rather my servers sit in a Dutch datacenter than route through a US subsidiary.

Mijn.host is small, independent, and run by people who actually respond when you email them. The VPS is fast, the pricing is straightforward, and I haven't had a single minute of unexpected downtime since I moved everything over.

I also write about hosting on Start24.nl, so I put my own infrastructure where my recommendations are. Practice what you preach.

I use mijn.host for all my servers. If you sign up through the link below, I earn a small commission. It doesn't cost you anything extra.

Check out mijn.host VPS

Affiliate link -- I only recommend what I use myself


The boring conclusion

I didn't leave managed hosting because of some ideology about server ownership. I left because it kept getting in the way of my work.

The "unmanaged" option turned out to be easier than the "managed" one, because the right tools make the hard parts disappear. SpinUpWP handles WordPress. PM2 handles Node.js. Nginx ties it together. And I have a single machine that does everything, for less money, with more control.

If you run one WordPress site and never touch the server, managed hosting is perfectly fine. But if you build things -- if you need SSH, or multiple frameworks, or the ability to fix a problem without waiting for someone else -- consider an unmanaged VPS with a good panel on top.

It's not exciting. It just works. And that's the whole point.

If you want to know when I write something new: