LiteSpeed Web Server (LSWS) is priced along two axes at once — the RAM cap the server processes are allowed to consume, and the number of domains the licence will serve. Most buyers get the first right and the second wrong, then either over-buy by a tier or hit the domain ceiling on day 30 of a shared-hosting build-out.
This article covers what each of the six tiers actually limits, how the RAM cap is measured (it isn't total server RAM), and the tier transitions you should plan ahead of growth rather than after a customer ticket.
The six tiers
| Tier | RAM cap | Domain cap | Typical use case |
|---|---|---|---|
| Site Owner | 2 GB | 1 | Hobby site, single-tenant VPS |
| Site Pro | 8 GB | 1 | Single high-traffic site, e-commerce |
| Web Host Lite | 8 GB | 5 | Small agency, internal projects |
| Web Host Essential | 8 GB | Unlimited | First shared-hosting node, boutique hosts |
| Web Host Professional | 32 GB | Unlimited | Mid-size shared-hosting fleet |
| Web Host Enterprise | Unlimited | Unlimited | High-density nodes, reseller backbones |
The boundaries that catch people out:
- The RAM cap is per-worker, not whole-server. LSWS reserves the cap for its own worker processes. If your box has 64 GB of RAM but you're on Web Host Essential, LSWS will only use 8 GB of it — the remaining 56 GB sits idle for the web server. MySQL, PHP-FPM, and cPanel itself still get the rest.
- The domain cap counts vhosts. Addon domains and subdomains in cPanel each create a vhost, so a single cPanel account with five addon domains uses six vhost slots, not one.
- There is no "Lite Plus". The jump from Web Host Lite (5 domains) to Web Host Essential (unlimited) is a single step. There is no intermediate tier — once you cross five domains, you go to Essential.
How the RAM cap is enforced
LSWS counts memory allocated by the worker processes. On a cPanel box that runs Apache as
LSWS, this is the sum of resident memory across httpd (now LSWS) workers serving requests.
PHP-FPM pools and Apache module memory do count because LSWS spawns and tracks them.
You can see the live total against your cap in the WebAdmin Console under Server Status → Realtime Statistics. If you hit it, LSWS throttles new workers rather than crashing — but throughput drops sharply, often surfacing as long TTFB on cache-miss requests rather than as an obvious error in logs.
Workers, CPU, and the Enterprise tier
LSWS also licenses by worker count — the number of processes LSWS will fork to handle requests in parallel. The default is one worker per CPU socket, capped by the tier:
- Site Owner / Site Pro — 1 worker.
- Web Host Lite / Essential / Professional — up to the licensed worker count for the SKU (typically scales with the tier's RAM allowance).
- Web Host Enterprise — unlimited workers.
On a 32-core box, one worker is the wrong default — you'll only get one core of LSWS throughput regardless of how much RAM you have. For multi-core shared hosting, Professional or Enterprise is usually the right answer, not Essential.
Cloud vs dedicated — no separate SKU
Unlike cPanel, LiteSpeed does not split tiers into Cloud and Metal SKUs. The same Web Host Essential licence activates on a KVM guest, an AWS EC2 instance, or a bare-metal dedicated server. The price is the same.
What this means in practice: you can move a LiteSpeed licence between an on-prem host and a cloud VPS during a migration without buying a different SKU. You do need to release the licence from the old IP before activating on the new one — see the LiteSpeed licence reactivation flow for the IP-rebind mechanics, which work identically across cPanel and LSWS.
Worked example: scaling a shared-hosting node
A reseller starts on a 16 GB VPS with 8 cPanel accounts and grows over a year.
| Quarter | Accounts | Vhosts | Peak LSWS RAM | Tier needed |
|---|---|---|---|---|
| Q1 | 8 | 14 | 3 GB | Web Host Lite (5 dom) |
| Q1 end | 12 | 21 | 4 GB | Web Host Essential |
| Q2 | 35 | 80 | 6 GB | Essential |
| Q3 | 90 | 220 | 9 GB | Web Host Pro |
| Q4 | 180 | 480 | 14 GB | Web Host Professional |
The first transition (Lite → Essential) is forced by the domain cap, not RAM. The second (Essential → Professional) is forced by RAM, not domains. Plan the cutover at least a week before you expect to cross either boundary — mid-traffic upgrades work but they're stressful.
For a single high-traffic site that's outgrowing Site Owner, the natural next step is Site Pro, not Web Host Lite — Site Pro keeps the single-domain SKU at a lower price than Lite, even though Lite would technically also fit.
When to upgrade (and when to consolidate instead)
Upgrade the tier when:
- LSWS worker RAM is at 80% of cap on a 7-day average. The peak doesn't have to hit 100% — you don't want to throttle during a Black Friday burst.
- You're about to migrate accounts in from another server. Buy the headroom before the migration, not during it.
Consolidate instead when:
- You have two Essential nodes each running at 30% RAM. One Professional licence on a bigger VPS costs less than two Essentials and gives you headroom in one place.
- A node is hitting the domain cap because of stale addon domains. Audit and remove unused vhosts before paying for the next tier.
For current per-tier pricing across regions, see the LiteSpeed pricing page. For fleets above five servers, contact sales for partner rates — the volume discounts are real and start meaningfully above the listed prices.
Does LiteSpeed Web Host Essential have a domain limit?+
What counts as a domain on a LiteSpeed licence?+
Can I use a LiteSpeed Site Owner licence on a cPanel server?+
How much RAM does the LiteSpeed RAM cap actually limit?+
Can I move a LiteSpeed licence between servers?+
Is there a discount for buying multiple LiteSpeed licences?+
Next steps
- Pick a tier and activate a LiteSpeed licence, or read the free-vs-paid trade-off in LSWS vs OpenLiteSpeed.
- New to LSWS on cPanel? Start with installing LiteSpeed Web Server on a cPanel box and then enable LSCache for WordPress.
- Mid-cycle tier change? See how prorated licence billing works before you press the upgrade button.