Working with Laravel?

Laravel app abandoned or stuck on an old version? We take it over.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

laravel.log

still failing

What it is

Laravel at a glance

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.

Type
PHP web framework
First released
2011
License
MIT
Built on
PHP and Composer
Maintained by
Taylor Otwell and contributors
Typically used for
Custom web apps, APIs, SaaS back ends, admin dashboards

The honest version

Laravel pros and cons

No technology is all upside. This is where Laravel earns its place and where it tends to cause trouble.

Where Laravel is strong

  • Pleasant to work inThe framework is written with the developer in mind. New people on a Laravel project tend to be productive in days rather than weeks.
  • Batteries includedEloquent, queues, Horizon, Nova, Sanctum and Livewire all come from the same team. You rarely have to glue together five libraries to get a normal feature done.
  • Active ecosystem and strong docsThe official documentation is kept current, and the community around it is large and busy. Most problems have already been answered somewhere.
  • Blade and ArtisanBlade templates stay readable as pages grow, and the Artisan command line turns routine chores into one short command each.
  • Easy to hire forThere is a large freelance and agency market for Laravel work, so bringing in extra help when you need it is usually straightforward.

Where Laravel bites

  • Performance tuning is on youIn production you are expected to cache the routes, config and compiled views yourself. Skip that and even a small app feels sluggish under load.
  • Major upgrades drag the stack with themMoving from 8 to 9 to 10 to 11 usually means new Symfony versions and a newer PHP as well. One version behind is routine, three is a project.
  • Eloquent makes N+1 queries easyThe ORM is comfortable enough that developers forget it is hitting the database. A single page can fire hundreds of small queries before anyone notices.
  • Queue workers need a supervisorJobs run in long-lived PHP processes. Without Supervisor or a similar watcher they quietly die, and the queue backs up until someone checks.
  • EOL versions turn into liabilitiesAn app left on Laravel 5 or 6 stops getting security fixes, and so does the PHP it needs. Every month it sits there the fix gets more expensive.

Sound familiar?

Common Laravel problems we fix

The Laravel problems that bring people to us, and what you have once each one is fixed.

composer install: could not be resolved

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

developer unreachable

The original developer vanished

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

Target class [App\Services\Bar] does not exist.

It broke after a deploy

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

Horizon failed: Redis connection refused

Queued jobs stopped running

Workers that crashed and were never restarted, a Redis that moved, or Horizon running under the wrong user.

Queues supervised and monitored

TTFB 2.9s on every page

The app is slow under normal traffic

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

No application encryption key has been specified.

Fresh server, nothing works

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

last tested restore: never

No tested backup of the database

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

Laravel help, from takeover to upkeep

Call us for one upgrade, or hand us the whole app.

Takeover
We pick up a Laravel codebase from a developer who has moved on, get it building and deploying again, and document what is actually in there.
Upgrades
Laravel 5, 6 or 7 brought forward to a supported major version, with the PHP bump and the Symfony changes that come with it.
Performance
N+1 queries found, indexes added, route and view caches put in place, with page times measured before and after.
Queues and background work
Horizon set up properly, workers supervised, failed jobs visible instead of silently piling up.
Custom features
New screens, APIs and integrations built into the existing app without breaking what already works.
Managed Tech
Framework and dependency upgrades, queue worker supervision, uptime checks on the app itself, and an engineer who already knows the codebase when a release goes sideways.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Laravel alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Laravel questions

Something else? Call+1 737 727 7327

Can you take over a Laravel project from the original developer?

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.

How do I upgrade Laravel 5.x to Laravel 11?

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.

Why does my Laravel queue stop processing jobs?

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.

Why are Laravel pages suddenly slow after deploy?

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.

Is it worth rewriting a Laravel app or just upgrading it?

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.

How much does Laravel help cost?

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

Laravel app giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.