Laravel support and maintenance · monthly retainer
Laravel support and maintenance with an engineer who knows your app, a response time in writing, and a report every month.
Once the application is current, a care plan keeps it there: patches inside the SLA, monitoring, small changes from your backlog, and one named engineer who stays. From $500/month.
Not on a supported version yet? Start with the free audit.
The SLA table
Hours, response times and price for each plan. Each tier replaces the one below it rather than stacking.
| Plan | Hours / month | Response | Critical | Price |
|---|---|---|---|---|
Essentials Patched, monitored and never more than one minor version behind. | 6 | Next business day | Same day for security incidents | $500 per month £380 · €460 |
Standard Most chosen Current, and moving: small changes land every month. | 12 | Same business day | 4 hours for security incidents and outages | $900 per month £680 · €830 |
Partner A senior engineer on your team three days a month. | 24 | 4 hours | 4 hours, including weekends for outages | $1,500 per month £1,150 · €1,400 |
Essentials
- 6 engineering hours a month
- Security patches and dependency updates within the SLA
- Uptime, error and queue monitoring
- Monthly health report: versions, vulnerabilities, what changed
- A named engineer who knows the codebase
three-month minimum, then month to month
Start with EssentialsStandard
Everything in Essentials, plus:
- 12 engineering hours a month
- Small features and bug fixes from your backlog
- Performance and database review each quarter
- Staging environment kept in step with production
- Priority queue: same-day response
three-month minimum, then month to month
Start with StandardPartner
Everything in Standard, plus:
- 24 engineering hours a month
- Monthly planning call and a written roadmap
- Architecture and security reviews before big changes
- Direct line to the engineer during UK/EU hours
- Pre-agreed day rate for anything beyond the plan
three-month minimum, then month to month
Start with PartnerThe Mobile module
For the Flutter app that talks to the application under care. An add-on to any plan, never a fourth tier: the same promise, keep it current, extended to the app in the store.
| Added to | Extra hours / month | Covers | Module price |
|---|---|---|---|
Essentials One Flutter app pair kept shippable. | 3 |
| +$300 per month +£230 · +€275 |
Standard Current, and moving: monthly releases from your backlog. | 6 |
| +$450 per month +£340 · +€415 |
Partner Release pipeline owned, a second app covered. | 8 |
| +$600 per month +£455 · +€555 |
Precondition. The app must be current — it has passed a Store-Compliance Sprint or Catch-up Upgrade — and its backend must be a Laravel application under care or maintained by your own team. Not current yet? Start with the review.
How we work inside your store accounts
Store work carries liability a Laravel plan never had, so these ten clauses sit alongside the plan terms.
What every plan includes
Patched within the SLA
Security releases for Laravel, PHP and every package are applied inside the response time your plan states, not when someone remembers.
Monitored
Uptime, error rates and queue depth watched continuously. You hear from us before your customers hear from you.
One named engineer
The same person each month, who knows your codebase and your deployment. No ticket roulette.
A monthly health report
Versions, vulnerabilities, what changed and what is coming up — in plain language, for whoever signs the invoice.
Why a plan rather than a reminder
Three things outside your roadmap decide when a version becomes a problem. A care plan keeps you ahead of all three. The PHP 8.2 end-of-life guide explains the three triggers in full.
Cyber Essentials v3.2 (April 2025)
“All software on in-scope devices must: be licensed and supported; removed from devices when it becomes unsupported or removed from scope by using a defined sub-set that prevents all traffic to / from the internet; have automatic updates enabled where possible; be updated, including vulnerability fixes, within 14 days of release, where the update fixes vulnerabilities described by the vendor as 'critical' or 'high' risk”
SourceCyber insurance renewal
“Use of any outdated or unsupported software or systems”
SourceYour host retires the PHP version
“If your project uses a retired version, you must update to a supported version.”
Source
The hand-over checklist
The first two weeks of any plan. Nothing is "looked after" until every line is ticked.
- 1Repository access confirmed, with branch protection and review rules agreed
- 2Production, staging and local environments documented, with every credential in your vault, not ours
- 3Deployment procedure and rollback written down and rehearsed once
- 4Monitoring, alerting and log access connected and tested with a deliberate failure
- 5A baseline health report: current versions, open vulnerabilities, abandoned packages, test coverage
- 6A backlog of the small fixes we found on the way in, each sized and prioritised
What the monthly report contains
One page, in plain language, on the first working day of the month.
- Laravel, PHP and package versions against their support dates
- Vulnerabilities found, patched or deferred — and why
- Everything deployed this month, linked to the commit
- Uptime, error and queue figures against last month
- Hours used against the plan
- What we recommend for next month, with sizes
A care plan or a hire?
Most Laravel applications a business runs on need between six and twenty-four engineering hours a month to stay patched, monitored and moving. That is not a job. A full-time hire spends most of their week looking for work to do, and the recruitment, onboarding and notice period arrive before a single patch does.
A freelancer solves the cost problem and creates a continuity one: no SLA, no cover when they are busy or gone, and the knowledge of your codebase leaves with them.
A care plan is the middle: a fixed block of hours, a named engineer who stays, a response time in writing, and the ability to scale into a sprint when a bigger piece of work appears. When the application genuinely needs a full-time engineer, we will say so — it is cheaper for you and we would rather keep the smaller account than lose it.
Care plan, in-house hire or freelancer
What each option actually commits to
| What you get | Care plan | In-house hire | Freelancer |
|---|---|---|---|
| Written response-time SLA | Depends on the person | Rarely | |
| Named engineer who knows the codebase | Until they move on | ||
| Monthly health report (versions, vulnerabilities, changes) | If you ask for one | ||
| Cover during holidays and sickness | |||
| Recruitment, onboarding and notice periods | None | Months | Weeks |
| Commitment | Three months, then monthly | Permanent contract | Per task |
| Scales up to a sprint when needed | Limited by one person | ||
| You own every line of code | Check the contract |
The longer version, with the arithmetic: A care plan or a hire?
Care plan questions
Is a care plan the same as a Laravel retainer?
Yes, with the terms written down. A care plan is a monthly Laravel retainer: a fixed number of engineer-hours (6, 12 or 24), a response time for each kind of issue, one named engineer and a monthly report on what the hours were spent on. Unlike an open-ended retainer, you can check every month what you got for it.
Does the engineer actually stay the same?
Yes. A named engineer owns the account and does the work. If they are away, a second engineer who has already been introduced to your codebase covers the SLA, and you are told in advance.
What counts as a critical incident?
A production outage, a data-integrity problem, or a security vulnerability being actively exploited or publicly disclosed in something you run. Each plan states its own critical response time.
Can I pause or cancel?
After the three-month minimum, plans run month to month and you can stop with a month of notice. Everything is in your repository, so there is nothing to export.
Can I move between tiers?
Up at any time, down at the next renewal. Unused hours do not roll over, so if you regularly leave hours on the table we will suggest the smaller plan ourselves.
Can the plan cover our mobile app as well?
Yes, through the Mobile module, if the app is Flutter and talks to the Laravel application under care. It adds hours to the plan and takes on both annual store deadlines, the quarterly Flutter bump and the store metadata. The app has to be current first; an app that has fallen behind goes through a Store-Compliance Sprint or Catch-up Upgrade before the module starts.
Terms
- Half of the fixed price up front, half on hand-over. No surprises in between.
- Fixed means fixed: if we underestimated, that is our cost, not yours.
- You own every line. Code lives in your repository from day one.
- Care plans run month to month after a three-month minimum.
- Working hours overlap the UK and EU day in full; the US East Coast morning in part.
What you are actually buying
The answer to "why an agency in India?", in writing.
Who you contract with
Jigomit LLP, Ahmedabad, India. The company name on the contract and on every invoice.
UK/EU working hours
Working hours overlap the UK and EU day in full; the US East Coast morning in part.
NDA before requirements
We sign your NDA, or send ours, before you share a repository or a brief.
You own every line
You own every line. Code lives in your repository from day one. All IP in the work transfers to you on payment.
Named engineer
The same engineer stays on your account. No junior substitution.
Fixed means fixed
Fixed means fixed: if we underestimated, that is our cost, not yours.
Data-processing terms published
UK GDPR Article 28 processing terms are published and signed as a schedule to the engagement letter. Read the data-processing terms
Written SLAs
Response times in the contract, not on a slide.
Tell us about the app
Which Laravel version, how it is hosted, and what has gone wrong lately. We will say which plan fits, or whether an upgrade has to come first.