# CWP 1.8: Finally PHP 8.4 and 8.5… but where is CWP really going?
Let's be honest: **seeing PHP 8.4 and PHP 8.5 finally becoming available in CWP 1.8 is good news.**
But is this really a major step forward in 2026?
PHP 8.4 was released in **November 2024**.
PHP 8.5 was released in **November 2025**.
We are now in **August 2026**.
That means CWP is roughly **21 months behind PHP 8.4 and 9 months behind PHP 8.5**.
This is not an unfair criticism. It is simply a fact.
And that fact should make the CWP community ask some serious questions.
---
## The problem is no longer just PHP
For a long time, a certain amount of delay could be considered acceptable.
But today, the gap seems to affect much more of the CWP ecosystem.
Administrators are waiting for answers regarding:
* new PHP versions;
* modern operating systems;
* modern web technologies;
* newer Apache and Nginx versions;
* HTTP/2 and HTTP/3;
* modern security technologies;
* virtualization technologies;
* performance improvements;
* backup solutions;
* integration with modern security products;
* and, most importantly, CWP's overall strategy.
The problem is that **we don't really know where CWP is going.**
And that may be the biggest problem of all.
---
# Where is the roadmap?
This is the question many administrators are asking.
**What is CWP's official roadmap for the next 12, 24 or 36 months?**
Which technologies are priorities?
Which operating systems will be supported?
When can we expect major releases?
Which features are actually being developed?
What has been abandoned?
What is simply delayed?
Today, getting clear answers to these questions is far too difficult.
And for administrators running production infrastructure, **uncertainty is a problem.**
We cannot build professional hosting infrastructure based on the hope that a feature will eventually arrive.
---
# The changelog needs to change
A changelog is one of the most important communication tools a development team has.
Yet CWP's changelog too often fails to provide a clear picture of the actual evolution of the product.
An administrator should be able to open the changelog and immediately understand:
**"This is what was developed. This is what is coming. This is what is planned. This is what has been fixed."**
That is not an unreasonable request.
It is basic communication for software that is used in production environments.
---
# Competition is moving forward
While CWP continues at its current pace, **other control panels are continuing to evolve.**
Modern technologies are released rapidly.
PHP versions move forward.
Linux distributions evolve.
Security requirements become increasingly demanding.
Hosting providers have to keep up.
And when a control panel falls too far behind, administrators naturally start looking elsewhere.
Not necessarily because competitors are better at everything.
Sometimes simply because they provide a stronger impression of **active development and a clear direction.**
---
# CWP still has something extremely valuable
And this is exactly why this discussion matters.
**CWP has a community.**
There are thousands of administrators who know the platform extremely well, have been using it for years, and would actually prefer to continue using it.
But that community needs to know that CWP has **a vision for the future.**
We are not asking for every feature to be released tomorrow.
We are asking for something much simpler:
### Give us a direction.
Tell us what is coming.
Tell us what is being developed.
Tell us what is delayed.
Tell us what is not planned.
And most importantly, **communicate regularly.**
---
# PHP 8.4 and 8.5 should be a beginning, not a destination
To be clear:
**Congratulations on CWP 1.8 and the addition of PHP 8.4 / 8.5.**
This is a positive step.
But it should not be considered the end of the problem.
It should be **the beginning of a new development cycle for CWP.**
A cycle with:
* more regular releases;
* a properly maintained changelog;
* a public roadmap;
* better communication;
* faster adoption of current technologies;
* a clear strategy for modern operating systems;
* and a long-term vision.
---
# The real question
So the question is not:
**"Does CWP 1.8 finally support PHP 8.4 and 8.5?"**
The real question is:
## "Will CWP remain technologically relevant over the next 3, 5 or 10 years?"
Because a hosting control panel cannot simply catch up with technologies months after they are released.
It needs to be able to **anticipate them.**
CWP still has a place in the hosting industry.
CWP still has a community.
CWP still has many loyal users.
But that loyalty should never be taken for granted.
**We want to continue using CWP.**
But for that to happen, we need to see that CWP genuinely wants to keep moving forward.
### PHP 8.4 and 8.5 are welcome.
**Now show us what comes next.**
Topic: CWP 1.8 is out, and has options for PHP 8.4 & 8.5 (Read 88 times)
