Walk into any shared hosting company's backend and you'll find the same thing: a server with 64GB of RAM sold to customers whose combined allocations total 200GB. That's overselling. It's standard practice, it's the reason shared hosting is cheap, and it's the direct cause of slow sites.
We don't do it.
What Overselling Actually Means
A shared server has finite resources — CPU cores, RAM, disk I/O bandwidth. When a hosting company sells 300 plans on a server that can comfortably run 100, they're betting that most customers won't use their full allocation at the same time. Usually that bet pays off. Sometimes it doesn't, and everyone on the server slows to a crawl during peak hours.
The maths works until it doesn't. And you don't find out it doesn't work until your WooCommerce store times out on a Friday afternoon.
How We Do It Differently
Every server we run has a fixed number of slots. Each plan type takes a fixed number of slots. When a server is full, signups pause — you can see this in real time on our homepage.
We currently have four plan sizes:
- Flameling — 1 slot
- Ember — 10 slots
- Blaze — 25 slots
- Inferno — 50 slots
Each server has 100 slots total. When all 100 are taken, that server stops accepting new customers. We bring up a new server instead.
Why This Costs More to Run
Capping slots means we run more servers with fewer customers on each. Our infrastructure cost per customer is higher than an overselling competitor's. We offset that by keeping the team small, building our own tooling, and not running a traditional sales operation.
The tradeoff is deliberate: you pay a bit more per month, but the performance you're paying for is actually there.
What the Hard Cap Enforces
Beyond slot counts, every account runs inside a Linux cgroup — a kernel-level container that enforces CPU and RAM limits hard. Not soft warnings. Hard stops. If your PHP process tries to claim more RAM than your plan allows, it gets killed. Your site returns an error for that request. Other customers are unaffected.
This sounds harsh, but the alternative is worse: one runaway site silently consuming resources that fifty other sites were promised.
The Thing No One Else Publishes
We publish our live server capacity on the homepage. Every server, every slot count, updated every 60 seconds. If a plan is full, you see it.
We've never seen another host do this. The reason is obvious — most hosts don't want you to know how full their servers are. We think the opposite: if you're trusting us with your business, you should be able to verify the numbers yourself.