HostPress is a German managed WordPress hosting company based in Saarland, serving over 5,000 customer websites from its own hardware across three data centers in Germany. Founded in 2016, the company built its reputation on premium B2B hosting — highly individual setups for customers who outgrow standard managed hosts. From day one, HostPress ran CloudLinux for tenant isolation. But by 2024, their security stack wasn’t consistent: ImunifyAV+ ran on every server, while full Imunify360 coverage with its proactive firewall was limited to part of the fleet.

After joining the CloudLinux VPS Bundle program, HostPress upgraded to CloudLinux OS Shared Pro and rolled out Imunify360 across all servers. 
As a result, more attacks are now handled automatically, fewer security support tickets, and a simpler product where every customer, including the smallest, gets the full stack without needing to upgrade.

The Problem With a Split Stack

HostPress has run CloudLinux since the day they set up their first shared hosting server in 2016. Isolating customer environments was never optional. Nearly half of their managed VPS customers are agencies or multi-brand businesses running dozens of WordPress sites on a single server. The other half are high-traffic e-commerce operations where a security incident isn’t just an inconvenience, it’s a business problem.

For most of those years, ImunifyAV+ handled scanning and malware cleanup across the fleet. On selected VPS servers, full Imunify360 was also active, bringing the firewall layer that blocks threats before they reach a site. On the rest, it wasn’t.

Marcus had a clear view on what the standard should look like. “We didn’t want to tell a customer: ‘you don’t have that feature because you’re not on the bigger plan,'” he says. “We’re a specialized company. Our customers already pay more than they would at a standard host. The expectation is that they get the best.”

New Standard for Every Server

The CloudLinux VPS Bundle gave HostPress the commercial structure to do what they wanted to do anyway: upgrade every server to the same standard. A combined licence for CloudLinux and Imunify360, purpose-built for VPS environments, made a fleet-wide upgrade economically viable.

Joining the program meant two things happening in parallel. First, upgrading from the legacy CloudLinux OS to Shared Pro meant adding enhanced resource management, centralized monitoring, and PHP X-Ray to the standard toolkit. Second, rolling out full Imunify360 across every server in the fleet.

The decision wasn’t driven purely by cost. HostPress had a Plesk licensing arrangement that meant the economics would improve over time rather than immediately.

“We didn’t make this decision only because of price. We wanted the best solution for our customers.”

The CTO led the rollout through 2025. It went smoothly.

What Changed Across the Fleet

With Imunify360 deployed on every server, HostPress now handles significantly more attacks automatically. The difference between ImunifyAV+ and Imunify360 isn’t just scanning depth — it’s the firewall layer. Where ImunifyAV+ detects and cleans, Imunify360 blocks proactively. The support queue reflects that.

Centralized monitoring, included in the VPS Bundle, gave the team operational visibility across the fleet they didn’t have before. “We love the centralized monitoring — it’s included,” Marcus says.

PHP X-Ray, now part of every server’s standard toolkit, sharpened the team’s performance diagnostics. When a customer’s WordPress backend slows down, PHP X-Ray identifies the problematic plugin or query without anyone needing to log into the WordPress installation. HostPress uses it as part of their performance check service, helping customers optimize to a defined standard without touching content or code.

Every Customer, the Full Stack

Every HostPress customer (shared hosting or managed VPS) now runs on CloudLinux, Imunify360 and KernelCare. No plan tiers, no features held back for an upgrade.

That also simplifies how HostPress presents its product to customers. The stack is the same everywhere. Support teams don’t need to qualify which server a customer is on before troubleshooting. And as the Plesk licensing arrangement matures, the unit economics per managed server improve further.