What "Isolation" Actually Means in Hosting

“Isolated” is one of the most stretched words in hosting. On a cheap shared plan it can mean little more than separate folders on the same server. Real isolation is a stronger guarantee, and the difference shows up on exactly the day you don’t want surprises.

Shared by default

Traditional shared hosting packs many sites onto one server, sharing the same operating system, the same web server process, and often the same database server. Most days that’s invisible. It stops being invisible when one site gets a traffic spike and starves the others, or when one is compromised and the attacker can see its neighbors.

What real isolation looks like

Real isolation gives each site its own container, its own network, and its own credentials. A process in one can’t see or reach another. A break-in next door stays next door, because there’s no shared surface to cross. Resource limits are per-site, so a neighbor’s spike doesn’t become your slowdown.

Why it matters for security

Most site compromises aren’t sophisticated, an outdated plugin, a weak password. Isolation limits the blast radius: a compromised site is contained to itself instead of becoming a foothold into everything on the box. It turns a potential disaster into a single-site cleanup.

How we do it

On SrvBot every site runs in its own dedicated container, on its own network, with its own credentials, and those credentials rotate automatically. It’s the same model whether you run one site or ten.

The bottom line

When a host says “isolated,” ask what’s actually separated, files, or the whole environment. The gap between those two answers is the gap between a neighbor’s bad day staying theirs and becoming yours. More on how we contain sites across /help.