The app is stuck on Laravel 5 or 6
Dependencies that no longer install, a PHP version the host is retiring, and nobody willing to start the upgrade.
Brought up to a supported version
Working with Laravel?
Most Laravel apps that reach us were built quickly by one developer who has since moved on. The code still runs, but nobody wants to touch it, and the PHP version it needs is going out of support. We pick it up, get it onto something current, and keep it that way.
What it is
Laravel is an open-source PHP web framework created by Taylor Otwell and first released in 2011. It follows an MVC pattern and ships as a Composer package, which means you pull it in as a dependency rather than installing a server product.
Out of the box it brings Eloquent for talking to the database, Blade for templates, built-in authentication, queues, caching and an Artisan command-line tool. Underneath it leans heavily on Symfony components. A new major version lands roughly every year, which is part of its appeal and part of why so many apps end up out of date.
The honest version
No technology is all upside. This is where Laravel earns its place and where it tends to cause trouble.
Sound familiar?
The Laravel problems that bring people to us, and what you have once each one is fixed.
Dependencies that no longer install, a PHP version the host is retiring, and nobody willing to start the upgrade.
Brought up to a supported version
No handover, no access to the repository or the server, and a running app that nobody dares redeploy.
Code, hosting and accounts back in your hands
A composer autoload that was never regenerated, a cached config pointing at old class names, or a service provider removed by mistake.
Deploys that work the same way every time
Workers that crashed and were never restarted, a Redis that moved, or Horizon running under the wrong user.
Queues supervised and monitored
N+1 queries from Eloquent, route and view caches that were never warmed in production, and a database without the indexes it needs.
Pages served in a fraction of a second
A .env that never made it onto the new box, or storage permissions that stop the app writing its own logs.
Environment captured and reproducible
Nightly dumps that may or may not be complete, kept on the same server they are supposed to protect.
Backups off-server, restores rehearsed
What we do
Call us for one upgrade, or hand us the whole app.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes, and it is one of the most common things we are asked to do. We get access to the code, servers and third-party accounts, stand up a working local copy, write down what the app actually does, and then get it building and deploying cleanly before we change anything else.
Not in one jump. We move through the major versions in order, with the matching PHP and Symfony changes at each step, running the test suite and the app against a copy of production between them. If there is no test suite we add enough coverage to upgrade safely first.
Usually the worker process died and nothing restarted it. Laravel expects a supervisor such as Supervisor, systemd or Horizon to keep workers alive, restart them after code deploys, and alert when jobs keep failing. Without that, one bad job can stall the queue for days.
Most often the production caches were cleared and never rebuilt. Running php artisan config:cache, route:cache and view:cache as part of the deploy brings response times back. N+1 queries introduced in the new release are the other common culprit.
Upgrading is almost always cheaper and faster, even from an old 5.x version. We only recommend a rewrite when the original design no longer fits the business or the code is genuinely unmaintainable, and we show you the numbers before suggesting it.
Estimates are free. Tell us what the app does and what is going wrong, and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: