CloudLinux License for Shared Hosting Servers
The OS layer that stops one account from taking the whole box down with it. Licenses are issued against the server IP, and installation is a single command.
CloudLinux OS is a server operating system aimed squarely at shared hosting. Every hosting account runs inside its own LVE - a lightweight environment with its own limits on CPU, memory, disk I/O and concurrent processes - so a runaway script shows up as one account slowing down rather than a support queue full of unrelated customers. CageFS gives each account a view of the filesystem containing only its own files, hiding system files and the neighbors alike. A per-account PHP selector lets one customer stay on an older version for an older application while everyone else moves forward. If you host many customers on one machine, this is the layer that keeps one account's mess inside that account.
Licenses are issued per server IP, so there is no key material to bake into your images or rotate later. Building a machine at three in the morning is fine: create the license over the REST API inside the same provisioning script, then run the installer, which is a single command and resolves the license from the IP. Create, renew, suspend and re-IP are all API calls, open on every account tier, so you can drive them from WHMCS or from your own panel. Payment comes out of your prepaid balance with no approval step in between. Re-imaging a box or moving it to another data center means editing the IP in the panel yourself, and the old address stops at that moment. Reseller accounts can define sub-resellers with their own price lists and balance limits, and serve the install script from their own domain under their own brand. Every order, renewal and API call is logged with its result, so which machine got licensed when is a matter of record.
CloudLinux installs by converting an existing RHEL-family system - CentOS, AlmaLinux, Rocky and relatives - in place. If your fleet is Ubuntu-based, this is not the direction to go. The conversion installs its own kernel, so one reboot is part of the job: schedule a window and take a backup first. There is more than one edition, and which components you get - the PHP selector, CageFS, database resource management - depends on the one you buy, so read the edition name and its scope in the catalog before ordering. CloudLinux is not a control panel either; it handles isolation and leaves account creation and billing to the panel you already run. Monthly licenses run to the end of the period and auto-renewal can be turned off, with no commitment and no cancellation fee; current editions and prices are shown in the panel.
Why buy it here
Per-account limits
LVE caps CPU, memory, disk I/O and processes per account, so one busy site stays one busy site.
Licensed by IP
The license belongs to the machine's IP address, with no key file to carry around in your images.
Provisioning by API
A new machine can create and activate its own license from inside your build script.
Sub-reseller pricing
Reseller accounts can set a separate price list and balance limit for each sub-reseller.
Frequently asked
Can I convert a running server instead of reinstalling it?
Yes - CloudLinux is designed to convert an existing RHEL-family system in place, so there is no rebuild. It does install its own kernel, so one reboot is required. Pick a quiet hour and take a backup before you start.
Do I need a new license if I rebuild the server?
No. The license belongs to the IP address, so rebuilding on the same IP needs nothing from you - the installer finds it again from the IP. Moving to a different IP means updating the address in the panel yourself, and the old one stops at that moment.
How do I fit licensing into automated server builds?
Call the API to create the license, then run the installer in the same script - one command. Because the installer resolves the license from the machine's IP, there is no secret for your automation to store or bake into an image. Renewal and re-IP go through the same API.
Does the license depend on how many accounts I host?
That depends on the edition. Editions meant for a single-account server and editions meant for busy shared machines do not cover the same ground, so check each edition's description in the panel for the components included and any account limit. If anything is unclear, ask us before you order.
Other licences
Add your server IP, create the license, and let your build script take it from there.