What is the difference between a software license agreement and a SaaS agreement?

A software license agreement grants the right to install and use a copy of software, typically delivered to the customer and run on their own machines or servers. A SaaS agreement gives access to software hosted by the vendor and accessed over the internet, where the customer never receives a copy of the code. Because SaaS is access rather than a transferred copy, it is governed more by service terms and uptime commitments than by traditional license-grant language.

Does a software license transfer ownership of the software?

No. A license grants permission to use the software under specific conditions, but the developer retains all ownership of the underlying code, copyrights, and intellectual property. This is the core distinction between licensing and selling: the customer buys the right to use, not the asset itself. If you actually intend to transfer ownership, you need an assignment agreement, not a license.

What is the difference between a perpetual and a subscription license?

A perpetual license lets the customer use a specific version of the software indefinitely after a one-time payment, though ongoing support and updates may require a separate maintenance fee. A subscription license grants usage rights only for the paid term, monthly or annual, and access ends when the subscription lapses. Most modern software has shifted to subscription pricing for predictable recurring revenue.

Do I need a software license agreement if my software is free?

Yes. Even free or open-source software is distributed under a license, and that license is what sets the terms of use, limits your liability, and protects your copyright. Without one, users have no clear permission to use your code and you have no protection if something goes wrong. Open-source projects rely on licenses like MIT, Apache 2.0, or GPL to define exactly what users may and may not do.

Should a software license agreement limit liability?

Almost always. Software can fail in unpredictable ways, and a limitation of liability clause caps your financial exposure, usually to the fees paid in the prior 12 months, and excludes indirect or consequential damages. Without this clause, a single defect that disrupts a customer's business could expose you to claims far larger than the license fee you collected.

Software License Agreement Template: How to Write One

Learn how to write a software license agreement, license types, grant clauses, restrictions, IP ownership, warranties, and common drafting mistakes.

A software license agreement is the contract that lets someone use your software without giving away ownership of it. It is one of the most important documents a software company signs, because it defines exactly what a customer can do with your code, what they cannot do, who owns the intellectual property, and who is liable when something breaks.

Whether you sell desktop applications, embedded firmware, on-premise enterprise software, or a downloadable tool, a well-drafted license agreement protects your revenue and your IP. This guide explains what a software license agreement is, the different types, every clause it should contain, and the mistakes that quietly expose developers to risk.

What is a software license agreement?

A software license agreement is a legally binding contract between the owner of software (the licensor) and the person or company using it (the licensee). Instead of selling the software outright, the licensor grants a limited right to use it under specific conditions.

The distinction matters. When you license software, you keep ownership of the code, the copyrights, and all underlying intellectual property. The customer only receives permission to use it within the boundaries you set. This is what lets you license the same software to thousands of customers while remaining its sole owner.

Software license agreements appear under several names (end-user license agreement or EULA, software licensing agreement, or simply "license terms"), but they all do the same job: grant usage rights while protecting the owner.

Types of software licenses

The right structure depends on how your software is delivered and how you charge for it.

Perpetual license

The customer pays once and can use that version of the software indefinitely. Updates, upgrades, and support are usually sold separately through a maintenance agreement. Common for on-premise enterprise software and traditional desktop applications.

Subscription (term) license

The customer pays on a recurring basis, monthly or annually, and usage rights end when payment stops. This is the dominant model today because it produces predictable recurring revenue and keeps customers on current versions.

Per-seat (named-user) license

Each individual user requires their own license. Best for software where usage maps cleanly to people, such as design tools or developer environments.

Concurrent-user license

A set number of users can access the software at the same time, drawn from a larger pool. Useful for tools that aren't used by everyone simultaneously.

Site or enterprise license

One license covers an entire organization, location, or unlimited users within defined boundaries. Priced as a flat fee and common for large deployments.

OEM and embedded license

The software is bundled into another company's hardware or product and redistributed to their end customers. These licenses include redistribution rights the standard agreement would otherwise prohibit.

Open-source license

Free-to-use licenses like MIT, Apache 2.0, or GPL define what users may do with the source code. They still impose obligations such as attribution, copyleft requirements, or limits on warranty claims, so even "free" software needs a license.

Key clauses in a software license agreement

1. Grant of license

This is the heart of the agreement. It states exactly what the licensee is permitted to do. A strong grant clause specifies whether the license is:

Exclusive or non-exclusive, whether you can license the same software to others
Transferable or non-transferable, whether the customer can pass it to a third party
Revocable or irrevocable, under what conditions you can terminate the rights
The permitted scope, number of users, devices, locations, or installations

Vague grant language is the single most common drafting error. "Customer may use the Software" tells you nothing about how many users, on how many machines, or for what purpose.

2. Restrictions on use

Spell out what the licensee may not do. Standard restrictions prohibit:

Reverse engineering, decompiling, or disassembling the code
Copying the software beyond what the license allows
Modifying or creating derivative works
Sublicensing, renting, leasing, or reselling
Removing copyright notices or proprietary markings
Using the software beyond the licensed user or device count

These restrictions are what stop a single license from being shared across an entire company or repackaged and resold.

3. Intellectual property ownership

State clearly that the licensor retains all ownership of the software, including the source code, copyrights, trademarks, and any improvements. The license grants usage rights only; it transfers no ownership. If your customers expect any custom work product, clarify who owns that separately. For a deeper look at how to handle ownership and licensing of IP, see our guide on assigning and licensing your intellectual property.

4. Fees and payment terms

Define the license fee, the billing schedule, what happens on non-payment, and whether fees are refundable. For subscriptions, specify renewal terms, price-increase notice periods, and auto-renewal mechanics. For perpetual licenses, separate the upfront fee from any recurring maintenance charge.

5. Support and maintenance

If you provide updates, bug fixes, or technical support, define the scope here or in a separate maintenance agreement. Specify response times, what counts as supported, and what is billed separately. Many disputes start because "support" was never defined.

6. Warranties and disclaimers

Most license agreements provide a limited warranty (for example, that the software will perform substantially as documented for a defined period) and then disclaim everything else. The disclaimer typically states the software is provided "as is" without warranties of merchantability or fitness for a particular purpose. This caps the promises you're legally on the hook for.

7. Limitation of liability

This clause caps your financial exposure if the software causes a loss. It usually limits total liability to the fees paid in a recent period (often the prior 12 months) and excludes indirect, incidental, and consequential damages. Without it, a single defect could expose you to claims that dwarf the license fee.

8. Indemnification

Indemnification clauses allocate who covers third-party claims. Typically the licensor indemnifies the licensee against claims that the software infringes someone else's IP, while the licensee indemnifies the licensor for misuse. Keep these mutual obligations balanced and tied to the limitation of liability cap.

9. Term and termination

Specify how long the license lasts, how either party can terminate, and what happens on termination, usually that the licensee must stop using and delete all copies of the software. Define which clauses survive termination, such as confidentiality and limitation of liability.

10. Confidentiality

If the agreement gives the customer access to non-public information, pricing, source code, or technical documentation, include confidentiality obligations or reference a separate non-disclosure agreement. For source-code escrow or deep technical access, an NDA is essential.

How to write a software license agreement: step-by-step

Step 1: Identify the parties. Use full legal names and entity types. State which party is the licensor (owner) and which is the licensee (user).

Step 2: Choose your license model. Decide whether you're granting a perpetual or subscription license, and whether it's per-seat, concurrent, site-wide, or enterprise. This decision drives the rest of the document.

Step 3: Write the grant clause. State precisely what the licensee may do, number of users, installations, and permitted purposes, and whether the license is exclusive, transferable, and revocable.

Step 4: List the restrictions. Cover reverse engineering, copying, sublicensing, modification, and resale. Be explicit; courts enforce what's written, not what you intended.

Step 5: Lock down IP ownership. Confirm in plain language that the licensor owns everything and the licensee receives usage rights only.

Step 6: Set fees and payment terms. Define the fee, schedule, renewal, and consequences of non-payment.

Step 7: Add warranties, liability limits, and indemnification. These three clauses control your risk. Don't skip them, even for low-priced software.

Step 8: Define term, termination, and governing law. State the duration, the exit conditions, the post-termination obligations, and which state's law applies.

Step 9: Add signature blocks. For companies, the signatory must have authority to bind the entity. Click-through acceptance works for high-volume consumer software; signed agreements are standard for enterprise deals.

Common mistakes to avoid

Confusing a license with a sale. Writing "Customer purchases the Software" instead of "Customer is granted a license to use the Software" can undermine your ownership. Use licensing language consistently.

Leaving the scope undefined. A grant clause that doesn't state user counts, device limits, or permitted uses invites disputes and license abuse. Quantify everything.

Omitting the limitation of liability. Many small developers skip this clause and expose themselves to claims far larger than the fee collected. It's the most important protection in the entire agreement.

Forgetting redistribution and OEM terms. If a customer plans to embed or resell your software, the standard grant prohibits it. Address redistribution explicitly or you'll renegotiate later.

Ignoring the SaaS distinction. If you actually deliver hosted software accessed over the internet, a traditional license grant is the wrong framework: you need service-based terms. Our SaaS licensing agreement guide covers that model in detail.

No survival clause. Confidentiality, liability limits, and indemnities should survive termination. If they don't, your protections vanish the moment the contract ends.

How license acceptance works: click-wrap, shrink-wrap, and signed agreements

A software license agreement only protects you if the licensee actually agreed to it in a way a court will recognize. How you capture that agreement depends on how the software is sold.

Signed (negotiated) agreements are the standard for enterprise and high-value deals. Both parties review and sign a single document, often after negotiating specific terms like the limitation of liability cap or support response times. This produces the strongest, clearest record of agreement, which is why it's used whenever the deal is large enough to justify the friction.

Click-wrap agreements present the terms on screen and require the user to click "I agree" before installing or using the software. Courts broadly enforce click-wrap because the user takes a clear affirmative action to accept. To hold up, the terms must be visible and the acceptance step unavoidable; burying a link at the bottom of a page is not enough.

Shrink-wrap and browse-wrap are weaker. Shrink-wrap terms (where opening the packaging signals acceptance) and browse-wrap (where merely using a site implies agreement) are harder to enforce because the user may never have seen the terms. If you rely on either, make the terms as conspicuous as possible.

For consumer and high-volume software, click-wrap is usually the right balance of enforceability and low friction. For enterprise software, a signed agreement is worth the extra step because the dollar amounts, and the risks, are higher.

When you need a software license agreement

Selling or distributing any software, desktop, mobile, embedded, or on-premise
Releasing open-source code, where the license defines permitted use and limits liability
Licensing software to enterprise customers under negotiated terms
Bundling your software into another company's product through an OEM arrangement
Offering a free tool or trial, where you still need to set usage limits and disclaim warranties

If your relationship also involves custom development work alongside the license, pair this agreement with a software development contract that covers deliverables and a master service agreement for the broader commercial relationship.

Related guides

Generate Your Software License Agreement with Contractable

Drafting a software license agreement from scratch means getting the grant, restrictions, IP ownership, and liability clauses exactly right for your delivery model. Contractable generates a customized software license agreement in seconds, perpetual or subscription, per-seat or enterprise, with the right protections built in. No lawyers or legal background required.