PHP 8.5 for CentOS 7
Current, upstream-supported PHP on an EOL OS — the opposite of a backport.
Remi ships no PHP 8.5 for EL7. The GetPageSpeed PHP 8.5 stack is a complete, signed build of current PHP for CentOS 7 / RHEL 7, one package away.
The gap
CentOS 7 went end of life in June 2024, and the PHP ecosystem's EL7 packaging stopped with it: Remi ships no PHP 8.5 builds for EL7 at all. If your OS migration is scheduled but your PHP upgrade cannot wait, there was no supported path — current PHP simply did not exist for CentOS 7.
The GetPageSpeed PHP 8.5 stack fills that hole: a complete build of current PHP 8.5 for EL7, packaged both under base php-* names and as a parallel-installable php85 software collection, signed, and updated as upstream releases. Your application gets an actively supported runtime while the OS migration happens on its own timeline.
Install
Replacing system PHP (base-name php-*)
yum -y install https://extras.getpagespeed.com/release-latest.rpm yum-config-manager --enable getpagespeed-extras-php85 yum -y install php85-getpagespeed-stack
Side by side (software collection, php85-php-*)
yum -y install https://extras.getpagespeed.com/release-latest.rpm yum install php85-php-cli php85-php-fpm systemctl restart php85-php-fpm scl enable php85 -- php -v
The base-name stack replaces the system PHP packages under php-* names. Switching a production host onto it is a maintenance operation: snapshot your package set first, and yum downgrade reverts. The channel stays enabled so a plain yum update keeps the stack current.
The php85-php-* collection is GetPageSpeed's own (Remi never built PHP 8.5 for EL7) and lives in the always-enabled main repository, so it installs next to any existing PHP without enabling a channel. scl enable php85 finds it wherever it lives, so scripts stay the same as for the older collections.
Two differences from the older channels: PHP 8.5 has no oci8 (upstream dropped it from core, and Remi ships none either), and zip is the bundled extension, packaged as php-zip / php85-php-zip rather than php-pecl-zip.
The stack rides maintained GetPageSpeed libraries instead of EL7's frozen ones: OpenSSL 3.5 LTS, ICU 74, libzip 1.11, libpq 17 and libxml2 2.13. Every channel, this one included, is tested serving real pages through both mod_php and PHP-FPM.
Free for personal use. Running it for a business?
Patching EOL PHP is ongoing work: every new PHP CVE has to be ported to branches upstream abandoned years ago, then built and tested on EL7. Commercial production use requires GetPageSpeed Ultra or GetPageSpeed Fleet: either one funds that work and keeps your production servers covered for the next one, together with the full GetPageSpeed repository. When a new fix is ready for the PHP your servers run, we email you the exact command. Ultra covers up to 10 servers running your own services; Fleet is the plan for servers that host client websites, or for more than 10 servers. 250+ employees or $10M+ revenue, or need a contractual SLA and invoice/PO? That is Enterprise.
Ultra, $500/year Fleet, from $800/year Contact us about Enterprise
Frequently asked questions
Is this an EOL backport like the other Everpatch PHP channels?
No — it is the reverse. PHP 8.5 is fully supported upstream; what is end of life here is the OS. The stack packages current PHP for CentOS 7, so the runtime stays supported even while the OS is not.
Why is there no Remi PHP 8.5 for CentOS 7?
Remi stopped building for EL7 when the OS went end of life; PHP 8.5 arrived after that. Building modern PHP on EL7 requires a newer toolchain and library set than the OS ships, which the stack carries along.
Will it replace my existing PHP packages?
The base-name stack does: it ships under php-* names and takes over the system PHP, which is why installing it is a deliberate maintenance step. It is reversible with yum downgrade. To keep your current PHP untouched, install the php85 software collection instead and move sites over one PHP-FPM pool at a time.
My application cannot run on PHP 8.5 yet — what then?
Step down to the PHP 8.4 stack, or stay on your version with its Everpatch channel (8.3, 8.2, 8.1, 7.4, or the older lines) — known CVEs stay closed while you port at your own pace.
Do I need a subscription?
Not for personal, development or evaluation use: the PHP packages install from the public GetPageSpeed repository with no signup. Commercial production use requires a subscription under the repository terms: GetPageSpeed Ultra ($500/year) for up to 10 servers running your own services, or GetPageSpeed Fleet (from $800/year) for servers that host client websites or fleets larger than 10. Either one funds these backports and keeps your servers covered for the next EOL PHP CVE. Organizations with 250+ employees or $10M+ revenue, or anyone needing a contractual SLA and invoice/PO procurement, should contact us about Enterprise. To license servers without registering IP addresses, place your license file at /etc/getpagespeed/license.jwt.