Type at least 3 letters to search

·15 min read

Laravel Support and Maintenance: What It Costs per Month and What Is Included

Laravel support cover: an open watch movement, a loupe and tools beside a service logbook listing dated changes and their reasons

A launched Laravel site on plain support usually needs 4 to 8 hours of work a week. A site that keeps growing can need 40. Here is what goes into those hours, how support is billed, what to ask a team before you hand over the keys, and what happens to a project that has no history of its changes.

SHORT ANSWER

The short answer

Support for a Laravel application costs as many hours as the application asks for, and the biggest factor is not its size but whether it is still growing. A launched site that only needs to stay safe, fast and working usually takes 4 to 8 hours a week. A site that is being extended can take up to 40 hours a week, because most products today launch as an MVP and keep being built after release.

At our rates that means support from $1,000 a month for the first case, and a dedicated developer or a small team for the second. Our Laravel developers work at $55 to $100 an hour depending on seniority, and a dedicated team starts from $8,000 a month. Hosting, paid packages and licences are paid separately in both cases.

ModeHours a weekWhat goes into the hours
Support only4 to 8Framework, PHP and package updates, security fixes, backups and restore checks, monitoring, small changes, help when something breaks
Steady growth10 to 20All of the above, plus new pages, integrations and features on a monthly plan
Active developmentup to 40A developer, sometimes with a tester, building the product release after release

The table reflects what we see on our own Laravel projects, not an industry survey. The point that does not change with prices is the logic: you pay for support either regularly and predictably, or all at once on the day something breaks.

WHAT IS INCLUDED

What support includes

A Laravel site that is not being touched still changes underneath. The framework releases a new major version every year, each version gets 18 months of bug fixes and two years of security fixes, and PHP, the server, the database and dozens of packages move on their own calendars. Support is the work that keeps all of that in step.

In a typical month the work falls into a few groups:

  • Updates. Laravel and PHP minor releases, Composer packages, front-end dependencies. A security advisory gets checked the day it appears; the composer audit command lists the packages with known vulnerabilities.
  • Safety. Backups that are actually restored on a test copy from time to time, access reviews, SSL and domain renewals, a look at the logs for anything unusual.
  • Monitoring. Uptime, errors, queues and scheduled jobs. A queue that stops processing does not show on the home page, but orders and emails stop with it.
  • Small changes. Texts, a new field in a form, a fix in a report, a new redirect. In most months this is where half of the hours go.
  • Help when something breaks. A payment provider changes its API, a mail service turns off an old login method, the server provider moves the site to new hardware. Someone has to know the code well enough to answer the same day.

Once a year support also plans the next major upgrade. A move from one current Laravel version to the next is usually short, and Laravel's own guide estimates the code changes for 12 to 13 in minutes. A move across several versions is a project of its own; our case of upgrading Laravel 7 to 13 shows what it involves, and the guide on upgrading an old Laravel or PHP site covers costs and deadlines.

CANNOT WAIT

When an update cannot wait

Most security advisories are routine: a fix lands, it goes in with the next monthly update, nobody notices. A few cannot wait a month. Three real cases show what the difference looks like, and why support reads every advisory the day it appears.

A hole from 2018 that bots still use. In August 2018 Laravel fixed CVE-2018-15133: on versions 5.5 and 5.6, anyone who knew the application key could make the server run their code through a cookie. Laravel called the release "recommended as an immediate upgrade" and told everyone to change the key. Six years later, in January 2024, the FBI and the US cybersecurity agency CISA published a joint warning about the Androxgh0st botnet: it scans the internet for Laravel sites, looks for open .env files with keys and passwords, and uses exactly this hole on sites that were never updated. CISA added it to its catalog of vulnerabilities exploited in real attacks on the same day.

Debug mode on a live server. CVE-2021-3129 sat in Ignition, the error page Laravel used at the time: with debug mode on, anyone could run code on the server without logging in. The fix, Ignition 2.5.2, came out in November 2020, the score is 9.8 out of 10, and CISA lists the hole as used in ransomware campaigns. Two lessons in one: keep the package updated, and never run a live site with debug mode on, because that page shows far more than a visitor should see.

When your version is no longer supported. In May 2026 Laravel fixed a high-severity flaw in the default email validation rule: a crafted address could tamper with outgoing mail, change its content or add recipients. The fix shipped in 12.60.0 and 13.10.0. Laravel 11, out of security support since 12 March 2026, did not get it. Two years earlier Laravel had patched a flaw in environment detection all the way back to version 6, long after its support ended. That was goodwill, not a promise, and the 2026 case shows the difference.

Packages around the framework count too. In July 2025 Livewire, a popular Laravel package for interactive pages, fixed a critical hole that allowed remote code execution in version 3.6.4. In March 2026 CISA added it to the same catalog of exploited vulnerabilities. A site whose framework is current but whose packages are a year old is not current.

The checks themselves are simple. This is what support runs and keeps in order on every Laravel project:

# .env on the live server
APP_ENV=production
APP_DEBUG=false

# which Laravel version is running
php artisan --version

# which installed packages have known vulnerabilities
composer audit

# versions of the packages that matter most
composer show laravel/framework livewire/livewire

One more line belongs to the server rather than the project. Security guides commonly recommend turning off register_argc_argv in the PHP settings used by the web server, which closes the door the 2024 environment flaw used. It is general hardening, not Laravel's official instruction, so agree it with whoever runs your hosting.

WHY HOURS DIFFER

Why one site needs 6 hours and another 40

The difference is almost never the number of pages. It is whether the business is still discovering what the product should be.

Most projects we start today launch as an MVP: the smallest version that can go to real customers, followed by months of building on what those customers do. That is a sound way to spend money, and our article on MVP as the cost of entry explains why. But it means the launch is the middle of the project, not its end. After release come the second payment method, the dashboard the sales team asked for, the integration with the warehouse, the mobile view of the account. That is development, and it can take a full working week every week.

The mistake is to budget for support and then ask for development. Six hours a week cannot carry a new module, and a team pushed to do both in that time starts cutting corners on the updates, the backups and the tests, which are exactly the things nobody sees until they are needed. It is better to name the two kinds of work separately: a fixed base for keeping the system healthy, and a development budget that rises and falls with the plan.

Support keeps the site alive. Development makes it grow. Pay for both separately.

A practical sign of which mode you are in: count how many requests for new features reached the team in the last three months. If it is one or two, you need support. If it is a list, you have a product in development, and it deserves a developer who knows it.

A CAUTIONARY CASE

What happened to a project we built

One story from our own practice explains better than any checklist why support is about knowledge, not only hours.

We built a system on Laravel for a client. Some time later the client moved to another team, which is a normal thing for a business to do. The new team did not work with Laravel. Instead of learning the code, they started writing scripts in Python with AI, for a newer version of Python than the project was set up for. The scripts did not work, and each attempt left more files behind in the project. Then they tried to repair things by editing directly on the server over SSH, and that did not work either. In the end they removed the whole back end and rebuilt the site on WordPress.

Our surprise was as large as it gets. The system had worked. It did not need to be replaced, it needed someone who could read it. The rebuild cost the client a working application, its logic and the time to recreate what it had already paid for once.

The lesson is not about Laravel or WordPress; we compare them honestly in Laravel or WordPress for a business site. It is about three habits that turn a fixable situation into a loss: working in a framework nobody on the team knows, letting AI write code nobody can check, and changing a live server by hand. Any one of them can be survived. Together they leave nothing to roll back to.

CHANGE HISTORY

Commits, and why a project needs a memory

The second thing we see again and again when we take over a project is simpler and just as costly: nobody wrote anything down. No commits for months, or commits that say "fix" and nothing else. Files changed straight on the server. No note of what was changed, where, or why.

A Laravel project without that history has no memory. The next developer cannot tell a deliberate exception from a mistake, cannot see why a strange line exists, and cannot undo last week's change because nobody knows what last week's change was. Every question costs hours of digging, and some questions cannot be answered at all.

This is the minimum we insist on in any support we provide, and what you can ask of any team:

  • All code lives in a git repository that belongs to the company, not to the developer.
  • Every change is a commit with a message that says what changed and why.
  • Nothing is edited on the live server by hand; changes go through the repository and a deployment.
  • Before a risky change there is a backup and a written way back.
  • A short working document in the repository explains how the project is built, what is unusual about it and what must never be done.

We keep such a document on our own site. Every non-obvious change is in it with the date, the files, the reason and the rollback, so any developer, and any AI assistant, starts from facts instead of guesses. We described the approach in our article on writing a codebase manual that AI can use.

A change nobody wrote down is a change nobody can undo.

AI IN SUPPORT

Where AI helps and where it hurts

AI has changed support work more than almost anything else in the last two years, and mostly for the better. On a clean Laravel codebase an AI assistant reads the structure quickly, finds where a change belongs and drafts it with far less effort than on a heavy CMS. Routine updates, tests for old code, explanations of a forgotten module: all of it is faster now.

The cautionary case above shows the other side. AI writes code with confidence whether or not it understands the project, and it does not know which strange line is a bug and which one protects a payment from being charged twice. In the hands of a team that cannot check the result, it produces more code, not better code. The same applies to fast-built MVPs; our article on vibe-coded MVPs covers when such code is worth keeping.

The rule we work by: AI drafts, a developer who knows the project decides, and git keeps the record. That combination is what makes 4 to 8 hours a week enough for a healthy site.

HOW IT IS BILLED

How support is priced

There are three common ways to pay for Laravel support, and each fits a different stage.

ModelHow it worksFits when
Monthly supportA fixed number of hours a month for updates, monitoring and small changes, with unused hours handled as agreedThe site is launched and mostly stable
HourlyYou pay for the hours actually worked, on one monthly invoiceWork comes in waves, or you need a specialist inside your own team
Dedicated developer or teamPeople work on your product full time or part time, month after monthThe product is being built after launch

Our website maintenance and support starts from $1,000 a month. Hourly work with our Laravel developers is $55 to $100 an hour depending on seniority. A dedicated team starts from $8,000 a month, and its size and roles are agreed before work starts. In every model, hosting, paid packages such as Nova or Forge, and other third-party licences stay on your account.

Two things are worth agreeing in writing whatever the model: how fast the team answers when the site is down, and what is handed over if you part ways. The second question is the one most contracts forget.

CHOOSING A TEAM

Questions to ask before you hand over the keys

Whether you are choosing a first support team or replacing one, these questions show quickly whether the people in front of you can be trusted with a live system:

  1. Where will the code live, and who owns the repository?
  2. How do you deploy changes, and do you ever edit the live server by hand?
  3. How often are backups restored as a test, and when was the last time?
  4. Which Laravel and PHP versions does our project run, and when does their support end?
  5. What do you write down after each change?
  6. If we stop working together, what exactly do we receive on the last day?

A good team answers all six without a pause, and the last one gladly. If you are inheriting a project from a previous contractor, start with an audit before any promises; our guide on taking over a project from another contractor lists what to collect, and our project takeover work does exactly that.

WHEN IT IS NOT ENOUGH

When support is not enough

Support keeps a healthy system healthy. It cannot fix a system that is years behind, has no tests and no history, or runs on versions that stopped receiving security fixes long ago. In that case the first step is an audit, then a choice between upgrading and rebuilding, and only then a support plan. Our website modernization work starts with such an audit, and the article on paying down technical debt after an audit shows how to order the work so the business keeps running.

The cheapest support is the one that starts the week after launch, with a repository, a backup and a written record from day one.

FAQ

Frequently asked questions

How much does Laravel support cost per month?

It depends on whether the site is still growing. A launched site on plain support usually needs 4 to 8 hours a week, and our support starts from $1,000 a month. A site under active development can need up to 40 hours a week, which is a dedicated developer or team, from $8,000 a month at our rates.

What does Laravel maintenance include?

Framework, PHP and package updates, security fixes, backups with test restores, monitoring of uptime, errors, queues and scheduled jobs, small changes, help when something breaks, and planning of the yearly major upgrade.

How often does a Laravel application need updates?

Security advisories should be checked as they appear, and minor updates applied monthly. Laravel releases a major version once a year; each gets 18 months of bug fixes and two years of security fixes, so a supported site moves to a new major version roughly every year or two.

Can AI maintain a Laravel site on its own?

No. AI speeds up updates, tests and routine fixes on a clean codebase, but it does not know which unusual line protects the business. It works well when a developer who knows the project checks every change and git keeps the record.

Is it safe to stay on Laravel 11?

Not for a site with real users. Laravel 11 has received no security fixes since 12 March 2026, and in May 2026 a high-severity flaw in email validation was fixed only in versions 12 and 13. The move from 11 to 12 is usually small and worth planning soon.

Why do commits matter for support?

Commits are the project's memory. Without them nobody can tell why a line exists, what changed last week or how to undo it, and every question costs hours. Each change should be a commit that says what changed and why.

What should we receive if we change support teams?

The repository with full history, access to hosting, domain and every paid service in the company's name, backups, the deployment process and a written description of how the project is built and what is unusual about it.

Sources

Not sure who looks after your Laravel site, or what they changed last month? Let's check its state together.

Book a Strategic Session

Website Maintenance & Support