Shared hosting is the entry-level product nearly every web host sells: one machine, one operating system, one web server and database engine, sliced into customer accounts by a control panel such as cPanel, Plesk or DirectAdmin. You receive a home directory, one or more databases, mailboxes, and an installer that will have WordPress running before the kettle boils. What you never touch is the operating system, and avoiding it is precisely what you are paying for. Security patches, PHP upgrades, firewall rules and dying disks belong to the provider, and on a competent host you will never hear that any of it happened. Support belongs to the product as well, and on cheap plans it is the component that varies most wildly between providers whose feature lists look identical.
Where the pooling shows
- Other people's code runs on your processor. A runaway import or a brute-forced login page next door can drag response times across the whole machine until the limiter catches up with it.
- Allowances are per account and invisible until they are not. Hosts cap processor seconds, memory, simultaneous processes, database connections and inode counts, and none of that is mentioned in the marketing for a plan sold on unlimited anything.
- Isolation is a permission model, not a wall. Your files are fenced off from the account beside you, but you share a kernel, a PHP version policy and frequently an IP address, which is why one spammer on the box can affect everyone's email deliverability.
None of that is an argument against shared hosting. It is a map of when to leave, and the trigger is a limit you keep hitting rather than a feature you fancy. The resource graph pinned to its ceiling during your best hours, a checkout that stalls whenever the newsletter goes out, a backup that cannot finish: those are the signals, and they arrive long after the price stopped mattering. Backups deserve their own sentence, because a plan whose only copy of your site sits on the same machine as the site is not a backup at all, and the cheapest tiers quietly assume you keep your own. From there a VPS buys reserved capacity and root access in return for making you the systems administrator, while managed hosting buys the same capacity with somebody else still carrying the pager. Shared hosting stops being a bargain at roughly the moment a site starts earning. Until then it remains the right answer, and an unfashionable one, which is a combination worth being suspicious of in the other direction.