Software License Agreement in Germany: Template, Key Clauses and Local Law (2026)

What a software license agreement in Germany is A software license agreement in Germany is a contract under which the owner of software grants another party the right to use it on agreed terms. The licensor keeps the copyright; the licensee receives defined rights of use (Nutzungsrechte), not ownership of the software itself. The agreement sets who may use the software, on how many devices or users, in what territory, for how long, and the limits on copying, modifying or passing it on. Software in Germany is protected by copyright law. The Copyright Act (Urheberrechtsgesetz, UrhG) contains special rules for computer programs in Sections 69a to 69g, which implement the EU Software Directive. The licence works on top of that copyright: without the granted rights of use, the licensee's copying or running of the software would infringe. The contract itself is governed by the Civil Code (BGB), and how a licence is classified (sale-like for a perpetual licence against a one-off fee, or lease-like for a time-limited licence) affects warranty. This article is general guidance, not legal advice. Have a German-qualified lawyer review a software license before you rely on it. ## What German law requires in 2026 - Copyright in software (UrhG Sections 69a to 69g). Computer programs are protected as literary works. Copying, adapting and distributing need the rightholder's permission, which the licence provides. Some acts cannot be excluded by contract, for example the lawful user's right to make a back-up copy and, within limits, to decompile for interoperability (Sections 69d and 69e UrhG).

• Exhaustion and resale of used licences. Following the Court of Justice UsedSoft ruling (C-128/11) and later German case law, the distribution right in a copy of a program can be exhausted on first sale within the EU, even where the copy was downloaded, so a perpetual licence sold for a one-off fee can in principle be resold, and a blanket contractual ban on resale may not hold. This generally applies to sold copies, not to time-limited SaaS access.
• Classification and warranty (BGB). A perpetual licence for a single fee is treated like a sale, bringing sales warranty rules; a time-limited licence against recurring fees is treated more like a lease. The classification affects the licensee's warranty rights.
• AGB rules on standard terms (Sections 305 to 310 BGB). Standard business terms are controlled strictly, even B2B. A broad as-is disclaimer or one-sided liability cap in standard terms may be void. Liability for intent can never be excluded, and limits on liability for injury to life, body or health are not allowed.
• Open-source components. Open-source licence terms carry through and should be disclosed, since some impose copyleft or attribution duties.
• VAT. German VAT applies; state whether licence fees are net or gross. ## Key clauses in a German software license | Clause | Why it matters in Germany | | --- | --- | | Grant of rights of use | Scope of Nutzungsrechte: users, devices, territory, term, exclusive or not. | | Licence type | Perpetual (sale-like) or time-limited (lease-like), which sets the warranty regime. | | Permitted and prohibited use | Limits on copying and modifying, subject to the mandatory UrhG user rights. | | Resale and transfer | Must account for exhaustion of perpetual licences under UsedSoft. | | Ownership and IP | Licensor keeps copyright; licensee gets rights of use only. | | Warranty | Reflects sale-like or lease-like classification. | | Liability and AGB | Caps drafted to survive the AGB rules; intent never excluded. | | Support and maintenance | Whether updates and support are included, and on what terms. | | IP indemnity | Protects the licensee against third-party infringement claims. | | Open-source disclosure | Identifies components and flow-through terms. | | Fees and VAT | Licence or subscription fees and net or gross VAT. | | Term and termination | Duration, renewal, and the effect on rights of use. | | Governing law and disputes | German law and courts or arbitration. | ## A simple software license structure you can adapt 1. Parties and definitions.

2. Grant of rights of use: scope, users, territory and term.
3. Licence type (perpetual or time-limited) and warranty regime.
4. Permitted and prohibited uses, respecting mandatory UrhG rights.
5. Resale and transfer, accounting for exhaustion.
6. Ownership and intellectual property.
7. Support, maintenance and updates.
8. Warranty and liability, drafted to meet the AGB rules.
9. IP indemnity.
10. Open-source components and disclosure.
11. Fees, payment and VAT.
12. Term and termination and the effect on rights of use.
13. Governing law (Germany) and dispute resolution. ## Red flags to avoid - No clear grant of rights of use (Nutzungsrechte), leaving scope and limits open to dispute.

• A broad as-is disclaimer or one-sided liability cap in standard terms that the AGB rules can void.
• Trying to exclude liability for intent or for injury to life, body or health, which is never allowed.
• A blanket ban on resale of a perpetual licence, which exhaustion under UsedSoft may override.
• Trying to remove the mandatory user rights under the UrhG, such as a lawful back-up copy.
• No open-source disclosure, so copyleft or attribution terms surprise the licensee.
• Silence on whether the licence is perpetual or time-limited, which the warranty regime depends on. ## Where a contract workspace helps A template gives you a solid German software license. The ongoing work starts after signing: confirming the licence type and warranty regime match the deal, that the liability cap is drafted to survive the AGB rules, that resale and open-source terms are handled correctly, and that renewal, support and notice dates across many licences do not slip. Drafting the licence, reviewing each counterparty's version for scope, liability and IP gaps, and tracking key dates can sit in one AI workspace tuned to how your company contracts. Adira is built around that shape: it drafts from your template, models the agreement as linked clauses so it can flag a disclaimer the AGB rules would strike or a missing IP indemnity, lets you edit clauses in plain language, and keeps renewal and notice dates on one timeline. Adira is India-first today, and deeper Germany-specific coverage is on its roadmap rather than a settled claim, so use it for drafting and review and keep a German adviser for the local-law call. The template above is enough to put a fair agreement in place on its own. Last verified October 2026.