PHP 8.2 reaches end of life on 31 December: a two-day Health Check shows where your system stands
Support for PHP 8.2 ends on 31 December 2026. Many owners do not know which version they run or what depends on it. What a read-only Health Check looks at in two days, what you get back, and what it costs.
PHP 8.2 stops receiving security fixes on 31 December 2026. For the owner of a system built on it, that date is not an abstract milestone: from January, a flaw like the ones fixed in this month's PHP release gets no patch for that version. The question I hear most before a date like this is simple. What do I actually run, and how bad is it?
Most owners cannot answer it. The developer who built the system moved on, the server is looked after by whoever has time, and the only documentation is the system itself. That is the situation the Health Check is made for.
What the Health Check is
It is a fixed-price review of two days, 12 hours at EUR 90, so EUR 1,080 excl. VAT. It is read-only: I do not change anything on your system. I read, run and write, and a free intro call comes first so we agree what is in scope.
Day one: how it runs
- Versions: operating system, PHP, database, framework and main packages, each checked against its official end-of-life date.
- Hosting: how it is deployed, how it is backed up, when a restore was last tested, what is monitored.
- Security basics: open ports, TLS, headers, dependencies with known advisories, how secrets are stored.
Day two: how it is built and used
- Code: where change is risky, how parts depend on each other, what the tests cover.
- Hours: the repetitive work in and around the system, and what an agent or an integration could save.
- The plan: the order of steps, with effort ranges, so that nothing stops while the work is done.
What you get back
A report in plain language, with findings ranked by value and risk and an hours estimate per item. After that comes a walkthrough call where you can challenge anything in it. The report is yours, whether or not you ask me to do the work. Nothing in the price is a down payment on a project.
What it does not do
It does not fix anything, and it is not a penetration test. If the report shows that a deeper security look is warranted, the security quick scan is the next step: EUR 720 excl. VAT for 8 hours. If it shows a version past its end of life, the upgrade is quoted separately, per step, so you can stop after any of them.
Why before the end of the year
An upgrade from PHP 8.2 to 8.4 is usually small when the system has tests and current packages, and large when it does not. You find out which one you have from the review, not from the upgrade. Two days now cost EUR 1,080. Finding the same facts in the middle of an incident costs more, and you do not get to choose the order of the work.
The Health Check is at /health-check. Tell me what the system is, which version it runs if you know it, and where it is hosted. I reply within one working day with what I would look at first.
This article is about: Health Check
More news: PHP security release of 21 October fixes two critical remote code execution bugs · Customers now ask for AI on their own data: an MCP server in front of the API is the safe answer · all news