CloudLinux OS 9: Features and Limitations in Shared Hosting

Putting CloudLinux OS 9 in Perspective

CloudLinux OS 9 is a generation of the operating system that continues to be documented for shared hosting Based on AlmaLinux 9. However, it should not be confused with CloudLinux OS 10, which the manufacturer treats as a separate major branch. The version number alone does not describe either the scope of the license or the shared hosting components available on a specific server.

For classification, the AlmaLinux Kernel Important: CloudLinux OS 9 no longer uses its own CloudLinux kernel; instead, it uses the AlmaLinux kernel. Therefore, a name component such as „LVE“ in the kernel version is not a suitable criterion for assessing active resource isolation. LVE must be verified based on the installed CloudLinux components and their operational status, not based on the string in the kernel name.

This distinction dispels a common misconception regarding a CloudLinux Update: Upgrading to OS 9 does not replace the need to check limits, CageFS, PHP handlers, or database controls. The operating system version provides the technical foundation; which features are visible to customers depends on the combination of license, packages, and control panel integration. Especially on established servers, these levels may differ from one another.

An optional feature for CloudLinux OS 9 is a LTS Kernel Available. According to the manufacturer, it includes security fixes and fewer upstream changes than the regular AlmaLinux kernel. This may be suitable for environments with conservative change management, but it is not necessarily the better choice in all cases. Providers must weigh requirements related to hardware drivers, deployed software, maintenance processes, and the kernel strategy for their entire server infrastructure.

Clearly Distinguish Between Editions and Licenses

The version number CloudLinux OS 9 does not refer to either an edition or a license. For shared hosting, it is particularly important to distinguish between CloudLinux OS Legacy (formerly CloudLinux OS Shared) and CloudLinux OS Shared Pro. Legacy supports an unlimited number of hosting accounts and includes established components such as LVE, CageFS, MySQL Governor, PHP Selector, and language selectors.

Shared Pro should be considered separately: The edition overview assigns features such as PHP X-Ray, Centralized Monitoring, and AccelerateWP to this edition. Therefore, a cloudlinux update from OS 8 to OS 9 will not enable these features if the appropriate Pro license and the respective installation and panel requirements are not met.

CloudLinux OS Admin is also not a shortened name for Shared Pro. This edition is designed for a different scope; among other things, it does not include MySQL Governor. Therefore, anyone who wants to limit database overload per hosting account should not assume that this tool is available simply because they have an existing CloudLinux installation.

Before confirming functionality, three questions must be answered separately: Which edition is licensed, which packages are installed, and does the existing panel support the desired component? In addition, the versions of individual packages may affect the prerequisites. A successful operating system conversion only confirms that the conversion step was completed; it does not automatically confirm that all optional modules are ready for use.

Isolation and Limits in Shared Hosting

In Shared Hosting, the following is provided: LVE The task of limiting resource consumption per account. This includes, among other things, CPU, memory, input/output operations, processes, and concurrent web accesses. If a project reaches its limits, its resource consumption should not place a disproportionate burden on other accounts. This serves as protection against excessive resource consumption, but does not automatically resolve issues with slow applications or faulty database queries.

For reseller plans, reseller limits supplement the account limits. They cap the combined usage of a reseller’s subaccounts. Individual plans may have higher numerical limits, but the subaccounts collectively cannot exceed the overarching limit. This makes capacity and plan commitments more transparent, but requires careful planning of the overall limit.

CageFS has a different goal than LVE: The File system isolation restricts a user's visible system environment and is intended to prevent access to files in other hosting accounts. However, it does not replace a comprehensive security architecture. On cPanel servers, for example, the vendor’s documentation lists WebDAV, File Manager, Webmail, and FTP servers without proper chrooting as scenarios in which CageFS does not apply. Symlink protection and secure service configuration remain separate tasks.

PHP Selector allows you to select centrally shared PHP versions and extensions and requires CageFS. MySQL Governor monitors database usage by user and can limit accounts that are overloading the system; mod_lsapi, on the other hand, is a PHP handler for Apache. The components complement each other but are not interchangeable. Their availability and optimal combinations depend on the edition, web server, and configuration.

Panel integration requires special attention. On cPanel systems, customers should not be presented with both the PHP Selector and a competing MultiPHP selection as equivalent options, as this can lead to conflicting settings. Furthermore, not every control panel integrates every feature to the same extent. For a more in-depth explanation of account and website isolation, see the article on SecureLVE and Process Isolation in Shared Hosting; however, the license, documented panel support, and the specific server configuration remain the determining factors.

Select Components Based on Application

The specific business use case is what matters when making a selection, not just the "CloudLinux OS 9" label. The operating system, edition, license, installed packages, and control panel are separate factors to consider. Shared Pro extensions are not automatically available through an OS upgrade; the edition overview and the requirements of the respective component must be reviewed together.

The table is intended as a decision-making guide, not as approval for installation. Before giving your approval, check the supported panel version, the PHP handler, the specific license, and the package status. CloudLinux documents its own integration requirements for individual components; therefore, a feature that is generally available may be missing or managed differently in a specific panel environment.

This distinction is particularly important for rate planning: LVE Limits protect shared server capacity at the account level, while reseller limits set an additional shared cap for subaccounts. CageFS, PHP Selector, and MySQL Governor, on the other hand, serve different purposes. A component should therefore be chosen based on the observed bottleneck or protection need, not on a blanket list of features.

Practical Planning for Limits and PHP Management

If a WordPress store experiences traffic spikes, account limits restrict CPU usage, memory, input and output operations, processes, and concurrent web access. This keeps the affected account’s resource usage within defined limits and can protect other accounts from excessive usage. When analyzing the cause, it is crucial to determine which limit is actually being reached, rather than simply assuming a general server slowdown.

However, reaching a limit does not constitute a diagnosis of the store’s problem. A faulty extension, costly database queries, an import, or a lack of caching can trigger the load. Higher values shift the threshold but do not eliminate the root cause. Therefore, first check the resource data and the application; only then should you decide whether optimization, a different pricing plan, or additional capacity is appropriate.

For a reseller with many small plans, a Reseller Limit the limits for each individual end customer. While each subaccount can have its own limits, their combined total consumption must not exceed the parent limit. This prevents a reseller from using more resources than are allocated for its service due to the combined activity of many active customers.

For PHP, there should be exactly one clear selection interface per customer account. The PHP Selector requires CageFS. On cPanel systems, concurrent use with MultiPHP can lead to conflicting expectations if customers change versions in different locations. Therefore, specify which interface is visible, which versions are approved, and who manages exceptions.

The internal article explains how CPU, PMEM, I/O, IOPS, EP, and NPROC can be translated into specific pricing profiles How to Properly Configure CloudLinux LVE Manager in Shared Hosting. The values listed there are not automatically applicable to every piece of hardware or customer environment. Storage performance, the mix of applications, and the analysis of actual faults remain critical factors for each configuration.

Isolate multiple websites per account

A single hosting account often contains a main website, a store, a staging environment, and client projects. The account limit alone does not separate these applications from one another. CloudLinux Isolates The manufacturer has labeled it as a beta feature overall. This feature can set up file system isolation per domain, so that a website's access to files is restricted from other websites within the same account. It is therefore a viable option to consider for accounts with projects involving different levels of risk or responsibilities.

Separate from this are per-domain LVE limits. These are intended to limit resources on a per-website basis rather than just for the entire customer account. CloudLinux also explicitly labels this layer as beta and refers to it as such for OS 8 and OS 9. File system isolation and per-domain resource limits are thus two separate levels with different requirements.

• For domain LVE limits, CloudLinux specifies at least lve-stats3 5.1.0-1 and lve-utils 6.6.40-1.
• The PHP handler and control panel must support the respective Isolates configuration.
• It may be possible to separate file systems by domain, even though the requirements for domain limits have not yet been met.

You should therefore check the requirements separately: first, whether the beta feature “Isolates” is documented for the panel and handler you’re using with the desired file system layer; then, the package versions and the beta status of the resource limits. For standalone LiteSpeed, CloudLinux currently documents support only for cPanel. Other possible combinations should not be assumed to be supported in the same way.

Isolates can reduce the scope of impact within an account, but do not replace application maintenance. Updated plugins, separate login credentials, backups, and appropriate access control remain necessary. For an account with multiple independent client projects, the Domain Isolation After a documented compatibility test, this may still be a more appropriate additional limit than relying solely on shared account limits.

Preparing for Migration to OS 9

Migrating to CloudLinux OS 9 is a planned conversion, not a standard package update. It may affect installed packages, repository configurations, and the integration with the hosting panel. Before beginning, check your current operating system, CPU architecture, virtualization environment, and the CloudLinux integration supported by your hosting panel.

Set a maintenance window and work with complete, tested backups or consistent VM snapshots that can be restored according to the applicable recovery procedure. As an administrative best practice, it is also recommended to document package sources, active services, and non-standard configurations in advance. This allows you to specifically track any differences after the conversion, without treating the documentation as a substitute for a backup.

After the system migration, the verification process should not end once the conversion process is successfully completed. Check the integrated repositories as well as the panel integration, and handle additional components separately. PHP Selector, X-Ray, and AccelerateWP have their own installation, licensing, and panel requirements; a functional OS-9 base does not automatically guarantee their availability.

One key limitation concerns the version path: The conversion preserves the major version of the source system. Consequently, it does not directly convert a CentOS 7 system into a CloudLinux OS 9 system. For such a generational change, you’ll need a suitable migration path—such as a fresh installation with data and account migration—rather than treating the conversion as an upgrade across multiple major versions.

Check Packages, Kernels, and Faults

After installation or upgrade, the operational check begins with an inventory. First, check the currently running kernel. CloudLinux OS 9 uses the AlmaLinux kernel; therefore, the absence of the „LVE“ suffix in the output does not indicate that LVE features are missing. The command simply displays the version of the kernel that is currently running.

uname -r

Next, you check for the installed core packages. The output displays package names and version numbers or indicates if a package is not installed. This does not replace a license check or a verification of whether the control panel being used correctly integrates the respective interface and functionality.

rpm -q lve lvemanager cagefs lve-utils

If you want to evaluate per-domain limits using CloudLinux Isolates, you should also check the documented package versions for this feature. This query does not change any configuration. Domain LVEs are marked as beta; therefore, a matching package version alone does not confirm either the practical compatibility of the PHP handler or support by the panel.

rpm -q lve-stats3 lve-utils

For the root cause analysis, the following are Faults and resource data is more informative than a blanket increase in all thresholds. If an account reaches a limit, you first determine whether CPU, memory, I/O, processes, or concurrent accesses are affected. Next, you review the application and database queries, evaluate caching, and, if the demand is persistent, re-plan capacity or plan your pricing tier.

Avoiding Common Misconceptions

The most important point to note is this: CloudLinux OS 9 refers to the operating system generation, not the full range of features included in a hosting license. CloudLinux OS 10 is a separate major branch; therefore, statements about OS 9 cannot automatically be applied to OS 10. Shared Pro also remains a distinct edition with additional features such as PHP X-Ray, Centralized Monitoring, and AccelerateWP.

Similarly, a successful conversion should not be considered a blanket approval of all modules. After migration, the panel integration, package statuses, license scope, and requirements for each additional feature must be checked separately. This prevents customers from being promised features that, while they may be part of the selected edition, have not yet been set up or are not yet supported on the specific server.

CloudLinux Isolates require particular care. The vendor’s documentation classifies Isolates as beta. Furthermore, the file system isolation of websites within an account and the optional per-domain LVE limits are not equivalent; the domain limits are also explicitly marked as beta. Before deployment, check the PHP handlers, the control panel, and the documented package requirements.

Also Resource limits do not address the root causes within an application. For operational analysis, it makes sense to first evaluate faults and the affected resource type: CloudLinux can identify threshold violations for CPU, memory, I/O, IOPS, concurrent connections, and processes. Only then should you assess the application, database queries, cron jobs, and caching, as well as determine whether additional capacity is actually needed.

Account limits are sufficient for operational decisions when the primary goal is to keep customer projects separate from one another and limit peak loads. Reseller limits are also appropriate when a reseller needs to cap the combined capacity of its subaccounts. Website isolation should be considered a beta option for multiple projects with varying levels of risk within a single account, but only after a documented compatibility test and with clear labeling of their status.