Security and updates
Your software hasn’t been updated in years.
In one or two weeks, your live software runs on supported versions, tested, with a way back if anything goes wrong.
Support has an end date
Once a version stops getting security fixes, a hole found in it stays open.
| Version | Security support |
|---|---|
| PHP 8.2 | Security fixes end 31 Dec 2026 |
| PHP 8.3 | Security fixes only, until 31 Dec 2027 |
| Laravel 11 and older | No security fixes since 12 Mar 2026 |
| Laravel 12 | Security fixes until 24 Feb 2027 |
| Laravel 13 | Current, needs PHP 8.3 or newer |
As of 22 November 2026. Sources: php.net supported versions and Laravel release notes.
For PHP, Laravel and Node
For a company running a PHP, Laravel or Node application that nobody has updated in a year or more.
We move the language, the framework, the server and its packages onto versions that still get security fixes.
On our own platform first
SportPoint, the platform Daniel co-founded, has run Laravel 13 in production since 28 October 2026. Its releases cause no downtime.
Checks before every step
We took one client platform across five major framework versions and onto new servers in ten working days, against an estimate of 33. AI did much of the work, and no step moved on until its checks had passed.
Three ways to do it
The update
Just the move onto versions that still get security fixes.
The update and a security clean-up
The update, plus keys and passwords changed, old access removed, a backup restored once and spending limits set.
Both, then monthly updates
The update and the security clean-up, then we keep it updated every month.
Fixed price, set after the free first step.
What it isn’t
It isn’t a penetration test, and it isn’t a guarantee. It gets your software onto versions that still get security fixes.
Start with a free version check
Send your link through the free app health check and tell us which versions you’re on, if you know. Daniel replies within one working day.