Shared resources need shared rules. Here's exactly where the limits sit, and why they exist — no vague fine print.
Our shared and business plans list "unlimited" storage and bandwidth. That word does real work for 99% of customers — and this page explains the boundary that protects the other 1% from slowing everyone else down.
Shared hosting works because hundreds of low-traffic sites split the cost of one server. It only stays affordable if no single account can monopolize the CPU, memory, or bandwidth that everyone else is drawing from. This policy exists to keep that balance fair — not to trip up ordinary websites.
"Unlimited" means we don't cap storage or bandwidth at a fixed number for typical website use — blogs, portfolios, small stores, brochure sites. It does not mean a shared server can host a video streaming platform or a public file-mirror. Over 99.7% of our shared accounts never come close to a limit.
Shared and Business plans are capped at 25% of a single CPU core sustained and 1GB RAM per process, which comfortably covers WordPress, WooCommerce, and most CMS-driven sites under normal traffic. Inode count (total files) is capped at 250,000 — mainly relevant to sites with huge media libraries or cache bloat.
We don't suspend accounts on the first spike — traffic surges happen. Our monitoring flags sustained overuse, our team emails you what's happening, and in most cases we suggest moving to VPS or a Dedicated Server, since that's genuinely a better fit at that point. Suspension is a last resort, reserved for accounts that ignore repeated notices or actively harm the shared server.
Think a flag was a mistake — a one-off traffic spike from a press mention, for example? Reply to the notice email or open a ticket. A real engineer reviews the usage graphs, not an automated script.
Questions about where your site sits relative to these limits? Email support@webhostingksa.com — we can pull your usage graphs and tell you plainly.