Software maintenance contract: support, SLA and responsibilities
Published on 2026-11-14 by frfrand
What to define in scope, availability, response times, backups, security, costs, and provider exit.
# Software maintenance contract: support, SLA and responsibilities
Without a precise agreement, “includes maintenance” can mean anything from bug fixing to unlimited development. The purpose of a contract is for client and provider to know what is covered, how the service is measured, and who decides in an emergency.
1. Inventory and service scope
Identify application, domains, environments, repositories, infrastructure, version, and external dependencies. Separate corrective maintenance (fixing failures), preventive maintenance (updates and monitoring), adaptive maintenance (compatibility with external changes), and evolutionary maintenance (new features). Specify whether scope changes are budgeted separately and what update windows are allowed.
2. SLA: availability and response times
Do not confuse first response with resolution. A well-drafted SLA defines service hours, official channel, severity levels, calculation rules, exclusions, and remedies if the contracted service is not met. For example, an incident blocking all payments may have higher priority than a visual issue. Do not promise 24/7 availability if there is no staff and operations coverage to fulfill it.
3. Responsibility matrix
| Area | Contractual question | | --- | --- | | Hosting | Who pays for and manages VPS, domains, and DNS? | | Code | Who reviews, approves, and deploys? | | Security | Who applies patches and manages access? | | Backups | Who performs, retains, and tests restorations? | | Third parties | Who manages APIs, email, payment gateways, and their incidents? | | Data | Who authorizes export, deletion, and recovery? |
Attach a list of accesses and a procedure to revoke them when the relationship ends.
4. Copies, security, and personal data
Define backup frequency and retention, location, encryption, RPO/RTO objectives, and test frequency. If personal data is processed, agree on roles, privacy obligations, and, where applicable, a data processing agreement with local legal advice. The maintenance provider must not assume they can download entire databases to a personal laptop.
5. Changes, costs, and communication
Establish how to request tasks, accept quotes, approve deployments, and prioritize incidents. Document rates or fixed amounts, invoicing, third-party services, and consequences of non-payment according to applicable law. A change log with tickets avoids disputes over what was done.
6. Intellectual property and output
Determines code ownership, dependency licenses, repository access, documentation availability, and cooperation obligation in a transition to another provider. Avoid lock-ins through personal accounts. Define deadlines and format for delivering backups and credentials upon closure.
7. Review checklist before signing
Check written scope, severities, exclusions, maintenance windows, backup tests, liability limits, confidentiality, and termination mechanism. This article is an operational guide, not legal advice; the final document requires legal review for the chosen jurisdiction.
For a technical scope basis, consult CI/CD and deployments and shared hosting, VPS or dedicated.
Frequently asked questions
Does maintenance include new features? Only if agreed upon. Does SLA equal zero-downtime warranty? No. Who owns the repository? It must be defined by the agreement and the licenses.