Free tool
Free SaaS Licensing Agreement Template
The template
Replace everything in [BRACKETS], delete the options that don't apply, and have a lawyer review the result before anyone signs. This is general information, not legal advice.
SAAS LICENSING AGREEMENT
1. Parties and purpose
- 1.1This SaaS Licensing Agreement (the "Agreement") is made on [EFFECTIVE DATE] between [LICENSOR NAME], [LICENSOR ADDRESS] (the "Licensor"), and [LICENSEE NAME], [LICENSEE ADDRESS] (the "Licensee").
- 1.2The Licensor owns and operates [PRODUCT NAME] (the "Software"). The Licensee wishes to [use / resell / offer under its own brand] the Software on the terms below.
2. Definitions
- 2.1"Customer" means a business or person to whom the Licensee provides the Software under this Agreement.
- 2.2"Licensee Brand" means the Licensee's names, logos and domains.
- 2.3"Customer Data" means data that Customers or the Licensee put into the Software.
- 2.4"Documentation" means the Licensor's user and technical guides for the Software.
3. Licence grant
- 3.1The Licensor grants the Licensee a [non-exclusive / exclusive], non-transferable licence during the Term to [choose one or more: (a) use the Software for its own internal business purposes; (b) resell access to the Software to Customers; (c) offer the Software to Customers under the Licensee Brand] in [TERRITORY].
- 3.2The Licensee may not sublicense the Software, except to Customers as permitted above.
- 3.3All rights not expressly granted in this Agreement are reserved by the Licensor.
4. Restrictions
- 4.1The Licensee will not copy, modify, reverse engineer or create derivative works of the Software, except to the extent the law allows this despite this restriction.
- 4.2The Licensee will not use the Software to build a competing product, or give access to anyone other than its own staff and its Customers.
5. Branding (white-label deals)
- 5.1The Licensor will allow the Licensee to apply the Licensee Brand to [the interface, login page, emails and a custom domain] and will [remove / keep] "powered by" references to the Licensor.
- 5.2The Licensee is responsible for its own brand, its marketing and any claims it makes about the Software.
6. Fees and payment
- 6.1The Licensee will pay [choose: a fixed fee of [FEE] per [month / year]; [FEE] per Customer per month; [REVENUE SHARE %] of the revenue it receives from Customers for the Software].
- 6.2Invoices are due within [PAYMENT DAYS] days of the invoice date. Fees exclude taxes, which the Licensee pays, except taxes on the Licensor's income.
- 6.3The Licensor may change the fees no more than once every [12] months, with [NOTICE DAYS] days' written notice.
7. Reporting and audit (revenue share and per-customer fees)
- 7.1Within [10] days after the end of each month, the Licensee will report the number of active Customers and the revenue it received for the Software in that month.
- 7.2Once a year, on [30] days' notice, the Licensor may audit the Licensee's relevant records. If the audit shows an underpayment of more than [5]%, the Licensee will pay the shortfall and the reasonable cost of the audit.
8. Support and service levels
- 8.1[Choose: The Licensee provides first-line support to its Customers and the Licensor provides second-line support to the Licensee / The Licensor supports Customers directly] by [email / ticket] during [SUPPORT HOURS].
- 8.2The Licensor will aim to make the Software available [UPTIME %] of each month, excluding scheduled maintenance announced at least [48] hours in advance. If it falls short, the Licensee may claim a service credit of [CREDIT %] of that month's fees as its sole remedy for the shortfall.
9. Updates
- 9.1The Licensor may update the Software. It will give at least [30] days' notice of any change that removes a feature the Licensee or its Customers rely on.
10. Intellectual property
- 10.1The Licensor keeps all rights in the Software, the Documentation and any improvements to them, including improvements based on the Licensee's feedback.
- 10.2The Licensee keeps all rights in the Licensee Brand and in Customer Data.
11. Customer data and privacy
- 11.1The Licensor will process Customer Data only to provide the Software and on the Licensee's documented instructions, under the data processing addendum attached as [Schedule 1].
- 11.2The Licensor will keep Customer Data secure using appropriate technical and organisational measures, and will notify the Licensee without undue delay after becoming aware of a breach affecting it.
12. Confidentiality
- 12.1Each party will keep the other's confidential information secret, use it only for this Agreement and protect it at least as well as its own, during the Term and for [3] years after it ends.
13. Warranties
- 13.1Each party confirms it has the right to enter into this Agreement.
- 13.2The Licensor warrants that the Software will perform materially as described in the Documentation. Otherwise, and to the extent the law allows, the Software is provided "as is".
14. Indemnities
- 14.1The Licensor will defend the Licensee against third-party claims that the Software infringes their intellectual property rights, and pay the resulting damages and costs, provided the Licensee notifies it promptly and lets it control the defence.
- 14.2The Licensee will defend the Licensor against claims arising from the Licensee's marketing, its contracts with Customers or its breach of this Agreement.
15. Limitation of liability
- 15.1Neither party is liable for indirect or consequential loss, or for loss of profit, revenue or data.
- 15.2Each party's total liability under this Agreement is limited to the fees paid or payable in the [12] months before the claim, except for breach of confidentiality, the indemnities above and any liability that cannot be limited by law.
16. Term and termination
- 16.1This Agreement starts on the Effective Date, lasts for [INITIAL TERM] and then renews for further periods of [RENEWAL TERM] unless either party gives [NOTICE DAYS] days' written notice before the renewal date.
- 16.2Either party may end this Agreement immediately by written notice if the other materially breaches it and does not remedy the breach within [30] days of being asked to, or becomes insolvent.
17. When the Agreement ends
- 17.1The Licensee will stop offering the Software to new Customers. Existing Customers may keep using it for a transition period of [90] days while the Licensee moves them.
- 17.2The Licensor will make Customer Data available for export in [a standard format such as CSV or JSON] for [30] days after the transition period, and then delete it.
18. Exclusivity (optional)
- 18.1If the licence is exclusive, the Licensor will not license the Software to anyone else in [TERRITORY / INDUSTRY]. Exclusivity ends if the Licensee has not reached [MINIMUM FEES OR CUSTOMERS] by [DATE].
19. General
- 19.1This Agreement is governed by the laws of [GOVERNING LAW], and the courts of [JURISDICTION] have exclusive jurisdiction.
- 19.2Neither party may assign this Agreement without the other's written consent, except to a successor of its whole business.
- 19.3This Agreement is the entire agreement between the parties on its subject and may be changed only in writing signed by both parties.
Signed for the Licensor: [NAME], [TITLE], [DATE]
Signed for the Licensee: [NAME], [TITLE], [DATE]
How to use this template
Start with section 3, the licence grant. It decides the type of deal: internal use only, resale of the original product, or a white-label deal where the licensee sells it under its own brand. Delete the options you don't need there and in the sections that depend on them, such as branding, reporting and audit.
Then choose one fee model in section 6: a fixed fee, a fee per customer or a revenue share. With per-customer fees or a revenue share, keep section 7 so the licensor can see the numbers its income depends on.
Fill in every [BRACKET], read the agreement through as each party, and have a lawyer in your jurisdiction review it. A short template cannot cover every law, industry or risk.
Clauses that cause the most disputes
Support: say who answers end customers, how fast the licensor responds to escalations, and what counts as an urgent issue.
Customer data: say where it is stored, who may access it, and how the licensee gets it out if the agreement ends.
Ending the deal: a transition period protects the licensee's customers, and a clear export format avoids arguments when it matters most.
Exclusivity: tie it to minimum fees or customers, or the licensor can lose a market to a partner that never sells.
Which agreement does your deal need?
SaaS licensing agreement: one business gets the right to use, resell, rebrand or embed your software. This template covers it, with options for each kind of deal.
Reseller or distributor agreement: the partner sells your product under your brand. A reseller sells to end customers; a distributor usually supplies a network of resellers in a territory. Keep the resale option in the licence grant and drop the white-label branding clauses.
White-label agreement: the partner sells your product under its own brand. Keep the white-label option, the branding clause and the transition clause.
OEM agreement: the partner builds your software into its own product and sells the combined product. Add terms on how your software may be embedded, how updates reach the partner's customers and who supports which part.
End user licence agreement (EULA) or SaaS terms of service: the terms between whoever sells the product and each end customer. They sit underneath the agreements above, and a white-label partner usually issues its own.
Before you sign
Check that the licence grant matches what the licensee will actually do, that the fee model matches how the licensee charges its own customers, that the service levels are realistic for the licensor, and that both sides can meet the data protection terms. If a clause is unclear to either side, rewrite it now rather than argue about it later.
Common questions
What should a SaaS licensing agreement include?
At minimum: the parties, the licence grant (who may use or resell the software, where and for what), fees and payment, support and service levels, intellectual property, customer data and privacy, confidentiality, limits on liability, term and termination, and what happens to customers and data when the agreement ends.
What is the difference between a SaaS agreement and a SaaS licensing agreement?
A SaaS agreement usually covers a customer using a hosted service. A SaaS licensing agreement covers one business giving another the right to use, resell, rebrand or embed the software, so it adds clauses on resale rights, branding, revenue share, reporting and moving customers when the deal ends.
Is a SaaS licensing agreement template legally binding?
A completed agreement becomes binding once both parties sign it, but a general template may not fit your deal or your local law. Use it as a starting point and have a lawyer in your jurisdiction review the final version.
Who supports customers in a white-label deal?
Usually the licensee handles first-line support for its own customers, and the licensor supports the licensee. Write this split, the response times and the escalation steps into the agreement.
Can I use this template for free?
Yes. You can copy, download and adapt it for your own deals. It is general information, not legal advice.
What is a SaaS OEM agreement?
An OEM agreement lets a partner build your software into its own product and sell the combined product to its customers, usually under the partner's brand. It covers how the software may be embedded, per-unit or revenue-based fees, updates, support for each part and what happens to existing customers if the agreement ends.
What is the difference between a SaaS reseller agreement and a distributor agreement?
A reseller sells the software directly to end customers. A distributor usually licenses in volume and supplies a network of resellers in a territory, so its agreement adds terms on territory, minimum volumes, onboarding resellers and who supports them.
What should a SaaS agreement checklist cover?
The parties, licence grant, permitted users and territory, fees and payment, service levels and support, data protection and data export, intellectual property, confidentiality, liability limits, term, renewal and termination, and what happens to customers when the agreement ends.
Do I still need a EULA if I have a SaaS licensing agreement?
Usually yes. The licensing agreement is between the software owner and the partner. End customers still need terms of service or a EULA from whoever sells to them, which in a white-label deal is often the partner.
Find software to license or white-label
Browse SaaS products, AI tools and APIs whose founders offer licence, white-label and reseller deals, and contact them directly.