Look at who shares the VPS

A VPS may itself host several customer accounts. In that situation, you still need a policy for how the shared CPU, memory and other resources are used inside the virtual machine. Begin with the workload and account structure.

Define the account policy

Decide what resources each hosting package should receive and how you will investigate an account that reaches its limits. CloudLinux provides account-resource tools for supported shared-hosting environments; the administrator still needs to configure an appropriate policy.

Check compatibility before converting

Review the supported operating system and hosting panel. Prepare a recovery plan before changing an existing production server. Resource controls cannot create more physical capacity than the VPS provider supplies.

Review the purchase

LicenseCage CloudLinux includes KernelCare and offers regular monthly and discounted annual billing. Temporary promotions are listed separately. Check existing package inclusions and the selected edition. Follow our documentation for the LicenseCage activation method.

A practical example

If one customer repeatedly consumes the resources available inside a VPS, distinguish the provider's VPS allocation from the resources assigned to individual hosting accounts. CloudLinux can help implement account-level policies in a supported hosting environment, but it cannot add physical CPU time or memory to the allocation purchased from the provider.

Checks to make

  • Identify which accounts and workloads are responsible for the observed contention.
  • Review the VPS allocation and the hosting package limits separately.
  • Check application, database and background-job behavior before changing account policies.
  • Monitor the result after a controlled adjustment and communicate limits to customers.

Making the decision

Define how the hosting team investigates repeated limit events instead of only increasing thresholds. For purchasing, compare the regular CloudLinux monthly and discounted annual plans, including KernelCare, and consider temporary promotions separately. Installation and conversion should follow the current documentation for the chosen environment.