Is Unlimited Hosting Really Unlimited? The Honest Answer

No. Not in the way the word sounds, and not on any host — ours included. Something on a shared server is always finite, because the server itself is finite. The honest version of the question is not whether hosting is unlimited but *which* things are uncapped, which ones are allocated, and whether the company will tell you the numbers before you pay.

Most won't. Across the Indian hosting market you will find "unlimited" on the pricing page and nothing anywhere that says what the CPU ceiling is. This guide explains what the word genuinely covers, what it never covers, and then prints our own limits so you can hold us to them.

What is genuinely uncapped

Some resources cost a host almost nothing to hand out generously, and those are the ones that carry no account-level cap on an unlimited plan. On our Unlimited Hosting line that means:

• NVMe storage — no per-account quota
• Bandwidth — unmetered
• Email accounts, MySQL databases, subdomains and domain aliases
• FTP accounts, DNS records, forwarders and cron jobs

These are real. There is no hidden storage meter waiting to bill you, and no bandwidth overage invoice. The catch is not in this list — it is in the next one.

What is always allocated, on every host

CPU, memory, disk throughput and process counts cannot be unlimited on shared infrastructure. A server has a fixed number of cores and a fixed amount of RAM, and every account on it draws from the same pool. If one site could consume without limit, every other site on that machine would suffer — which is precisely why limits exist, and why a host that claims otherwise is either not telling you about theirs or is running a server you would not enjoy sharing.

On cPanel hosting these ceilings are usually enforced by CloudLinux, which gives each account its own LVE — a container with a defined CPU, RAM, I/O and process allowance. It is the reason one busy neighbour no longer takes down everyone else, and it is the number that actually determines how much traffic your site can absorb.

Our actual numbers

Here is what we allocate on each Unlimited tier. The live table on the Unlimited Hosting page is generated from the same plan data our billing system uses, so it is always current:

• Unlimited Solo — 3 CPU cores, 4 GB RAM, 25 MB/s I/O, 4,096 IOPS, 75 entry processes, 1 website
• Unlimited Trio — 4 cores, 5 GB RAM, 30 MB/s I/O, 5,120 IOPS, 100 entry processes, 3 websites
• Unlimited Pro — 5 cores, 6 GB RAM, 35 MB/s I/O, 6,144 IOPS, 125 entry processes, 5 websites
• Unlimited Infinity — 6 cores, 8 GB RAM, 40 MB/s I/O, 8,000 IOPS, 150 entry processes, no website limit

Two of those terms do the heavy lifting and are worth understanding. **Entry processes** is the number of requests your account can have actively executing PHP at one instant — not visitors per hour, but simultaneous work in flight. A cached page served by LiteSpeed barely touches it; an uncached WooCommerce checkout does. **IOPS** is how many separate read/write operations per second your account can make to disk, which is what a database-heavy site leans on hardest.

These are ceilings, not reservations. You are not charged for headroom you never use, and a normal business site spends its life nowhere near them. They matter on the day something goes right — a campaign lands, a post spreads — and that is exactly when you want to know the number in advance rather than discover it from an error page.

What happens if you hit the limit

Nothing dramatic and nothing silent. When an account reaches its CPU or entry-process ceiling, additional requests queue briefly and, if the pressure continues, are served a 508 error rather than being allowed to destabilise the server. The site does not get suspended and the account is not billed an overage. The pressure shows up in cPanel's resource usage graphs, which is the first place to look when a site feels slow for no obvious reason.

In practice, the usual fix is not a bigger plan. It is caching. A WordPress site serving cached pages through LiteSpeed uses a small fraction of the processes an uncached one does — see what LiteSpeed hosting actually changes. Tuning first is cheaper than upgrading, and we would rather tell you that than sell you a tier you do not need.

So when is Unlimited the right plan?

Unlimited earns its price when the *count* of things is your constraint rather than the size of any one thing. Several sites to host, a large media library, a mailbox for everyone on the team, a staging copy or two — those are the cases where per-account quotas become the daily annoyance, and removing them is worth ₹199 a month.

If you run one modest site, our shared hosting starts at ₹49 and will not feel slower for that workload — the platform underneath is identical. And if you need resources that are genuinely *yours* rather than allocated from a shared pool, that is a different product class: see VPS vs shared hosting for where that line falls.

How to read anyone else's unlimited plan

Take this to any host, including us. Ask for the CPU cores, the RAM, the entry-process count and the inode limit in writing before you buy. Ask what happens when you reach them. Then read the acceptable use policy, because that is where an "unlimited" plan is quietly bounded — almost every host forbids using web hosting as general file storage, backup dumps or a download mirror, and that restriction is entirely reasonable.

If a company cannot produce those numbers, the limits still exist. You just will not know them until the day they matter.

Frequently asked questions