CloudLinux license

CloudLinux OS is a leading platform for multi-user hosting environments which increases host stability and security

Full control of resources through LVE Manager
Security isolation of users through CageFS
Easy to manage PHP versions through PHP Selector

Choose the stability of CloudLinux OS

If you provide web hosting services, it’s extremely important to secure and stabilise the servers you’re using.
CloudLinux is also ideal if you require user isolation.

Solutions offered by the CloudLinux OS

Using CloudLinux you create an environment that is more similar to a virtual host than a shared hosting account.
Security is achieved by isolating each hosting user account and appointing host resources individually to each account.

Problem CloudLinux option Solution

Server overloaded and losing resources LVE virtualization Offers you control over server resources, including the CPU, IO, memory, inodes, the number of processes and connections that each individual cPanel account can use

Server breaches and malicious scripts CageFS Isolates every user and makes the users invisible to each other within the system. CageFS prevents a great number of attack, including most attacks through privilege escalation.

The user requires different PHP versions PHP selector Provides flexibility by offering the users all the popular versions of PHP, which enables them to keep old scripts without the obligation to use newer PHP versions or change the code of their website

MySQL server is overloaded MySQL Governor Pinpoints problematic users and limits them in real time; unprecedented in the industry.

Symlink attacks SecureLinks SecureLinks prevents all known symlink attacks at the kernel level.

Order a CloudLinux license

Limit resources using LVE Manager

CloudLinux places an LVE virtual environment in every user account for the purpose of maintaining resource control in each individual account.
The objective of LVE is to ensure that no user can take down the entire server.

CPU limitation

Limits CPU usage for each individual user. When a user reaches the set CPU limits, their processes are decelerated in order to prevent the misuse of server resources. Processor limitations are crucial in preventing individual users from slowing down or even blocking the entire server and making it unresponsive.
Entry process limitation

Limits the number of entry processes within the LVE for each user. A single entry process actually represents a single website visitor. This limitation is important in order to prevent a single website from taking up all Apache resources and making the server unresponsive due to overload.
Memory limitation

Limits memory usage per user. Memory limitations are important in preventing the overuse of server memory which can lead to server congestion. Memory limitations are also fundamental in protecting the server from destroying important caches that can help increase the speed and reduce the load of the server.
MySQL limits

MySQL Governor enables you to set a resource limitation per user. You can set a limitation for CPU and IO reading and writing, thus preventing individual users from taking up the majority of MySQL server resources. Nowadays, MySQL data launches most web applications and it’s important to monitor those applications.
I/O limits

Offers the limitation of data throughput per user. The bandwidth is measured in kB/s, and, upon reaching the limit, the processes are reduced. Since IO is one of the weakest shared hosting resources, setting a ceiling for user usage is vital because it enables stable work for all users, instead of several users with extremely complex sites congesting the disks.
Inode limits

Inode is a type of data structure that describes file system objects – files and directories. Only a limited number of inodes is in each file system, and, after those are used, no new files can be created. Limitations are enforced through file system quotas per user.
Process number limitation

Limits the number of simultaneous processes within the LVE for each user. After the limit has been reached, no new processes can be created until one of the existing processes is complete. This effectively prevents fork bombs and similar DOS attacks.