Maintenance and Support Agreement in Singapore: Template and Key Clauses (2026)

A maintenance and support agreement in Singapore sets out how a software or technology vendor keeps a product working after delivery: fixing defects, handling support requests and providing updates. It usually sits alongside a licence or SaaS subscription, and its commercial heart is the service level agreement (SLA). Singapore law adds a specific control on how far a supplier can limit its liability. This guide sets out the law, the key clauses and a working skeleton. It is general information, not legal advice; confirm a live deal with a Singapore lawyer. ## What law governs maintenance and support in Singapore? Singapore contract law is based on English common law. There is no special software maintenance statute, so the SLA and commercial terms do the work. One statute stands out for liability: the Unfair Contract Terms Act (Chapter 396) applies a reasonableness test to clauses that exclude or limit liability in many business contracts and makes some exclusions ineffective. Because support agreements rely heavily on liability caps and credits-as-sole-remedy clauses, this is the key Singapore-specific point, and a cap that is unreasonable may not hold. ## Service levels, uptime and service credits For hosted software the SLA is the commercial core. Define uptime precisely: the measurement window, what counts as downtime, and the exclusions (scheduled maintenance, force majeure, customer-caused outages, third-party platforms). Set a monthly availability target with service credits as the remedy if it is missed. - Service credits are a percentage of fees credited when a target is missed. State whether they are the main remedy for SLA failures, keeping the Unfair Contract Terms Act reasonableness point in mind if they are made the sole remedy.

• Response and resolution times are tied to severity levels (for example Severity 1 critical outage down to Severity 4 cosmetic), each with a target response (acknowledgement) and a target resolution or workaround time.
• Make clear which targets are firm commitments and which are reasonable-efforts targets. ## Support scope, tiers and channels Set support hours (business hours or 24x7), channels (portal, email, phone) and tiers (Level 1 triage, Level 2 technical, Level 3 engineering). Name authorised contacts who may raise tickets, the customer cooperation expected, and what is out of scope (for example custom development), which is billed separately. ## Maintenance, versioning and end-of-life Maintenance usually means error correction plus updates. Separate included updates and patches from chargeable major upgrades or new modules. Set a versioning policy (how many prior versions are supported) and an end-of-life (EOL) or end-of-support notice period after which a version is no longer maintained. A clear EOL clause prevents disputes when the vendor retires an old release. ## GST, warranties, liability and data - GST. Support and maintenance services supplied in Singapore are generally subject to GST at the prevailing standard rate of 9 percent. State whether fees are inclusive or exclusive of GST and confirm registration and invoicing.
• Warranties: a limited warranty that the software performs materially in line with its documentation.
• Liability: a cap, often linked to fees, and exclusion of indirect losses, drafted to meet the Unfair Contract Terms Act reasonableness test.
• Indemnities: usually an IP infringement indemnity from the vendor.
• Data protection: where the vendor accesses personal data, the Personal Data Protection Act 2012 (PDPA) applies, so set data-handling duties, security measures and breach handling. ## Escalation, reporting and business continuity Beyond the core SLA, set out an escalation matrix: named contacts at each tier, the time after which an unresolved ticket moves up, and management contacts for a Severity 1 outage. Agree the reporting cadence, such as monthly service reports showing uptime achieved, tickets by severity, and any credits due, plus a periodic service review. For business-critical systems, address business continuity and disaster recovery: backup frequency, recovery point and recovery time objectives, and the vendor's duties if its own infrastructure fails. Where the vendor hosts data, confirm the hosting location and any data-residency expectation, since customers in regulated sectors may require specific arrangements and the PDPA sets duties for transfers of personal data out of Singapore. ## Key clauses and a simple drafting skeleton 1. Parties, date and relationship to the licence or subscription

2. Definitions (support, maintenance, downtime, severity levels)
3. Scope of maintenance and support, and exclusions
4. Support hours, channels and tiers
5. Service levels: uptime, response and resolution times
6. Service credits and remedy status
7. Updates, upgrades and versioning
8. End-of-life and end-of-support policy
9. Fees, GST, renewal and price changes
10. Warranties
11. Limitation of liability (Unfair Contract Terms Act reasonable) and indemnities
12. Data protection (PDPA)
13. Term, termination and effect of termination
14. Governing law and dispute resolution
15. Signatures Give the most attention to the SLA definitions, service credits and the liability cap, because the Unfair Contract Terms Act will test whether the cap stands and the SLA decides what the customer actually gets. ## Keeping a portfolio of these contracts under control The hard part is rarely one agreement. It is tracking many of them at once: which service level or scope applies, when each renewal or notice period falls, which liability position you accepted, and whether a clause was quietly changed in the last draft. That work (drafting from a tuned template, flagging risky clauses per clause, tracking renewals and keeping versions straight) is what an AI contract workspace can hold in one place. Adira is built for this: one AI workspace tuned to your company and built on Claude, with per-clause risk review, plain-English clause editing and a live activity timeline. It is India-first today with other jurisdictions on its roadmap, so verify local depth before relying on it for Singapore law. More at Adira. The law above stands on its own. ## Bottom line A Singapore maintenance and support agreement runs on common law contract, with the Unfair Contract Terms Act (Chapter 396) testing liability limits, GST at 9 percent, and the PDPA covering personal data the vendor accesses. The deal turns on the SLA: precise uptime, severity-based response and resolution targets, service credits, and a clear versioning and end-of-life policy. Draft the liability cap to be reasonable and take Singapore advice before signing a real deal.