It’s shocking that this still hasn’t been addressed—especially since users were requesting it as far back as 2016.

Most server setups allow multiple PHP-FPM versions to run simultaneously, with Nginx configurations assigning specific versions per site. Implementing this is a basic feature, not a technical hurdle, yet Cloudways has ignored it for nearly nine years. That’s inexcusable.

Once again, I’ve hit this roadblock today. Cloudways, this is unacceptable.

PHP-FPM inherently supports multiple versions, so why doesn’t Cloudways? A proper solution would allow users to:

1) Enable multiple PHP versions at the server level (with a default).

2) Assign the required version per application( Add Per-Application PHP Version Control )

Even budget hosts offer this flexibility. For a premium managed service to lack such a critical feature—without even acknowledging it—is baffling.

This Isn’t Just a Request—It’s a Necessity
We manage 100+ applications, and upgrading PHP globally isn’t an option. Testing and fixing every app simultaneously is impossible. Per-application PHP version control is mandatory. If this isn’t implemented by April 2024, we’ll have no choice but to migrate to a platform that actually meets modern standards.

When I reached to cloudways support team, their "solution" was to add another server. It’s lazy, costly, and proves how out of touch Cloudways is with real-world needs.

Falling behind like this is unacceptable in our rapidly evolving industry. Cloudways, when will you finally listen to your users?