← Back to blog

The PHP Version Talk I Have With Every SaaS Client Eventually

11 Nov 2026 · 4 min read

Every so often I check php.net/releases just to see where things stand. It's a dry little page, a list of version numbers and dates, but it tells you almost everything you need to know about whether a client's app is sitting on solid ground or a slowly cracking one.

Here's the pattern PHP follows, roughly. A new version comes out every November. It gets two years of active support, meaning bugs get fixed and new features land. Then it gets a further year of security-only support, where only serious vulnerabilities get patched. After that, it's done. No more fixes, no more patches, nothing. You're on your own.

So a version released in November 2022 is out of active support by late 2024 and fully end of life by late 2025. Three years, start to finish. That's not a long time when you think about how long some SaaS products stick around.

I picked up a client last year running a subscription billing app on PHP 7.4. It had been quietly working for four years. Nobody touched it because nobody needed to, which is exactly the problem. PHP 7.4 went end of life in November 2022. That app had been running without security patches for well over a year before anyone noticed. The owner wasn't being careless, he just didn't know the clock was running. Most founders don't. Why would they? They hired someone to build the thing, it worked, they moved on to selling it.

Why this actually matters, beyond the scary word "vulnerability"

It's not just about hackers, though that's the headline risk. Hosting providers eventually stop offering old PHP versions on their control panels. Composer packages drop support for versions nobody's maintaining anymore. Laravel itself has minimum PHP requirements that climb with every major release, Laravel 11 needs PHP 8.2 at minimum, Laravel 12 needs 8.2 as well but runs much better on 8.3 or 8.4. If your app is stuck on an old PHP version, you're also stuck on an old Laravel version, which means you're stuck without the security patches Laravel itself ships for its supported releases.

It compounds. That's the bit I try to explain without sounding like I'm selling fear. An app two versions behind on PHP is usually two or three versions behind on Laravel too, and by that point an upgrade isn't an afternoon's work, it's a project.

What I actually do about it

For every client I work with on a retainer, I check their PHP version against the support table maybe twice a year. Nothing fancy, just a reminder in my calendar. If something's heading towards end of life within six months, I flag it early, not in a panic two weeks before.

For the upgrade itself, I lean on Rector to catch deprecated syntax automatically before I touch anything by hand. I run the test suite first, obviously, though I'll admit on older projects there sometimes isn't much of a test suite to run, which makes the whole thing slower and more nerve-wracking than it should be. Composer's own audit command is worth running too, it'll flag packages with known vulnerabilities even before you touch the PHP version.

I do the upgrade on staging, let it sit there for a week if the client's willing, then push it live outside business hours. Nothing clever. Just unglamorous, careful work.

If you're a founder reading this and you genuinely don't know what PHP version your app is running, that's the first thing to find out. Ask whoever built it, or run php -v on the server yourself if you have access. It takes two minutes and it's the kind of thing that's cheap to check and expensive to ignore.