PHP 8.2 security support ends 31 December
If your Laravel application still runs on PHP 8.2 or older, it stops getting security fixes at the end of the year. We upgrade business-critical Laravel applications one version at a time, without freezing your roadmap for months.
Why it matters
The further behind an application falls, the harder every upgrade becomes. Upgrading should be scheduled like an MOT, not left until the wheels are falling off.
Unsupported PHP and Laravel versions stop receiving security patches, and known vulnerabilities are published for them. Cyber Essentials requires software in scope, including the PHP runtime, to be supported, and ISO 27001 expects you to act on known vulnerabilities.
How we approach your upgrade
-
01
A short discovery first: which versions you're on, which packages are unsupported, and what can simply be removed. It turns a guess into a plan.
Take
stock -
02
We agree timelines, any development freeze and how the switch-over happens. For internal systems we often run old and new side by side for a while.
Plan around
the business -
03
One version at a time, pausing at each long-term support release, with automated and manual testing at every step. Refactoring waits until the upgrade is stable.
Upgrade,
then test
Legacy systems, brought up to date
-
Vivalda
Read the case studyHow we helped a building cladding company finally launch the website rebuild they'd been postponing for years
-
Caters News
Read the case studyHelping a century-old media agency modernise a business-critical system built around one developer.
-
Plymouth
Learning PartnershipRead the case studyTaking over a critical recruitment platform and building the resilience to keep it running.