The Key Clauses in a Software License Agreement, Explained

What are the key clauses in a software license agreement? A software license agreement sets the terms on which one party (the licensor) lets another party (the licensee) use its software. It is built from a predictable set of clauses, and a few of them carry almost all the money and risk. The grant of licence decides what you may do, the ownership clause confirms you are not buying the software, and the liability and indemnity clauses decide who pays when something breaks or someone sues. Understand these and you can read any licence, from a short SaaS order form to a heavy enterprise deal. This is general information, not legal advice. For a high-value licence or a cross-border deal, ask a qualified lawyer in your jurisdiction. ## Grant of licence and scope This is the core clause. It says what you are allowed to do with the software. Read it for four things: the rights granted (use, install, copy, modify), whether the licence is exclusive or non-exclusive, whether it is worldwide or limited to a territory, and whether it can be transferred or sublicensed. Most commercial licences are non-exclusive, non-transferable, and limited to your own internal business use. Anything broader, such as the right to modify or redistribute, is unusual and should be spelled out. ## Licence type: perpetual or subscription A perpetual licence lets you keep using the version you bought, usually for a one-time fee, even after support ends. A subscription or term licence lets you use the software only while you keep paying, and access stops when the term ends. SaaS is almost always a subscription. The practical difference is what you own on the last day of the contract: with a subscription, nothing. ## Permitted users, seats, and metrics Licences are usually limited by a metric: named users, concurrent users, devices, CPU cores, or usage volume. Check the metric carefully, because overuse is the most common cause of a surprise bill or an audit claim. Make sure the definition of a user matches how your team actually works. ## Restrictions This clause lists what you must not do. Typical limits are no reverse engineering, no decompiling, no renting or reselling, no removing copyright notices, and no using the software to build a competing product. Most of these are standard. Watch for restrictions that would block normal use, such as a ban on using the software for your clients when that is exactly your business. ## Ownership and intellectual property A licence is permission to use, not a sale. This clause confirms the licensor keeps all intellectual property in the software and that you receive only the rights expressly granted. If you are paying for custom development or configuration, say clearly who owns that work product, because the default is usually the licensor. ## Fees, payment, and price increases This clause sets the fee, the billing cycle, taxes, and late payment terms. For subscriptions, look for how renewal pricing works and whether there is a cap on increases. An uncapped right to raise the price at renewal is a common and avoidable trap. ## Maintenance, support, and updates Support is often a separate clause or a separate document. It should say what response times you can expect, what counts as an update or upgrade, and whether updates are included or cost extra. For business-critical software, this clause matters as much as the licence grant. ## Warranties and disclaimers The licensor usually warrants that the software will perform substantially as described for a limited period, and then disclaims everything else, selling the software "as is" beyond that. That pattern is normal. What you want is a meaningful warranty period and a clear remedy if the software does not work, such as repair, replacement, or a refund. ## Limitation of liability This clause caps how much the licensor must pay if things go wrong, often at the fees you paid in the prior 12 months, and excludes indirect or consequential loss. A cap is normal, but check the carve-outs. Confidentiality breaches and intellectual property indemnities are often excluded from the cap, and they should be. ## IP infringement indemnity A good licence promises that if a third party sues you claiming the software infringes their intellectual property, the licensor will defend you and cover the cost, usually with options to fix, replace, or refund. The absence of this indemnity is a real risk, because you did not build the software and cannot judge whether it infringes. ## Confidentiality and data If the software touches your data, check how the licensor may use it and whether a separate data processing agreement applies. Confidential information shared during the deal should be protected both ways. ## Audit rights Enterprise licences often let the licensor audit your usage. A fair audit clause gives reasonable notice, limits frequency, and runs during business hours. Make sure an audit cannot be used to disrupt your operations. ## Term, termination, and what happens after This clause says how long the licence runs, how either side can end it, and what happens on termination: you stop using the software, delete copies, and in a SaaS deal you should be able to export your data within a stated window. For perpetual licences, check that termination of support does not also terminate your right to use the version you bought. ## Source code escrow and export control For critical on-premise software, an escrow clause can release the source code to you if the licensor goes out of business. Export control and sanctions clauses require you not to use the software in breach of trade law. These matter more in cross-border deals, and the rules vary by jurisdiction. ## A quick map of risk | Clause | Risk level | Why |

|--------|-----------|-----| | Grant of licence and scope | High | Defines what you may legally do | | Limitation of liability | High | Caps what you can recover | | IP infringement indemnity | High | Protects you from third-party claims | | Fees and renewal pricing | Medium | Uncapped increases add up | | User and usage metrics | Medium | Overuse triggers audit bills | | Maintenance and support | Medium | Decides uptime in practice | | Audit rights | Low to medium | Should be reasonable and limited | | Restrictions, ownership | Low | Standard, but read for odd limits | ## Where a contract workspace helps Reading one licence is manageable; tracking dozens of them, each with a different renewal date, price-increase cap, user metric, and liability carve-out, is the real work, and it is exactly what an AI contract workspace can carry. Instead of re-reading every agreement to find the auto-renewal or the usage cap, you see each clause modelled in a structured clause tree, with its position marked favourable, neutral, or unfavourable to your company, and the key dates tracked automatically. Adira is one workspace built around that idea, keeping drafting, per-clause risk, version history, and renewal tracking together and tuned to how your company contracts. The clauses above stay the same; a workspace just makes reading and remembering them far less manual. Keep this explainer next to the next licence you sign, and it will read like a short list of decisions rather than dense legal text.