IP Indemnification Clause

TL;DR: An IP indemnification clause is a specialized third-party indemnity in which a supplier (vendor, licensor, developer, OEM) agrees to defend the customer against claims that the supplier's software, content, deliverables, or services infringe a third party's patent, copyright, trademark, or trade secret rights, and to pay resulting damages or settlement. The clause is heavily negotiated around carve-outs (customer modifications, unauthorized combinations, use outside specifications, post-notice continued use, OSS components, customer-supplied data), the remedies escalator (procure, modify, replace, or refund), and the cap structure (typically uncapped or super-capped at a multiple of annual fees, distinct from the general LoL).

‍

What Is an IP Indemnification Clause?

An IP indemnification clause is a contractual undertaking by one party (typically the licensor or service provider) to defend, hold harmless, and pay damages to the other party (the licensee or customer) for third-party claims that the indemnifying party's IP infringes a patent, copyright, trademark, or trade secret. It is a third-party indemnity, distinct from first-party indemnification for breach of reps and warranties. The trigger is not contract breach; it is an external claim by a third-party rights holder arising from the indemnitee's authorized use of the supplied IP.

The provision exists because the customer cannot perform a freedom-to-operate analysis on every line of code, image, or component in a vendor's product. The vendor controls what goes into the deliverable, has the closest visibility into IP risk, and is best positioned to negotiate licenses or design around third-party rights. The indemnity shifts the litigation burden back to that party. Without one, the customer faces direct exposure to patent troll demands, OSS license violation suits, trademark conflicts from vendor naming, and trade secret claims from vendor employees.

IP indemnification differs structurally from a general indemnification clause. The trigger is narrower (third-party IP only). The remedies escalator (procure, modify, replace, refund) is unique because the underlying loss is often equitable (an injunction) rather than monetary. Carve-outs reflect an industry-standard allocation: the supplier owns risk for what it controls (the product as delivered), and the customer owns risk for what the customer controls (modifications, combinations, misuse). Caps typically sit outside the general LoL, either uncapped or super-capped at two to three times annual fees, reflecting the catastrophic potential of an injunction or willful infringement award.

The clause sits at the intersection of federal IP statutes (35 U.S.C. Section 271 for patent, 17 U.S.C. Section 501 for copyright, Lanham Act 15 U.S.C. Section 1114 for trademark, DTSA 18 U.S.C. Section 1836 for trade secrets), state contract law governing indemnification mechanics, and UCC Section 2-312(3), which establishes a default warranty against infringement by merchant sellers of goods. Because the UCC default is narrow and easily disclaimed, parties negotiate an express IP indemnity rather than relying on the statutory baseline.

‍

Why It Matters

• Catastrophic injunction risk: Unlike most contract claims, IP infringement carries the possibility of an injunction that prevents continued use of the licensed software or services. For a customer with mission-critical workflows on a vendor platform, an injunction can halt operations. The escalator exists to keep the customer operational while the claim is resolved.
• Patent troll exposure: NPEs routinely target enterprise customers rather than vendors, expecting nuisance settlements. Without a vendor IP indemnity, customers bear the full defense cost even when the alleged infringement arises from the vendor's product. NPEs filed approximately 60 to 65 percent of all U.S. patent litigation recently (RPX and Unified Patents).
• OSS license compliance: Software products include thousands of OSS components under varied license terms (GPL, LGPL, Apache, MIT, BSD, AGPL). Copyleft non-compliance can trigger copyright claims and forced source disclosure. Versata v. Ameriprise (2014), Artifex v. Hancom (2017), and ongoing Software Freedom Conservancy enforcement confirm OSS violations are enforceable. The indemnity allocates this risk to the vendor that selected the components.
• Damages magnitude: Patent damages can include royalties, lost profits, and treble damages plus attorneys' fees for willful infringement (35 U.S.C. Sections 284 and 285). Copyright statutory damages reach $150,000 per work for willful infringement (17 U.S.C. Section 504). Trademark damages include defendant's profits, plaintiff's damages, and costs (15 U.S.C. Section 1117). These exposures dwarf typical SaaS LoL caps.
• Defense cost economics: Median patent litigation defense runs $2 million to $5 million per side through trial (AIPLA), and complex software cases routinely exceed $10 million. A customer defending a meritless claim without a vendor indemnity may spend more than the contract value.
• Insurance gap: Most CGL policies exclude IP infringement claims, and dedicated IP infringement insurance is expensive and limited. Contractual indemnification is often the only practical risk transfer.
• Procurement requirements: Enterprise procurement and InfoSec teams treat IP indemnification as non-negotiable in vendor MSAs. Vendors that refuse cannot pass enterprise onboarding, making the clause table stakes.

‍

Key Elements of a Well-Drafted IP Indemnification Clause

1. Scope of covered IP rights: Specify categories (patent, copyright, trademark, trade secret) and jurisdictions (U.S. only, designated countries, worldwide). Patent indemnity is the most contested because infringement is strict liability and claims can be asserted globally. Vendors typically resist beyond the U.S., EU, and key markets.
2. Defense, control, and settlement: Allocate duty to defend versus right to defend. Most IP indemnities give the vendor sole control of defense and settlement. The customer should retain consent rights for settlements that impose non-monetary obligations, include an admission of liability, fail to include a full release, or restrict future operations.
3. Notice and cooperation: Require prompt written notice, with late notice as a defense only to the extent of actual prejudice. Require customer cooperation including access to documents, witnesses, and technical information.
4. Carve-outs and exclusions: Standard carve-outs: (a) customer modifications; (b) combination with items not supplied or recommended by the vendor where infringement would have been avoided absent the combination; (c) use outside specifications; (d) continued use after notice of a non-infringing alternative; (e) compliance with customer-specified designs; (f) use of a superseded version when a non-infringing version was available; and (g) infringement from customer-supplied content or data.
5. Remedies escalator: A defined sequence: (a) procure the right to continue use; (b) modify to be non-infringing while preserving substantially equivalent functionality; (c) replace with a non-infringing equivalent; or (d) terminate and refund prepaid fees pro-rata (SaaS) or on a depreciation schedule (perpetual licenses). Customers should push for the substantially equivalent functionality standard and refund of all fees, not just the unused prepaid portion.
6. Financial cap and interaction with the general LoL: State whether IP indemnification is uncapped, super-capped (commonly two to three times annual fees), or subject to the general LoL. State expressly whether IP indemnity payments count against the LoL aggregate. The enterprise norm is to carve IP indemnity out of the LoL with a separate cap.
7. Sole and exclusive remedy: Vendors typically state the indemnity is the customer's sole remedy. Customers should narrow this so it does not bar claims for gross negligence, willful misconduct, or breach of express IP ownership reps.
8. Mutual (customer-back) indemnification: Where the customer supplies content, data, or branding integrated into the deliverable, the vendor will require a customer-back indemnity for claims arising from those inputs. Standard in SaaS and white-label arrangements.
9. Open-source treatment: Address whether the indemnity covers OSS components. Vendors often carve out OSS claims; sophisticated customers push for full coverage where the vendor selected and integrated those components.
10. Survival: The IP indemnity should survive termination for the period the customer may use the deliverable (perpetual for owned deliverables; through the wind-down period for SaaS).

‍

Market Position & Benchmarks

Where Does Your Clause Fall?

• Vendor-Favorable: U.S. issued patents only (no foreign, no applications). All standard carve-outs plus a blanket carve-out for third-party and OSS components. Cap at one times annual fees or subject to general LoL. Sole and exclusive remedy with no willful misconduct carve-out. Vendor controls defense and settlement without customer consent. Refund limited to fees paid in the prior 12 months.
• Market Standard: Patent, copyright, trademark, and trade secret indemnity covering the U.S. and select foreign jurisdictions where the deliverable is used. Standard carve-outs for customer modifications, unauthorized combinations, use outside specifications, post-notice continued use, and customer-supplied content. OSS covered when integrated by the vendor. Super-cap at two to three times annual fees, carved out from the LoL. Vendor controls defense with customer consent for settlements imposing non-monetary obligations. Escalator requires procure, modify, or replace attempts before terminate-and-refund.
• Customer-Favorable: Worldwide patent, copyright, trademark, and trade secret indemnity, including pending applications and post-issuance proceedings. Carve-outs limited to customer modifications and infringement that would have been avoided absent customer's specific design instructions. OSS fully covered. Uncapped, carved out from the LoL. Customer consent required for any settlement. Escalator requires procure or modify; replacement or termination requires consent. Refund of all fees paid plus documented switching costs and attorneys' fees.

Market Data

• Approximately 75 to 80 percent of enterprise SaaS and software license agreements include an express IP indemnification clause, approaching 100 percent in agreements with Fortune 500 customers (ACC Contracting Practices Survey; Practical Law What's Market, 2023 to 2024).
• Cap structure in technology contracts: approximately 50 percent super-capped at a multiple of annual fees (most commonly two to three times); approximately 30 percent uncapped or capped at a high fixed dollar amount ($5 million to $25 million); approximately 20 percent subject to the general LoL (Practical Law What's Market, Technology Transactions data, 2024).
• Patent litigation defense costs through trial average $2 million to $5 million per side for cases with $1 million to $25 million at stake, exceeding $10 million for higher-stakes cases (AIPLA Report of the Economic Survey, 2023).
• NPEs filed approximately 60 to 65 percent of all U.S. patent litigation in recent years, with software vendors and their enterprise customers as the most frequent defendants (RPX and Unified Patents annual reports, 2023 to 2024).
• The remedies escalator (procure, modify, replace, refund) appears in approximately 90 percent of enterprise software and SaaS IP indemnification clauses (Bowman Brogden Tech Transactions Benchmark, 2023; ACC IP Indemnity Survey).
• Approximately 65 percent of enterprise vendors carve out OSS-related claims from the IP indemnity; approximately 35 percent provide express coverage when the vendor selected and integrated the components (Linux Foundation OpenChain industry data, 2023).
• Worldwide patent indemnification appears in approximately 25 percent of enterprise vendor agreements; the remainder limit coverage to the U.S. or a defined list of countries (Practical Law cross-border tech transactions data, 2024).

Sample Language by Position

Vendor-Favorable: "Vendor shall defend Customer against any third-party claim that the Software, as delivered and used in accordance with this Agreement, infringes a U.S. patent issued as of the Effective Date or a U.S. copyright, and shall pay damages finally awarded or agreed in settlement. Vendor has no obligation for claims arising from (i) modifications not made by Vendor; (ii) combination with items not supplied by Vendor; (iii) use outside the Documentation; (iv) continued use after a non-infringing alternative is provided; or (v) any open-source software included in the Software. Vendor's aggregate liability shall not exceed the fees paid in the prior twelve months. This Section is Vendor's sole liability and Customer's sole remedy."

Market Standard: "Vendor shall defend and indemnify Customer from any third-party claim that Customer's authorized use of the Software infringes any U.S. or foreign patent issued as of the date of the alleged infringement, copyright, registered trademark, or trade secret, and pay damages awarded or agreed in a Vendor-approved settlement. Obligations are conditioned on prompt notice, sole control of defense and settlement (subject to Customer's consent for settlements imposing non-monetary obligations or failing to release Customer, not unreasonably withheld), and reasonable cooperation. Vendor has no obligation for claims arising from (i) Customer modifications; (ii) combination with items not supplied by Vendor where infringement would have been avoided absent the combination; (iii) use outside the Documentation; (iv) continued use after a non-infringing alternative is made available; or (v) Customer Content. If the Software becomes or is likely to become the subject of an infringement claim, Vendor shall, at its expense: (1) procure the right to continue use; (2) modify to be non-infringing while preserving substantially equivalent functionality; (3) replace with a non-infringing alternative of substantially equivalent functionality; or (4) if none is feasible, terminate the affected Order and refund a pro-rata portion of prepaid fees. Vendor's aggregate liability shall not exceed three times the fees paid in the prior twelve months and applies separately from the general LoL. This is Customer's sole and exclusive remedy."

Customer-Favorable: "Vendor shall defend, indemnify, and hold harmless Customer and its Affiliates, officers, directors, employees, and agents from any and all third-party claims, losses, damages, costs, and expenses (including reasonable attorneys' fees) alleging that the Deliverables or Services (including all open-source software incorporated therein) infringe or misappropriate any patent, patent application, copyright, trademark, trade secret, or other IP right in any jurisdiction worldwide. Vendor has no carve-outs except for infringement that would have been avoided absent (i) Customer modifications made without Vendor's involvement, or (ii) Customer's specific written design instructions to Vendor. Vendor controls defense subject to Customer's consultation and consent rights (not unreasonably withheld) for any settlement. If any Deliverable becomes the subject of an infringement claim, Vendor shall, at its expense, procure the right to continue use or modify the Deliverable to be non-infringing while preserving full functionality. Replacement or termination requires Customer's prior written consent. The obligations under this Section are uncapped and apply in addition to all other rights and remedies at law or in equity."

‍

Example Clause Language

The following examples illustrate IP indemnification in specific transactional contexts.

Enterprise SaaS (Mutual): "Vendor IP Indemnity. Vendor shall defend and indemnify Customer against any third-party claim that Customer's use of the Service in accordance with this Agreement infringes any U.S. or EU patent, copyright, registered trademark, or trade secret. The remedies here, with Vendor's procure-modify-replace-or-refund options above, are Customer's exclusive remedy. Customer IP Indemnity. Customer shall defend and indemnify Vendor against any third-party claim that Customer Content, Customer-Provided Configurations, or data transmitted through the Service infringes any third-party IP right or violates any law. Each party's obligations are conditioned on prompt notice, sole control of defense, and cooperation, with consent for settlements imposing non-monetary obligations on the indemnified party. The Vendor IP Indemnity is capped at three times the fees paid in the prior twelve months. The Customer IP Indemnity is uncapped. Both are carved out from the general LoL."

Software Development / Custom Deliverables: "Developer shall defend and indemnify Client against any third-party claim that the Custom Deliverables infringe any patent, copyright, trademark, or trade secret. The indemnity covers all open-source components and third-party libraries selected by Developer. It does not cover (a) Client's specific written design specifications that Developer objected to in writing; (b) Client-supplied content, data, or branding; or (c) Client modifications after delivery. If a court enjoins Client's use, or if Developer reasonably determines an injunction is likely, Developer shall, at its expense, procure the right to continue use, modify the Custom Deliverables to be non-infringing while preserving the functional specifications, or replace them with non-infringing equivalents. If none is commercially reasonable, Developer shall refund all fees paid plus Client's documented reasonable transition costs up to $250,000. Developer's liability under this Section is uncapped."

OEM / Reseller Agreement: "Manufacturer shall defend and indemnify Reseller and Reseller's end customers against any third-party claim that the Products, as supplied and used in accordance with the Documentation, infringe any patent, copyright, trademark, or trade secret in the Territory. The indemnity flows through to end customers as third-party beneficiaries under the EULA, and Manufacturer authorizes Reseller to extend equivalent protection. Manufacturer's liability is capped at $5,000,000 per claim and $15,000,000 in the aggregate per calendar year. The cap does not apply to willful infringement or claims relating to Manufacturer's product naming or trademarks."

‍

Common Contract Types

• Enterprise software licenses: IP indemnification is near-universal, with heavy negotiation over patent scope, super-cap multiples, and OSS treatment.
• SaaS and cloud services: Mutual IP indemnification is standard. Vendor covers platform IP; customer covers content and configurations. Caps tie to annual fees.
• Software development and SOW services: Developer indemnifies for infringement in custom deliverables, with carve-outs for client-specified designs and supplied materials.
• Content licensing: Licensors of stock images, music, video, or written content indemnify licensees against copyright and right-of-publicity claims. Common in advertising and publishing.
• OEM and reseller agreements: Manufacturers indemnify resellers and often the resellers' end customers, requiring careful third-party beneficiary drafting.
• Hardware purchase and supply: Suppliers indemnify buyers against patent and trademark claims. UCC Section 2-312(3) supplies a default implied warranty, typically superseded by express indemnity.
• Technology MSAs: The indemnity sits in the master agreement and applies across all SOWs, with order-specific exceptions.
• Professional services and consulting: Providers indemnify clients for infringement in work product and tools brought to the engagement.
• White-label and private-label: The underlying tech vendor indemnifies the white-label partner, often with broader coverage given the partner's exposure.
• Commercial OSS agreements: Vendors of OSS-based products (Red Hat, Canonical, MongoDB, Confluent) provide indemnification tailored to OSS compliance and patent claims on commercial enhancements.

‍

Negotiation Playbook

Key Drafting Notes

• Define IP rights with precision: Patent, copyright, trademark, and trade secret have different statutory frameworks (35 U.S.C. Section 271, 17 U.S.C. Section 501, 15 U.S.C. Section 1114, and 18 U.S.C. Section 1836). A reference to intellectual property without enumeration creates ambiguity. State expressly whether the indemnity covers patent applications, post-issuance proceedings (IPR, PGR, ex parte reexamination), and unregistered trademarks.
• Anchor geographic scope to business reality: Patent rights are jurisdictional and FTO analyses get expensive fast. The customer's actual deployment footprint should drive scope. A SaaS vendor with U.S. and EU customers should provide U.S. and EU coverage; demanding worldwide coverage when the customer operates in three countries is a reach vendors will resist.
• Calibrate the cap to risk: A super-cap at two to three times annual fees reflects catastrophic potential while preserving a ceiling. Uncapped indemnity suits high-trust, high-value relationships but is hard for vendors to underwrite. Capping IP indemnity at the general LoL is vendor-favorable and enterprise customers should resist it, especially where the LoL is set at a low multiple of fees.
• Address open-source explicitly: OSS is pervasive and silence creates ambiguity. The defensible position: vendor indemnifies for OSS it selected and integrated, with carve-outs only for OSS the customer requested. Vendors that broadly carve out OSS may find enterprise customers reject the indemnity entirely.
• Tighten the escalator: Push for substantially equivalent functionality (not merely similar or commercially reasonable) when the vendor modifies or replaces. Without this anchor, the vendor can downgrade while claiming compliance. Require consultation before terminate-and-refund, since termination is the worst outcome for the customer.
• Coordinate with the LoL: State expressly whether IP indemnity is inside or outside the general LoL. The enterprise norm is to carve it out. State whether the IP cap is in addition to the LoL or counts against it. Address whether the consequential damages exclusion applies to indemnity payments (customers should push for an express exclusion).

Common Pitfalls

• Conflating duty to defend with duty to indemnify: The duty to defend is broader and triggers earlier. It obligates the vendor to fund and manage litigation from tender, even if the claim is later determined to be outside scope. Indemnities using only indemnify and hold harmless leave the customer to fund its own defense and seek reimbursement after judgment.
• Overbroad carve-outs that swallow the indemnity: A combination carve-out that excludes any claim involving non-supplied items defeats the indemnity in real deployments, since customers always combine vendor products with other systems. Limit it to claims that would have been avoided absent the combination.
• Insufficient escalator on perpetual licenses: A pro-rata refund works for SaaS but is inadequate for a perpetual license. For perpetual licenses, refund should follow a depreciation schedule (commonly five-year straight-line) or include documented switching and reimplementation costs.
• Ignoring the patent troll posture: NPEs target customers with nuisance demands. Vendors may want to settle quickly to avoid precedent while customers want a vigorous defense. Give the customer veto rights over settlements involving admissions of liability or affecting the customer's broader position.
• Insurance and subrogation gaps: If the customer recovers from its own IP insurance, the indemnity should be reduced by net recoveries. The vendor should be subrogated to the customer's rights for payments made. Without these provisions, parties face double-recovery and coordination problems.
• OSS ambiguity: Silence on OSS coverage creates risk for both parties. Address it directly: vendor covers OSS it integrated, customer covers OSS it requested, both cooperate on compliance audits.

‍

Jurisdiction Notes

• United States: IP indemnification is governed by state contract law; the underlying IP claims arise under federal statutes: patent (35 U.S.C. Section 271 et seq.), copyright (17 U.S.C. Section 501 et seq.), trademark (Lanham Act, 15 U.S.C. Section 1114 et seq.), and trade secret (DTSA, 18 U.S.C. Section 1836, plus state UTSA adoptions). UCC Section 2-312(3) provides a default warranty against infringement for merchant sellers, but it is narrow and easily disclaimed. Patent damages can include treble damages and attorneys' fees for willful infringement (35 U.S.C. Sections 284 and 285); copyright statutory damages reach $150,000 per work (17 U.S.C. Section 504). The SCO Group v. IBM litigation (2003 to 2016) and Oracle v. Google (2010 to 2021, resolved by the Supreme Court on Java API fair use) shaped industry expectations on IP indemnity. Delaware and New York are the common choice-of-law jurisdictions.
• United Kingdom: English law treats IP indemnities as contractual undertakings under ordinary construction principles. The Patents Act 1977, Copyright, Designs and Patents Act 1988, Trade Marks Act 1994, and the law of confidence (in part codified by the Trade Secrets Regulations 2018) provide the framework. The Unfair Contract Terms Act 1977 may subject indemnities in standard-form business contracts to a reasonableness test. Courts construe ambiguities contra proferentem. Post-Brexit, parties should confirm scope language captures UK and EU coverage as separate jurisdictions.
• European Union: The EU Trade Secrets Directive (2016/943) and EU Trade Marks Regulation (2017/1001) harmonize frameworks. The Unified Patent Court (UPC), operational since June 2023, allows centralized patent enforcement across participating member states, increasing the importance of EU-wide patent indemnification. The Database Directive (96/9/EC) creates a sui generis database right with no direct U.S. analog.
• Other jurisdictions: Civil law systems (France, Germany, Japan, China) use indemnity-like obligations rather than common-law indemnification, with similar risk allocation. China's IP regime strengthened under 2020 amendments to the Patent, Copyright, and Trademark Laws. India follows English common law principles. Cross-border SaaS arrangements should specify patent scope by named countries rather than generic worldwide language.

‍

Related Clauses

• Indemnification: The general framework. IP indemnification follows the same mechanics (notice, defense, settlement, cooperation) but with narrower triggers and a unique remedies escalator.
• IP Clause: Establishes ownership of pre-existing and developed IP, defining what the vendor is supplying and the scope of the indemnity.
• License Grant Clause: Grants the customer the right to use the vendor's IP. The IP indemnity protects the exercise of that license against third-party challenges.
• Work for Hire: Allocates ownership of custom deliverables. Interacts with the IP indemnity to define infringement risk for client-specified versus vendor-specified design choices.
• Limitation of Liability: The general LoL cap. IP indemnification is typically carved out or subject to a separate super-cap.
• Warranty Disclaimer: Disclaims implied warranties including UCC Section 2-312(3) infringement warranty. The express IP indemnity replaces it.
• Sublicense Clause: Authorizes sublicensing to affiliates, end customers, or service providers. The IP indemnity should expressly cover authorized sublicensees.

‍

This glossary entry is for informational purposes only and does not constitute legal advice. Market data represents general trends and may vary by industry, jurisdiction, and deal size. Consult qualified legal counsel for specific contract matters.