Imunify360 is often described as a server security suite, but its licensing question is surprisingly simple: how many hosting users does the server need to protect?
The current Imunify360 pricing model is based on the number of non-admin hosting accounts covered by the server. That makes account count the first thing to measure before you compare license tiers.
How Imunify360 licensing works
Imunify360’s current pricing page groups plans by hosting users: a single-user tier, up to 30 users, up to 250 users and unlimited users. Imunify360 says the software works server-wide, so the license needs to cover the hosting accounts on that server rather than being purchased separately for each website.
That makes the sizing exercise straightforward. Count the hosting accounts that need protection, then choose the smallest tier that gives you room for normal growth.
What Imunify360 actually does
Imunify360 is more than a traditional antivirus scanner. Its current documentation lists an advanced firewall, intrusion detection and protection, malware scanning and cleanup, patch management, reputation monitoring and proactive defense for PHP applications.
That combination matters on shared or multi-account hosting because the threat model is not limited to the server operating system. Compromised WordPress sites, stolen credentials, malicious uploads and brute-force attacks can all become operational problems for the hosting provider.
Imunify360 also has features for scanning user and system cron jobs and reducing scan resource usage, which can be useful on busy hosting nodes.
How to choose a user tier
| Server situation | Licensing approach |
|---|---|
| One hosting account | Single-user tier |
| Small agency or VPS | Up to 30 users |
| Larger shared hosting node | Up to 250 users |
| Large hosting node | Unlimited users |
Do not size the tier from the number of websites alone. A customer may have multiple domains under one hosting account, while another business may operate many separate accounts. The licensing model is account-oriented.
When is Imunify360 worth it?
Imunify360 makes the most sense when the cost of manually detecting, cleaning and preventing malware is higher than the cost of a centralized security layer.
- Shared hosting: isolation and automated detection can reduce the blast radius of compromised sites.
- Agencies: a single security console can simplify protection across many customer accounts.
- Hosting providers: automated scanning and reputation monitoring can reduce repetitive support work.
- Single-site VPS owners: the value depends on the importance of the site and your ability to handle security manually.
How Imunify360 fits with CloudLinux and a control panel
Imunify360 is a security layer, not a replacement for a hosting control panel. It can work alongside panels such as cPanel, Plesk and DirectAdmin, and it can also run standalone on supported Linux distributions.
CloudLinux solves a different problem: account-level resource management and isolation. A common hosting stack can therefore use a control panel for administration, CloudLinux for resource isolation and Imunify360 for security operations.
If you are evaluating the broader stack, our WordPress VPS software stack guide explains how the layers fit together.
FAQ
Is Imunify360 only for cPanel?
No. Imunify360’s current documentation and pricing support cPanel, Plesk, DirectAdmin and standalone deployments on supported Linux systems.
Does one license protect one website?
The licensing model is server-wide and based on the number of hosting users covered, not a separate license for each website.
Do I need Imunify360 if I already use CloudLinux?
They address different areas. CloudLinux focuses on account isolation and resource control, while Imunify360 focuses on server and website security. Many hosting environments can benefit from using both, but the decision should be based on your threat model and operating workload.
Where can I compare an Imunify360 license?
You can browse the LicenseCage catalogue for Imunify360 and other server security licenses.
Bottom line: count hosting users first, then compare the security workload you want to automate. The right Imunify360 tier is the smallest one that covers the server today without making normal growth immediately force another licensing decision.
Image credit: FlyD via Unsplash.
