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

A maintenance and support agreement in Germany sets out how a supplier keeps software, hardware or equipment running: what is covered, how fast faults are acknowledged and fixed, and what the customer gets when service levels slip. German law shapes it in a specific way. The civil code (the Buergerliches Gesetzbuch, or BGB) treats the contract differently depending on whether the supplier owes an effort (a service, Dienstvertrag) or a result (a work, Werkvertrag), and German law on standard terms limits how far liability can be excluded. This guide sets out the governing law, the key clauses and a working skeleton. It is general information, not legal advice; confirm a live deal with a German lawyer. ## What law governs a maintenance and support agreement in Germany? The agreement is a private contract under the BGB, and the category matters: - Dienstvertrag (service contract, BGB sections 611 and following): the supplier owes its diligent effort, for example ongoing support availability, not a defined result.

• Werkvertrag (contract for work, BGB sections 631 and following): the supplier owes a defined result, for example fixing a specific defect, which carries acceptance and warranty rights.
• Standard terms control (BGB sections 305 and following), which polices one-sided clauses in pre-formulated contracts and limits exclusions of liability, especially for intent and gross negligence.
• GDPR (Regulation (EU) 2016/679) and the Bundesdatenschutzgesetz (BDSG) where support staff access personal data.
• Umsatzsteuergesetz (UStG), VAT (Umsatzsteuer) at the standard rate of nineteen per cent, which the pricing clause should address. ## Key clauses to get right - Covered items and scope: which systems, versions, modules or equipment are supported, and what is excluded, such as customer-caused faults or third-party products.
• Contract type: whether support is a continuing service (Dienstvertrag) or fault-fixing owed as a result (Werkvertrag), which sets warranty and acceptance.
• Support tiers: severity levels from a critical outage down to a minor issue, with a clear test for each.
• Response and resolution times: the time to acknowledge a ticket and the target to restore or fix, set per severity level and kept separate.
• Uptime or availability: the committed availability figure for hosted services, how it is measured and what is excluded.
• Service credits: the remedy for a missed target, usually a credit against fees with a stated cap, and whether credits are the sole remedy.
• Maintenance windows and updates: planned maintenance, patches, upgrades and whether new versions are included.
• Limitation of liability: a cap and exclusions drafted to respect the BGB standard-terms rules.
• End of life and end of support: notice before a product reaches end of life, and what support remains.
• Fees, VAT and review: charges, extra-charge triggers, VAT treatment and price review.
• Data protection and security: handling of personal data under the GDPR and BDSG, with a processing agreement where required. ## Germany-specific points that matter The first point is the service-versus-work distinction. Ongoing support that keeps a system available usually looks like a Dienstvertrag; a commitment to fix a specific defect can look like a Werkvertrag with acceptance and warranty. Many support contracts mix both. Label the obligations, because the category decides whether the supplier owes a result and what the customer can demand if it is not delivered. The second point is the standard-terms control. Where the agreement is a pre-formulated standard form, BGB sections 305 and following apply strict fairness controls. A supplier cannot exclude liability for intent or gross negligence, nor for injury to life, body or health, and broad blanket exclusions of all liability are often void. This is stricter than many common-law systems, so a limitation clause lifted from an English-law template can fail in Germany. Draft the cap to carve out the liabilities that cannot be excluded. The third point is data protection. Support staff frequently access systems holding personal data, so the GDPR and BDSG apply and a data processing agreement is usually needed where the supplier processes personal data on the customer's behalf. ## A simple drafting skeleton 1. Parties and date

2. Definitions and contract type (Dienst or Werk)
3. Scope of maintenance and support
4. Support tiers and severity classification
5. Response and resolution targets
6. Availability commitment and measurement
7. Service credits and remedies
8. Maintenance windows, patches and upgrades
9. Fees, VAT and price review
10. Limitation of liability (respecting BGB standard-terms rules)
11. Data protection and security (GDPR, BDSG)
12. End of life and end of support
13. Term, renewal and termination
14. Governing law (German) and jurisdiction
15. Signatures ## Common mistakes to avoid - Not stating whether support is a Dienstvertrag or a Werkvertrag, so warranty and acceptance are unclear.

• Copying a broad liability exclusion that is void under the BGB standard-terms rules.
• Merging response and resolution into one number, so neither is enforceable.
• Leaving availability undefined or without exclusions, so every outage becomes a dispute.
• Forgetting a data processing agreement where support staff access personal data. ## Keeping support contracts under control If you run maintenance and support across several suppliers or products, the hard part is not one agreement. It is tracking which uptime figure applies where, what the response and resolution targets are, which clauses survive the standard-terms rules and when each contract renews or a product hits end of life. That work, drafting from a tuned template, flagging one-sided or risky clauses, tracking renewals and keeping versions straight, is what an AI contract workspace can hold in one place. Adira is built for this, with per-clause risk review, plain-English clause editing and a live activity timeline; it is one AI workspace tuned to your company and built on Claude. It is India-first today with other jurisdictions on its roadmap, so verify local depth before relying on it for German law. More at Adira. The law above stands on its own. ## Bottom line A German maintenance and support agreement turns on the service-versus-work distinction under the BGB and on the strict standard-terms control of liability clauses. Label the obligations, draft the cap to respect the liabilities that cannot be excluded, define tiers, response and resolution times, availability and credits precisely, and get German advice before signing a real deal.