The traditional answer to this question was straightforward. Need isolation and control? Get a VPS. Need affordability and simplicity? Get shared hosting. The tradeoff was clear: you traded isolation and performance for cost and convenience.
That framing made sense when shared hosting meant CageFS filesystem isolation and shared PHP workers, and a VPS was the only way to get your own process space and dedicated resources. It makes less sense now that container-based shared hosting provides VPS-level isolation without VPS-level management overhead.
This post breaks down the actual differences, who genuinely needs a VPS, and who is paying for complexity they do not need.
What a VPS is#
A VPS (Virtual Private Server) is a virtual machine running on shared physical hardware. A hypervisor – the software that creates and manages virtual machines – carves up a physical server into multiple isolated VPS instances. Each instance gets its own operating system, its own kernel, its own process table, and its own network stack.
When you buy a VPS, you get:
- Root access. Full administrative control over the entire server. You can install any software, modify any configuration file, and run any service.
- Dedicated resources. The CPU cores, RAM, and storage allocated to your VPS are yours. The hypervisor enforces this at the hardware virtualization level. Other VPS instances on the same physical server cannot consume your resources.
- Full isolation. Your VPS runs its own kernel. Processes on your VPS are invisible to other VPS instances. Your network stack is separate. A compromise on another VPS cannot directly affect yours.
- Complete responsibility. Every aspect of server management is your job: operating system updates, security patches, firewall configuration, web server setup, PHP installation, database tuning, SSL certificates, backups, monitoring, and incident response.
A typical unmanaged VPS from a cloud provider (DigitalOcean, Linode, Hetzner, Vultr) costs $5-50/month depending on resources. You get a bare Linux server with an IP address. Everything else – installing Nginx, PHP, MySQL, configuring WordPress, setting up SSL, hardening security – is up to you.
A managed VPS, where the provider handles server administration, costs $50-300/month or more. You get the isolation and dedicated resources of a VPS without the management burden, but at a significantly higher price.
What shared hosting is#
Shared hosting means your site runs on a server alongside other sites. The server’s resources are shared between all accounts, with software managing isolation and resource limits.
When you buy shared hosting, you get:
- A control panel. A web interface (cPanel, Plesk, or a custom panel) for managing your domains, databases, email, and files. No command line required for basic operations.
- Managed infrastructure. The hosting provider handles the operating system, web server, PHP, database server, security, backups, and monitoring. You manage your website, not the server.
- Shared resources. CPU, RAM, and I/O are shared between accounts on the same server, with per-account limits to prevent one site from consuming everything.
- Lower cost. The fixed cost of server hardware is distributed across many accounts, making it the most affordable hosting option.
The traditional limitation of shared hosting was weak isolation. CloudLinux’s CageFS provides filesystem isolation – your site cannot read other sites’ files – but all accounts share the same process table, the same PHP worker pool, and the same network stack. This is adequate for many sites but meaningfully weaker than VPS-level isolation.
The traditional tradeoffs#
The VPS vs shared hosting decision used to come down to a clear set of tradeoffs:
| Shared hosting | VPS | |
|---|---|---|
| Cost | $3-15/month | $5-50/month (unmanaged), $50-300+ (managed) |
| Isolation | Filesystem only (CageFS) | Full (hypervisor) |
| Resources | Shared, with limits | Dedicated |
| Control | Control panel only | Full root access |
| Management | Provider handles everything | You handle everything (or pay for managed) |
| PHP configuration | Limited to what provider offers | Complete control |
| Security responsibility | Provider | You |
| Scaling | Upgrade plan | Resize VPS or add more |
The decision framework was simple:
- If you needed isolation, you got a VPS
- If you needed custom server configuration, you got a VPS
- If you needed dedicated resources, you got a VPS
- If you wanted affordability and zero management, you got shared hosting
The hidden cost in this framework was management. People who chose a VPS for isolation often underestimated the ongoing work of running a server. A VPS is not a product you buy and forget. It requires regular attention.
The real cost of managing a VPS#
The monthly price of a VPS is the smallest part of its total cost. The larger cost is your time and expertise.
What you are responsible for
Operating system updates. Security patches need applying promptly. A kernel vulnerability left unpatched for weeks is a window for exploitation. You need to monitor for updates, test them, apply them, and handle any issues that arise.
Web server configuration. Nginx or Apache needs configuring for your sites, with proper virtual hosts, SSL termination, caching headers, security headers, and performance tuning. A misconfigured web server is either slow, insecure, or both.
PHP management. Installing PHP, managing versions, configuring extensions, tuning FPM pools, setting memory limits, configuring OPcache – all of this affects your site’s performance and security. See how to install PHP on Ubuntu for what this involves.
Database administration. MySQL or MariaDB needs tuning for your workload. Buffer pool size, connection limits, slow query logging, and backup scheduling all require attention. A default MySQL configuration is not optimized for WordPress.
Security hardening. Firewall rules, SSH key configuration, fail2ban setup, disabling unnecessary services, configuring ModSecurity, monitoring for intrusions – security on a VPS is entirely your responsibility. Nobody is watching your server at 3 AM when an attack starts.
Backups. You need a backup strategy, a backup destination (preferably off-server), automated backup scheduling, backup verification, and a tested restoration process. A backup you have never tested restoring is not a backup.
SSL certificates. Setting up Let’s Encrypt, configuring auto-renewal, and handling certificate issues when renewal fails.
Monitoring. Disk space, memory usage, CPU load, PHP-FPM status, MySQL performance, SSL certificate expiry – without monitoring, you discover problems when your site goes down and a visitor tells you.
What happens when things go wrong
On shared hosting, server problems are the provider’s problem. On a VPS, they are yours.
When MySQL crashes at 2 AM, you fix it. When a PHP upgrade breaks a plugin, you debug it. When your server gets compromised because you missed a security patch, you clean it up. When disk space fills up because log rotation was not configured, you sort it out.
If you have the skills and enjoy server administration, this is fine. If you are a WordPress site owner who wants to focus on their business, this is a significant ongoing burden that distracts from your actual work.
How container-based shared hosting changes the equation#
The primary technical reason to choose a VPS over shared hosting was isolation. CageFS gave you filesystem isolation but shared everything else. A VPS gave you full isolation at every level.
Container-based shared hosting changes this by providing strong isolation without requiring you to manage a server. Each account runs in its own container with:
- Separate process namespace. Your processes are invisible to other accounts. Other accounts’ processes are invisible to you. There is no shared process table.
- Separate filesystem. Your container has its own filesystem image. It is not a filtered view of the host – it is a separate mount namespace with only your files accessible.
- Dedicated PHP. Your PHP runs inside your container with the specific version and extensions configured for your site. There is no shared PHP worker pool. Other accounts’ traffic does not consume your PHP workers.
- Enforced resource limits. CPU, RAM, and I/O limits are enforced at the kernel level through cgroups. Your allocated resources are yours regardless of what other accounts are doing.
For a detailed technical comparison of CageFS versus container isolation, see how Hostney isolates websites with containers.
This eliminates the biggest reason most WordPress site owners chose a VPS. If isolation was your primary motivation, container-based shared hosting gives you comparable isolation without the management burden.
What you still do not get
Container-based shared hosting is not a VPS. There are things a VPS provides that shared hosting – even container-based – does not:
Root access to the server. You cannot install arbitrary system packages, modify the web server configuration, or run custom services. If you need a specific system library, or need to configure Nginx rules that the control panel does not expose, you need a VPS.
Full kernel control. Your container runs on a shared kernel managed by the hosting provider. You cannot load kernel modules, change kernel parameters, run nested containers, or use software that requires direct kernel access.
Custom services. If you need to run services beyond a web server, PHP, and MySQL – Elasticsearch, custom daemons, mail servers, or monitoring agents – you need a VPS or a managed platform that includes those services.
Unrestricted resource scaling. A VPS can be resized to any amount of CPU and RAM the provider offers. Shared hosting plans have predefined resource tiers. If you need 32 GB of RAM and 16 CPU cores, shared hosting probably does not go that high.
Who actually needs a VPS#
You need a VPS if:
You run software that requires root access. Custom applications, non-standard services, specific system libraries, or software that needs direct server configuration that a hosting control panel cannot provide.
You need complete control over the web server. Custom Nginx modules, specific proxy configurations, non-standard routing rules, WebSocket handling, or other configurations that go beyond what managed hosting exposes.
You have compliance requirements that mandate dedicated infrastructure. Some regulatory frameworks require dedicated servers or virtual machines with specific security configurations that shared environments cannot provide.
You are a developer or sysadmin who prefers managing their own stack. If you enjoy server administration, know what you are doing, and want full control, a VPS gives you that. Just be honest about the ongoing time commitment.
You run multiple application types on one machine. Traditional shared hosting is built around web applications – PHP, databases, and static files. If you need to co-locate a Node.js service, a Python backend, and a WordPress site on one server under your own management, a VPS gives you that flexibility.
You probably do not need a VPS if:
You run WordPress or WooCommerce and your primary concern is performance and security. Managed WordPress hosting with container isolation gives you dedicated resources and strong isolation for WordPress workloads without the management overhead.
You wanted a VPS for “better isolation” but do not have server admin skills. An unmanaged VPS with a neglected security configuration is less secure than well-managed shared hosting with container isolation. Isolation only helps if the server behind it is properly maintained.
You spend more time maintaining the server than working on your business. If PHP upgrades, security patches, MySQL tuning, and backup management consume hours every month, you are paying for control you do not benefit from.
Your hosting needs are standard. WordPress, PHP, MySQL, SSL, email forwarding, cron jobs, backups – if this describes your stack, shared hosting covers it. You do not need root access for a standard WordPress deployment.
Cost comparison#
The monthly price comparison understates the true cost difference because it ignores the value of your time.
Unmanaged VPS
- Monthly cost: $5-50 depending on resources
- Your time: 5-20 hours/month for ongoing maintenance, security, updates, and troubleshooting (more during incidents)
- Risk: Misconfiguration, missed patches, and lack of monitoring can lead to security incidents or downtime that costs far more than the hosting itself
Managed VPS
- Monthly cost: $50-300+ depending on the provider and level of management
- Your time: Minimal for server tasks, but you still coordinate with the provider for changes
- Risk: Lower than unmanaged, but depends on the quality of the managed service provider
Container-based managed hosting
- Monthly cost: $10-50 for most WordPress sites
- Your time: Near zero for infrastructure. You manage your WordPress site.
- Risk: The hosting provider manages security, updates, backups, and monitoring at the infrastructure level
The managed VPS is the most expensive option. The unmanaged VPS is the cheapest in dollars but the most expensive in time. Container-based managed hosting sits in between on price while requiring the least time investment.
The decision framework#
Instead of “VPS or shared,” ask these questions. For a detailed breakdown of the technical criteria that matter when evaluating any WordPress host – PHP versions, storage types, isolation models, security, and more – see how to choose WordPress hosting: what actually matters.
Do I need to run software that requires root access? Yes – VPS. No – managed hosting.
Do I have the skills and time to maintain a server securely? Yes and want to – VPS. No or would rather not – managed hosting.
Is my primary application WordPress or WooCommerce? Yes – managed WordPress hosting is purpose-built for this. A VPS is general-purpose infrastructure that you configure for WordPress.
Is isolation my primary concern? Container-based shared hosting provides strong isolation. A VPS provides hypervisor-level isolation. For most WordPress sites, the difference is not worth the management overhead.
What is my budget including time? If you value your time, include it in the cost calculation. Ten hours of server management per month at even a modest hourly rate exceeds the cost difference between a VPS and managed hosting.
VPS vs shared hosting on Hostney#
Hostney is managed hosting with container isolation – the isolation benefits that used to require a VPS, with the managed experience of shared hosting.
Each account runs in its own Podman container with a separate process namespace, dedicated PHP workers, and cgroup-enforced resource limits. Resources are specified per plan and enforced at the kernel level. The security stack includes bot detection, ModSecurity with the OWASP Core Rule Set, real-time malware protection, and SELinux in enforcing mode.
You do not manage the server. PHP versions, web server configuration, SSL certificates, backups, security hardening, and monitoring are handled by the platform. You manage your WordPress site through the control panel.
For most WordPress and WooCommerce sites, this provides everything a VPS offers in terms of isolation and dedicated resources, without the management burden or the risk of an undermaintained server.
See the hosting plans for resource allocations and pricing for a full comparison. For a broader look at how managed cloud hosting compares to both VPS and traditional shared hosting, see cloud WordPress hosting explained.