PHP development · Cardiff & UK

Laravel upgrades & security

Bring Laravel, its PHP runtime and its workers into the same release plan.

Starting price
From £1,850 + VAT
Best for
Laravel applications with outdated dependencies or a blocked upgrade
Leaves you with
An agreed upgrade implemented and checked across web and background work
Scope & timing
We assess the application, hosting and release process before agreeing which framework, runtime and dependency changes belong in scope.

A clear scope. A useful outcome.

A Laravel application can look healthy in the browser while an old queue worker continues running yesterday's code. Framework upgrades and security patches need to account for the full application: PHP, Composer packages, configuration, database changes and every long-running process that does useful work.

We scope Laravel maintenance around the product's actual workflows. That may mean clearing a blocked framework upgrade, resolving dependency conflicts or coordinating a PHP security release on Forge. The result should be understandable to the team maintaining it, with deployment checks that cover both customer journeys and background processing.

  • A review of Laravel, PHP, Composer dependencies and the relevant upgrade constraints.
  • A scoped implementation plan for framework, package and application compatibility changes.
  • Checks for authentication, authorisation, validation and configuration in the affected code.
  • A deployment plan covering migrations, caches, queues and applicable Horizon, Octane or Reverb processes.
  • Verification of web requests and background jobs, with release notes and follow-up actions.

How the work runs.

  1. Trace the running systemMap the Laravel release, PHP installations, package versions and deployment tooling. List the queues, scheduled tasks and persistent processes that need attention during a release.
  2. Resolve the upgrade pathReview the relevant release guidance and dependency constraints. Decide the migration stages and any package replacements before mixing several major changes into a single deployment.
  3. Exercise the workflowsImplement and test in staging. Include permissions, validation, job retries and integration failures where they intersect the change, so a passing homepage is not the only release evidence.
  4. Deploy the whole changeRun the agreed migrations, refresh relevant caches and restart the appropriate workers. Confirm successful processing and capture the deployed versions and verification results.

Agree the boundaries first.

  • The engagement is application engineering and agreed security remediation, not an independent certification or a managed security operations service.
  • New product features and unrelated infrastructure changes are separated from the upgrade scope.

Questions before we start.

Does Laravel Forge automatically patch PHP for PHP2Shell?
Forge's October 2026 guidance states that automatic security updates do not patch PHP. Each installed PHP version needs attention. We check the provider guidance and the running services rather than assuming the server's general update setting covers the issue.
Can you upgrade a Laravel application several versions behind?
We start with the framework's upgrade path and the packages that constrain it. Several version steps may be needed. We agree the stages and acceptance checks after assessment, including replacements for dependencies that are no longer maintained.
Will you check queues and scheduled jobs?
Yes, where they form part of the agreed application scope. We identify the relevant workers, restart requirements and observable job outcomes, and check that deployment has not left background work on an older runtime or code release.
Do we have to move away from Forge?
No. Hosting migration is a separate decision. Where the current setup can support the required release, we work within it and document any operational changes needed to keep the application maintained.

Work directly with QDev

Tell us what needs to change.

Name, email and a project message are required.

10 to 2,000 characters. Include the goal, current state and any deadline.

We use your details to assess your enquiry and reply. Read our privacy note.

Migration

PHP upgrades & migration

Move legacy PHP applications to a supported runtime. QDev plans compatibility fixes, dependency updates, staging tests and a controlled production migration.

You leave with A supported target runtime, tested compatibility fixes and release notes

Price From £1,850 + VAT

Explore PHP upgrades & migration

Start with the facts.

Send the site, the hosting provider and what has changed. We'll reply with the next step and what it depends on.