If you're searching for unmanaged WordPress VPS hosting Europe agencies actually trust, you already know what you don't need: a "managed WordPress" panel that hides Nginx behind a proxy you can't touch. This post is for the agency dev or ops lead who wants root SSH, a real EU network, and a VPS sized correctly against the number of sites and PHP-FPM workers you're actually running — not marketing tiers dressed up as capacity planning.
Who This Post Is For (and Who It Isn't)
We'll say this upfront because it saves everyone time: if you want someone else to configure Nginx, tune PHP-FPM pools, and patch WordPress core for you, this isn't that. Unmanaged means the box is yours — root SSH, your choice of stack, your cron jobs, your backups. It's built for agencies and freelance devs who already run Nginx + PHP-FPM (or are comfortable learning), and who want to stop paying a per-site markup for hand-holding they don't need on ten client sites they already know how to keep patched.
If that's not you, that's fine — plenty of good managed options exist. If it is you, keep reading, because the math on unmanaged changes completely once you're hosting more than two or three WordPress sites.
Unmanaged WordPress VPS Hosting in Europe vs Managed WordPress: The Real Trade-off
Comparing unmanaged VPS hosting to managed WordPress isn't really about difficulty — Nginx, PHP-FPM, and WordPress are a well-documented stack most agency devs can stand up in under an hour. It's about what you're paying for per site. Managed WordPress hosts price per-site because they're running isolated environments with their own control plane, staff on call, and a support queue behind it. That's a legitimate model for agencies that don't want ops overhead at all.
But if you're already the ops person — if you're the one SSHing in to clear an opcache or debug a plugin conflict anyway — you're paying for an abstraction layer you route around constantly. An unmanaged VPS flips the economics: you pay for compute (RAM, vCPU, NVMe, bandwidth), not per-site licensing, and you can put as many client sites on one box as the resources support.
Sizing the Stack: One Big Box vs Many Small Accounts
Here's the actual planning question agencies need to answer, and it's a capacity one, not a feature one: do you run one bigger VPS hosting multiple client sites behind Nginx server blocks and separate PHP-FPM pools, or do you spin up several small VPS instances, one or two sites each, so a noisy neighbor never touches another client's uptime?
Both are valid — it depends on how much isolation your contracts require and how spiky your traffic gets. Here's how our hourly VPS tiers map to each approach, using only the specs and prices on the plan page:
| Tier | RAM / vCPU / NVMe | Price | Reasonable Use Case |
|---|---|---|---|
| VPS I | 2GB / 1vCPU / 40GB | €4/mo (€0.0056/hr) | Single low-traffic site, staging, or a client's brochure site |
| VPS II | 4GB / 2vCPU / 80GB | €6/mo | 2-3 small WordPress sites with separate PHP-FPM pools |
| VPS III | 8GB / 2vCPU / 120GB | €10/mo | 4-6 client sites, moderate traffic, headroom for object caching |
| VPS IV | 8GB / 2vCPU / 120GB | €16/mo | Same specs as VPS III — an alternate tier some agencies standardize on |
| VPS V | 16GB / 4vCPU / 200GB | €30/mo | One consolidated multi-site box for 8-12+ client sites |
| VPS VI | 32GB / 6vCPU / 400GB | €58/mo | Large agency consolidation, WooCommerce sites, or a shared staging fleet |
The "many small managed accounts" pattern usually means paying a per-site fee on every tier above regardless of actual load. The "one bigger box" pattern means you size once against real PHP-FPM worker counts (each pool eats RAM whether it's busy or not) and pay for compute you actually schedule. For most five-to-fifteen-site agency portfolios, we see VPS III through VPS V hit the sweet spot — enough RAM headroom to run separate FPM pools per client plus a shared Nginx layer, without paying managed per-site pricing on sites that get a few hundred visits a month.
What Actually Determines Sizing (Not Guesswork)
Skip the "how many sites fit on a VPS" rules of thumb — they don't hold across client bases. What actually matters:
- PHP-FPM pool count and pm.max_children per pool — each child process holds memory whether it's serving a request or not; this is usually your real RAM ceiling before disk or CPU matter.
- NVMe I/O, not just capacity — every tier we run is NVMe-backed, which matters more for WooCommerce and membership sites doing constant DB writes than raw GB does.
- Bandwidth model — our tiers are 1 Gbps unmetered symmetric, so a traffic spike from one client site doesn't turn into a surprise invoice for the others sharing the box.
- Deploy and rebuild speed — median deploy across our 41 OS templates is 47 seconds, which matters when you're testing whether a consolidated box or a split setup fits a given client roster before committing.
Cheap Unmanaged WordPress VPS for Agencies: Where the Savings Actually Come From
Keeping an unmanaged WordPress VPS setup cheap for agencies isn't just about a low sticker price — it's billing that matches how agencies actually work: spinning up a staging clone for a client review, testing a migration, then tearing it down. We bill hourly to the second, so a VPS I instance for a two-day staging test costs a few cents, not a rounded-up month. Root SSH and IPv4 + IPv6 come standard on every tier, so there's no "upgrade to unlock SSH" tier tax common on managed WordPress plans.
If a client's site outgrows shared hosting entirely — heavy WooCommerce traffic, or an agency consolidating a dozen sites onto dedicated hardware instead of a VPS — our dedicated servers are the next step up, and the same unmanaged, root-access philosophy carries over: you keep the stack decisions.
How Noded Can Help
We run every VPS tier on NVMe with root SSH from the first boot, so agencies can stand up their own Nginx + PHP-FPM stack exactly the way they already know how to run it — no managed panel forcing a workflow on top. Whether you're consolidating client WordPress sites onto one right-sized box or keeping them split across a few smaller instances for isolation, our VPS tiers are priced and billed hourly so you can test the sizing before committing to it. And if a client's footprint eventually outgrows shared VPS capacity altogether, our dedicated server line keeps the same root-access, no-per-site-fee model on hardware you don't share with anyone else.
FAQ
Is unmanaged WordPress VPS hosting harder to maintain than managed WordPress?
It requires you to own the stack — Nginx config, PHP-FPM pool tuning, WordPress core and plugin updates, backups. For an agency dev already comfortable with SSH, it's not harder, it's just visible. The trade-off is control and per-site cost versus a managed provider handling those tasks for a fee baked into each site.
How many WordPress sites can I run on one VPS?
It depends on your PHP-FPM pool sizing (pm.max_children per pool) more than raw traffic. A 4GB VPS II can comfortably run 2-3 lightly-trafficked sites with separate pools; an 8GB VPS III or 16GB VPS V gives more headroom for 5-12+ sites depending on how memory-hungry each pool is configured.
What's the cheapest way to test a WordPress VPS setup before committing?
Use hourly billing. Our smallest tier, VPS I at 2GB/1vCPU/40GB NVMe, bills at €0.0056/hr, so you can spin up a full stack, deploy a client site clone, and tear it down again for a fraction of a euro while you validate the sizing.
Do I need managed WordPress hosting for a WooCommerce site?
Not inherently — WooCommerce is more sensitive to NVMe I/O and database write performance than to having a managed panel. Every tier we run is NVMe-backed, and root access lets you tune MySQL/MariaDB and object caching directly rather than through a managed abstraction layer.
Can I move from a shared VPS setup to dedicated hardware later?
Yes. If a consolidated agency portfolio outgrows VPS capacity, our dedicated servers keep the same unmanaged, root-access model, just on hardware you don't share with any other tenant.