Imagine living in a block of flats where one resident’s kitchen fire could spread to every unit because there are no fire walls. That’s essentially how traditional shared hosting works. Site isolation is the digital equivalent of proper fire safety — and it’s critical for WordPress security.
On typical budget shared hosting, hundreds of websites share the same server environment: shared file systems (a vulnerability in one site can access files from another), common resources (if one site is compromised, attackers may pivot to others), noisy neighbours (attacked sites affect everyone’s performance), and delayed detection.
Here’s a typical cross-site infection scenario: Site A
An outdated plugin vulnerability. Hackers exploit it, discover they can read files from other sites due to poor isolation, find wp-config.php files with database credentials, and inject malware across all accessible sites. Your site was kept up to date — but someone else’s vulnerability became your problem.
Our platform takes a fundamentally different approach. Each site runs in a containerised architecture with isolated file systems, separate PHP processes, and guaranteed resource allocation. Sites cannot access each other’s files under any circumstances. A compromise in one container never affects another.
For UK businesses, proper isolation means reduced liability, predictable performance, easier GDPR compliance (data isolation helps with requirements), and faster recovery. Combined with brute force protection and DDoS mitigation, you get comprehensive security. Compare managed vs shared hosting to understand the isolation difference, and review our scaling policy for how WP Pro Host handles growth.
Frequently Asked Questions
What is site isolation in WordPress hosting?
Site isolation means each WordPress site runs in a sandboxed environment — its own container or virtual environment with an isolated file system, separate PHP processes, and distinct resource allocation. A site in one container cannot read, write, or execute files belonging to another account. This prevents cross-account contamination, where an attacker who compromises one site on a shared server pivots to access other sites through shared file system permissions. Container isolation is a fundamental security architecture difference between budget shared hosting and managed hosting.
Why does site isolation matter for WordPress security?
On shared hosting without proper isolation, a compromised neighbouring account on the same server can read your wp-config.php file to obtain your database credentials. With those credentials, an attacker can read and modify your database, inject malware, create admin accounts, and steal customer data — without ever directly attacking your WordPress installation. Your site can be fully up-to-date and well-secured but still be compromised through a neighbouring account’s vulnerability. Container isolation makes this attack vector impossible by preventing any cross-account file system access.
What is the difference between shared hosting isolation and container isolation?
Traditional shared hosting uses operating system-level user permissions to limit file access between accounts, but this isolation is partial and has documented bypass techniques. Container isolation (used in managed hosting with Enhance CP and similar platforms) uses OS-level containerisation to create completely separate virtual environments for each account — separate file systems, separate process namespaces, separate network stacks. There is no shared PHP execution environment and no shared filesystem path that would allow cross-account access under any circumstances.
Does site isolation affect WordPress site performance?
Container isolation has no negative performance impact and can improve it. Dedicated resources within the container — CPU, RAM, PHP workers — are not shared with neighbouring sites, meaning your performance is not affected by a neighbour’s traffic spike or resource-intensive plugin. The “noisy neighbour” problem that degrades performance on shared hosting is eliminated by container isolation. Each site gets consistent, guaranteed resource access rather than competing for a shared pool.
How do I know if my WordPress hosting provider uses site isolation?
Ask specifically: does each customer account run in an isolated container with a separate file system, or does it use shared PHP processes and a common directory structure? Look for references to LXC, Docker, containerisation, or account isolation in the hosting documentation. Hosting providers using Enhance CP, cPanel with CloudLinux, or similar containerisation technologies typically offer meaningful isolation. Generic “unlimited” shared hosting on standard cPanel servers typically does not. The clearest signal is whether the host can provide documentation of their isolation architecture.