What Do Security Updates for Your PHP Application Cover?

By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.

Profiles: GitHub · LinkedIn.

Published: · Last technical review:

In my PHP and MySQL maintenance service (from €60/month + VAT*), I include security updates, backups, and bug fixes, quoting new features separately. Before intervening in your application, I would propose agreeing in writing on which code, dependencies, and environment to review and how to verify each change.

Criteria: turn «updating» into a reviewable scope

I propose not starting with «update everything», but with a description of the application you want to maintain. What does it do? Who uses it? Which part do you need to keep without functional changes? Is there a specific modification that worries you? These questions are a preparation guide, not the result of an audit or a list of included coverage. With them, I aim for us to discuss the same subject before quoting.

My published offering mentions PHP and MySQL applications that you already have running. It includes security updates, backups, and bug fixes; new features are quoted separately. That text establishes categories of work, not a universal technical procedure. I would not use it to claim that any component of any application is covered by a monthly fee without a review of the case.

Conditions I propose describing

Application and environment
Identification of the operational PHP/MySQL application and the environments where changes are reviewed and applied.
Technical layers subject to agreement
Written demarcation between application code, external libraries or dependencies, and PHP/MySQL configuration.
Boundary against new features
Preservation of existing behaviour within maintenance; new screens, rules, or features are quoted separately.
Verification and production release
Testing critical business operations and obtaining prior authorisation before applying changes in production.

These are scope questions, not commitments already included.

I would suggest translating these conditions into recognisable examples. Instead of «review security», we could describe which screen or process concerns you and what you need to continue doing after an intervention. You do not need to diagnose the cause. It is helpful, however, for us to distinguish a symptom, a functional request, and a pending decision. I would not classify a change as small simply because its name takes few words.

My own proof: what I actually offer

On my homepage, I explain that I maintain and evolve existing PHP applications, whether I built them or they are already running in your company. Maintenance has a starting price from €60/month + VAT*. That benchmark is not a fixed quote for your application and does not allow deducing unlimited coverage. Each project is analysed and quoted in writing.

Reviewing your application requires analysing its specific situation. The retainer covers security updates, backups, and bug fixes; everything else is quoted separately. Before upgrading PHP, I review the entire codebase. I keep the published offering separate from the conditions we need to agree on for your application.

When you should NOT treat it as maintenance

If you want the application to permit an operation that was not agreed upon, I would propose assessing that need as an evolution. It may be important for your business, but I would not take it as included simply because it arises during a conversation about security. My offering explicitly distinguishes new features from maintenance. To classify your request, I would review the expected behaviour and the change you are actually requesting.

In a production PHP application, you can propose a scoped one-off intervention or ongoing monthly maintenance depending on how critical your operations are. The first alternative requires describing a concrete objective; the second demands defining what is maintained and under what conditions. I do not claim that one is always safer or that the starting price resolves that choice on its own.

Nor is it advisable to accept an absolute guarantee based on the word «updated». I do not present your application here as risk-free, nor do I take unreviewed changes as compatible. If information is missing to describe an intervention, I would prefer to keep it visible and agree on what is missing. The article guides the conversation; it does not replace the evaluation of your application or authorise operations in production.

How I would prepare the work

My process begins with a written diagnosis, followed by agreed deliverables, budget, and timeframe. For this case, I would propose attaching a description without secrets of the tool and the need you have identified. Afterwards, we would need to agree on what technical information to review and how to do it. The specific list of access credentials is not included by reading this article or submitting an initial inquiry.

Before describing an update as accepted, I would propose agreeing on what behaviour to observe in order to verify it. What tasks must continue working? What differences would be expected? Who can confirm that the outcome matches how your company uses it? These are questions to prepare a concrete verification. I do not attribute to my maintenance a protocol, frequency, or service level that we have not yet established.

Separate need from solution right from the inquiry

You can write «I am concerned about the state of my application» without choosing in advance a PHP version or a list of packages. I propose describing first what you have and what you need to maintain. If you also want a new screen or operation, include it as a separate request. That way we can discuss both without turning an addition into a tacit condition of maintenance.

Before sending me your inquiry, note down what PHP/MySQL application you have running, what tasks correspond to recurring maintenance, what new features you would like quoted separately, and what deliverables you expect to review. I would not take your answers as a security diagnosis or acceptance of a quote: they serve to prepare the need and the agreements we must later set out in writing.

A closing question before authorising

I propose reading the scope as if the person who approved it were not available to explain it. Could someone distinguish which application is included, what change is assessed, and what outcome must be reviewed? Would it be clear which new request requires a separate quote? If the answer depends on a conversation that is not reflected, I would propose clarifying it before intervening. I do not add a rigid technical procedure with this: I aim to ensure that update conditions do not rest on an implicit interpretation of «maintenance» or a promise of security that I cannot justify.

Layers I propose separating before intervening

General coverage includes security updates, backups, and bug fixes. That description does not determine which components, authorisations, or verifications correspond to a specific application. The following questions guide scope definition; they do not describe a proprietary protocol.

For each layer, what representative operations would need to be tested, in what testing environment, and with what scope? These questions do not authorise acting in production upon receiving your inquiry.

Frequently asked questions

What updates do we agree on?

In my maintenance, I include security updates, backups, and bug fixes. Which components and verifications correspond to your application is determined on a case-by-case basis.

How do I separate maintenance from evolution?

My offering separates updates, backups, and bug fixes from new features, which I quote separately. For your request, I would propose identifying what behaviour you need to preserve and what capability you want to add. That distinction must be set out in the written scope; I would not resolve it automatically based on the technology used or a brief description of the change.

PHP maintenance and evolution

PHP maintenance and evolution

Tell me about your case and I will review it in writing

Prepare your case with the checklist and self-assessment

Related articles

* Indicative starting prices, subject to conditions and change. VAT not included: charged separately at the applicable rate. The final amount is set in a written quote after reviewing your project and is binding only once accepted by both parties. Quotes are valid for 30 days. Full terms: General terms.