Software maintenance services that keep business systems secure and supported
Software maintenance services for the systems your business runs on: custom web applications, portals, internal tools, integrations and back ends. We keep them secure, updated and working: security patches every month, framework and runtime upgrades planned before end of support, bugs fixed, errors and backups monitored, and small changes made within a monthly allowance. Your code stays in your repository and your hosting stays in your company's name.
- No lock-in: cancel with one month's notice
- Scope agreed in writing before work starts
- Accounts and logins in your company's name
Why software that works still needs maintenance
Software does not wear out, but everything around it moves. Libraries publish security fixes, runtimes and frameworks reach end of support, browsers and operating systems change, the systems you integrate with change their interfaces, and laws add new requirements. A system nobody touches for two years is not stable; it is falling behind, and the gap becomes a large, risky upgrade project or a security incident.
Support dates make this concrete. On 12 November 2026, the PHP project lists PHP 8.2 as receiving security fixes only until 31 December 2026, and each later branch with its own end date, after which a branch receives no fixes at all. Node.js states that its long-term support releases typically receive critical bug fixes for a total of 30 months, and that production applications should only use Active LTS or Maintenance LTS releases. Every framework and database has a similar calendar. Maintenance means working to that calendar instead of being surprised by it.
What our software maintenance covers
- Security updates. Dependencies scanned for known vulnerabilities and updated every month, urgent fixes applied within days.
- Upgrades before deadlines. A register of every component with its support end date, and each upgrade planned and tested well before that date.
- Bug fixes. Faults reported by users or found in monitoring, fixed with a test so they do not return.
- Monitoring. Errors, uptime, response times, certificate and domain expiry, disk and database growth.
- Backups and restore tests. Backups checked, and a restore actually performed on a schedule, with the result recorded.
- Small changes. A monthly allowance for adjustments: a new field, a changed report, a new rule.
- Integration upkeep. When a connected system changes its interface or a certificate, the integration is updated before it breaks.
- Documentation. Architecture notes, runbooks and the component register kept current in the repository.
- A monthly report. What was done, what is coming, which deadlines are next, and how each request was handled.
The four types of software maintenance
| Type | Purpose | Example |
|---|---|---|
| Corrective | Fix faults | An invoice export that fails for one customer type |
| Adaptive | Keep up with a changing environment | A runtime upgrade, a new interface version of a payment provider, a new e-invoicing format |
| Perfective | Improve what works | A slow report made fast, a confusing screen simplified |
| Preventive | Reduce future problems | Tests added around a fragile module, duplicated code merged |
Plans that only cover corrective work turn into firefighting. We agree a balance with you, and most months the largest share goes to adaptive and preventive work, which is what keeps the corrective share small. Our technical debt guide explains why.
End-of-life software: when support stops
Many companies run a system on a framework or runtime that no longer receives security fixes, often because the original supplier is gone. We handle this as a planned project: inventory the components and their versions, add automated tests around the critical functions, then upgrade step by step, each step delivered to production. Where a component has no upgrade path, we replace that part behind a stable interface rather than rewriting the whole system. The software architecture guide shows how that works.
Legal duties that maintenance fulfils
Under the GDPR, Article 32 requires security appropriate to the risk, including the ability to restore availability and access to personal data in a timely manner, and a process for regularly testing the effectiveness of security measures. NIS2 requires essential and important entities to take measures that include security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure (Directive (EU) 2022/2555, Article 21(2)(e)).
For software sold as a product, the Cyber Resilience Act goes further. It applies from 11 December 2027, with reporting obligations from 11 September 2026. Under Article 13(8), manufacturers must handle vulnerabilities effectively for the support period, which shall be at least five years, or the expected use time if the product is expected to be in use for less than five years (Regulation (EU) 2024/2847; all legal texts read on 12 November 2026). A maintenance plan with a component register and tested updates is how that obligation is met in practice. See our Cyber Resilience Act guide.
What we watch every month
The monthly report is short and the same shape every month, so trends are visible. It lists the security updates applied and any open vulnerabilities with their planned fix date; the next three support deadlines in the component register; errors in production and whether they are rising or falling; uptime and the slowest pages or endpoints; backup status and the date of the last successful restore test; small changes delivered against the allowance; and any risk we see coming, such as an interface version of a connected system being retired. Management can read it in five minutes and see whether the system is getting healthier or not.
Severity levels and the maintenance agreement
The agreement sets out, in writing, what is included each month, the severity levels and how each is handled and escalated, how small changes are requested and approved, and how anything outside the plan is quoted. Every request and its resolution are recorded and reported every month. Severity levels follow the effect on your business, not on the code: a stopped order flow is critical even if the fix is one line, and a cosmetic fault on a rarely used page is minor even if it looks bad. Our guide to software maintenance cost explains how to set a yearly budget.
Maintenance plus development
Maintenance and new features work best with the same team, because the people who keep the system healthy know where changes are safe. New features are scoped and quoted as separate work, so the maintenance budget stays predictable. For mobile apps, store rules add their own calendar; see mobile app maintenance. For WordPress sites, see WordPress maintenance. For the servers, devices and accounts around the software, see managed IT services.
How maintenance starts
- Handover review. We get the code building from your repository, check access to hosting, domains and third-party accounts, and list every component with its version and support date.
- Findings and plan. A short report: what is out of date, what is at risk, what is missing, and a dated plan for the first months.
- Baseline. Monitoring, backups with a first restore test, and dependency scanning set up.
- Monthly rhythm. Updates, fixes, small changes and the report, every month.
We take over systems built by other suppliers as well as our own, in any common stack, including Python, Node.js, PHP and .NET.
You own it
As a standard term, the code is in a repository in your company's account, the hosting and domains are in your company's name in EU regions, and every change we make is recorded there with its reason. If you end the agreement, the documentation and component register go with the system, so another team can continue the next day. See prices.
Questions we get
What is included in software maintenance?
Security updates of libraries and the runtime, framework upgrades planned before end of support, bug fixes, monitoring of errors, uptime and backups, restore tests, small changes within an agreed monthly allowance, and a short monthly report. New features are planned and quoted separately, so maintenance stays predictable.
What are the types of software maintenance?
Four are usually named: corrective maintenance fixes faults, adaptive maintenance keeps the software working as its environment changes (operating systems, browsers, interfaces, laws), perfective maintenance improves performance and usability, and preventive maintenance reduces future problems, for example by paying down technical debt. A good maintenance plan covers all four in proportion.
Can you maintain software another company built?
Yes, that is a common starting point. We begin with a handover review: get the code building from the repository, check access to hosting, domains and accounts, list components and their support dates, and document what is missing. If something essential is missing, such as source code or admin access, we say so before any monthly agreement starts.
How are faults prioritised?
By severity level, agreed in writing: a production outage, a serious fault with a workaround, and a minor issue. Requests are handled on working days, the most severe first, with a named escalation path, and the monthly report shows how each one was handled.
Is software maintenance required by law?
Not as such, but laws require what maintenance delivers. The GDPR requires appropriate security for personal data, NIS2 requires covered entities to handle vulnerabilities, and the Cyber Resilience Act requires manufacturers of products with digital elements to handle vulnerabilities for a support period of normally at least five years.
Who owns the code and the accounts?
Your company. The code is in your repository, the hosting and domains are in your company's name, and every change we make is recorded there. You can end the agreement and hand the system to another team with the documentation we kept up to date.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.