CloudLinux Isolates Phase 3: per-site CPU and memory limits in beta
CloudLinux brings per-site resource limits to beta on cPanel with CloudLinux 8/9, the third phase of the Isolates project.
UptimeMag editorial team · 28 September 2026 · 2 min read

CloudLinux announced on 28 September 2026, on its blog, the beta availability of per-site resource limits within an isolated hosting account. This is phase 3 of the Isolates project: phase 1 gave each site an isolated filesystem, phase 2 gave it its own PHP version. Until now, however, all sites within an account shared the same CPU, memory and I/O limits. As of this beta, each site can have its own.\n\nFor those running reseller hosting or shared accounts with multiple domains, this changes how load spikes are handled: a site that runs into trouble no longer has to starve the other sites on the same account.\n\n## How it works\n\nEach isolated site gets its own LVE (Lightweight Virtual Environment), nested under the account's LVE. The account limit remains the overall ceiling: the sum of individual site limits can actually exceed it, because when a site is idle its spare capacity goes to the others. Example from the CloudLinux documentation: an account with a 100% CPU limit and three sites each set to 50%; if two are idle, the third can use its full 50%, and when all three are active they share the 100%.\n\nPer-site usage is visible via lveinfo and lvechart; the account owner can check their own sites with isolatectl stats. Fault emails now also indicate which site and which limit triggered the alert, but they're still sent to the account's address, not the individual site's.\n\n## Current limitations\n\n- Requires cPanel with CloudLinux 8 or 9: on CloudLinux 7, isolated sites retain only filesystem isolation.\n- Not yet available on LiteSpeed Web Server.\n- Database limits remain per account: MySQL Governor doesn't split them per site.\n- Available on the Up to 5 Hosting Accounts (Admin) and Unlimited Hosting Accounts (Shared Pro) plans; the Single Hosting Account (Solo) plan isn't included yet.\n\n## How to try it\n\nInstall the packages from the testing repository:\n\n\nyum update --enablerepo=cloudlinux-updates-testing lve-stats3 lve-utils lve liblve cagefs\n\n\nMinimum required versions: lve-stats3 5.1.0-1, lve-utils 6.6.41-1.\n\nFor a site not yet isolated:\n\n\ncagefsctl --site-isolation-allow <user>\ncagefsctl --site-isolation-enable <domain>\n\n\nFor those already using Isolates, you need to explicitly enable limits at both account and site level:\n\n\nlvectl allow-domain-limits <user>\nlvectl enable-domain-limits <domain>\nlvectl list-domains <uid>\n\n\nSetting the limits for a site:\n\n\nisolatectl limits set --domain example.com --cpu 5000 --pmem 268435456 --io 2048\nisolatectl stats --domain example.com\n\n\nThe first command assigns example.com 50% CPU, 256 MB of memory and 2 MB/s of disk I/O. CloudLinux is inviting users to share their experience in the blog comments or through official support.\n\nCloudLinux is a CloudLinux product.\n
Written with the help of artificial intelligence and checked by the editors (EU AI Act, art. 50). Source: CloudLinux – sicurezza e rilasci.