Every month: security and dependency updates tested on staging, monitoring, and a one-page note. Every quarter: a versions-and-patches report you can attach to an insurance form or a customer security review. Every year: the next major Laravel version, included. Apps that fell to Laravel 5 never intended to; this is how you don’t.
12-month term · 10% off annual · Invoiced in USD or GBP.
Same monthly discipline in every plan; the difference is response time, included hours and how much evidence you need to hand to reviewers.
$300/month
2 engineering hours/month · response within 2 business days
Best for: A stable internal tool that just has to stay patched.
$500/month
4 engineering hours/month · response within 1 business day
Best for: A customer-facing portal or booking system with integrations.
$800/month
8 engineering hours/month · response within Same business day
Best for: Revenue-critical apps with payments, or a compliance reviewer to satisfy.
The first months of a plan would be an upgrade anyway, so we scope that as a fixed-price project first and start the plan after cutover. Start with an Assessment.
Yes, if the app is already on a supported PHP and Laravel version. If it isn't, the first months would be spent upgrading anyway, so we scope that as a fixed-price upgrade first and start the plan after cutover.
Current PHP, Laravel, database and package versions; patches applied that quarter with dates; monitoring summary; backup restore drill result; and open recommendations. It is written to be attached to a cyber-insurance questionnaire or a customer security review.
The next major version is included in every plan. We schedule the hop within the quarter after release, once the ecosystem packages you use support it, and run it through staging like any other change.
No. Hours reset each month. Work beyond the included hours is quoted as a change order before we start.
3–5 working days. A fixed price for the upgrade, a list of what could break, and how we'll prevent it.