ServerPanelX
Security 4 min read Published

Why every site gets its own PHP jail

One hacked plugin should stay one problem. Here is how per-site isolation keeps the rest of your server safe.

ServerPanelX teamWritten by the people who build the panel

Quick answer

In ServerPanelX every hosting account runs in its own PHP jail with its own PHP pool and resource limits. If one site is hacked or gets a traffic spike, the damage stays inside that account and the other sites on the server keep running.

Key takeaways

  • Each hosting account runs in its own PHP jail with its own PHP pool.
  • Resource limits are set per account, from your hosting packages.
  • Isolation is on by default on every install — it is not an add-on.
  • Isolation heals itself after updates, and the Isolation Manager can repair it.
On this page
  1. The problem with shared hosting
  2. How ServerPanelX separates sites
  3. What it means for you
  4. Keeping isolation healthy
  5. Questions

The problem with shared hosting #

On many servers, every site runs under the same PHP process. When one site is compromised — an outdated plugin, a weak password — the attacker can often reach the files of every other site on the box.

How ServerPanelX separates sites #

  • Each hosting account runs in its own PHP jail
  • Each account gets its own PHP pool, so sites never share one PHP process
  • Resource limits are set per account, from your hosting packages
  • Each site can run the PHP version it needs, side by side

What it means for you #

If one customer’s site is hacked, the damage stays inside that account. The other sites on the server keep running, and you clean up one account instead of the whole server.

Keeping isolation healthy #

Isolation heals itself after updates. The Isolation Manager shows every account’s isolation at a glance and lets you repair it from the same screen, and Resource Guard catches runaway sites before they affect the rest of the server.

Questions people ask

What does site isolation mean in ServerPanelX?

Each hosting account runs in its own PHP jail with its own PHP pool and resource limits, so a hacked plugin or a traffic spike on one site stays contained to that site.

Is isolation an add-on?

No. Every site is isolated by default on every install, including the free trial — there is nothing extra to buy or set up.

What if one site uses too many resources?

Each account has its own resource limits from its hosting package, and Resource Guard catches runaway sites before they affect the rest of the server.

Related toolkits

Last updated