Patent Licensing
Patent Indemnification
IP warranties, indemnification triggers, carve-outs, financial caps, and negotiating stronger third-party infringement protection.
FAQ
What is patent indemnification and why does it matter in commercial contracts?
Patent indemnification allocates the risk of third-party IP claims between contracting parties: DEFINITION: a contract provision requiring one party (usually the vendor/licensor) to defend and hold harmless the other party (usually the customer/licensee) against third-party claims that the vendor's product or technology infringes a third party's patent; WHY IT MATTERS: users of technology face infringement liability even when they are not the ones who developed or manufactured the infringing product; customers buying software, SaaS, hardware, or licensed technology can be sued by patent holders who target the customer (the end user) rather than the vendor; indemnification shifts that risk back to the vendor who created the technology; TYPICAL SCENARIO: Company A licenses software from Company B; Company C owns a patent and claims Company A's use of Company B's software infringes Company C's patent; without indemnification, Company A bears the litigation risk; with indemnification, Company B (the licensor) must defend and potentially pay damages; COMMON CONTRACT TYPES WITH IP INDEMNIFICATION: software licenses (perpetual and subscription); SaaS agreements; technology supply agreements; hardware purchase agreements; API/developer agreements; OEM agreements; manufacturing agreements; WHO BENEFITS: customers benefit from vendor indemnification — it provides assurance that using the vendor's product is commercially safe; vendors who refuse all indemnification are less competitive in enterprise sales; LIMITS ON INDEMNIFICATION: virtually all indemnification provisions have limits; vendors do not provide unlimited open-ended indemnification; understanding the limits (carve-outs, caps, conditions) is critical to evaluating the actual protection provided.
What are the key trigger conditions for patent indemnification?
Indemnification triggers determine when the vendor's obligation activates: STANDARD TRIGGER — THIRD-PARTY CLAIM: the most common trigger is a third-party claim alleging infringement; important distinction: 'claim' may mean: (a) a written demand letter or threat (broadest trigger; most protective for customer); (b) a filed lawsuit; (c) a filed and served lawsuit (narrowest; customer bears risk during pre-suit period); NEGOTIATION POINT: customers should push for trigger at demand letter stage; vendors prefer lawsuit-filed trigger to avoid obligations for every threatening letter; NOTICE REQUIREMENTS: indemnification typically requires the indemnitee to: provide prompt written notice of the claim to the indemnitor; failure to provide timely notice can void the indemnification if the delay prejudiced the indemnitor's ability to defend; what is 'prompt' — typically 30 days but contracts vary; TENDER OF DEFENSE: the customer must 'tender' the defense to the vendor; the vendor then has the right (and usually obligation) to assume control of the defense; VENDOR'S RIGHT TO CONTROL DEFENSE: key provision: once the vendor assumes the defense, it controls the litigation strategy; the vendor typically has sole authority to decide whether to settle; customer must cooperate (provide documents; witnesses; testimony) but does not direct strategy; SETTLEMENT AUTHORITY: vendors typically require sole discretion to settle without the customer's consent; customers may push to exclude settlements that impose obligations on the customer (admissions; injunctions; ongoing restrictions); COOPERATION OBLIGATION: the customer must cooperate with the vendor's defense; failure to cooperate can void or reduce the indemnification obligation; cooperation includes: providing access to products; testifying; signing documents; making employees available.
What carve-outs and exclusions typically limit patent indemnification?
Carve-outs significantly limit the scope of IP indemnification in practice: MODIFICATION CARVE-OUT: if the customer modified the vendor's product and the modification causes the infringement, the vendor is not obligated to indemnify; rationale: the vendor cannot be responsible for third-party modifications it did not authorize; COMBINATION CARVE-OUT: if the infringement arises from combining the vendor's product with third-party products not specified or approved by the vendor, the vendor is not liable; this is often the most commercially significant carve-out because most enterprise software is integrated with other systems; customer must ensure they are using the product as specified (not in a novel combination) to preserve indemnification; SPECIFICATION CARVE-OUT: if the infringement arises from the vendor building to the customer's specifications, the customer (not the vendor) bears the infringement risk; the vendor was simply executing the customer's instructions; relevant for custom development agreements and manufacturing agreements; OPEN-SOURCE CARVE-OUT: some vendors exclude indemnification for infringement claims arising from open-source components; customers should push to eliminate this carve-out or require disclosure of open-source components at contract signing; FAILURE TO IMPLEMENT UPDATES: if the vendor provided a non-infringing update or workaround and the customer failed to implement it, the customer may lose indemnification rights; customer must maintain current versions of licensed software to preserve rights; USE OUTSIDE PERMITTED SCOPE: using the product outside the licensed scope (exceeding user limits; using in prohibited applications; using in territories not licensed) may void indemnification; THIRD-PARTY COMPONENTS: if the infringement arises from third-party components that the vendor merely passed through (not developed by the vendor), the vendor may exclude them; this shifts risk back to the customer for vendor's own supply chain decisions.
How do indemnification caps and financial limits work?
Financial limits on indemnification are heavily negotiated in enterprise contracts: TYPICAL CAP STRUCTURES: CAP AS MULTIPLE OF CONTRACT VALUE: 1x annual contract value; 2x total fees paid; 3x fees paid in prior 12 months; IP claims often have higher caps than general liability caps because patent damages can be enormous; UNCAPPED IP INDEMNIFICATION: some large enterprises demand uncapped IP indemnification; venture-backed startups typically cannot accept this; large public companies with mature IP portfolios can; MUTUAL CAPS: even if one party's liability is uncapped for IP claims, the other party's obligations may be capped — negotiation is bilateral; AGGREGATE CAPS: an aggregate cap across all claims (IP + data breach + other) can mean that a large IP settlement exhausts protection for other claims; better to negotiate separate sub-caps; CARVE-OUTS FROM CAPS: IP indemnification is sometimes explicitly carved out of the overall liability cap; this is the most favorable structure for the customer; without a specific carve-out, the IP indemnification obligation folds into the general liability cap; ALTERNATIVE REMEDIES INSTEAD OF DAMAGES: some vendor contracts limit indemnification remedies to: replacement with non-infringing version; workaround; refund; termination; rather than paying patent damages; customer must ensure the financial obligation is also covered (not just defense costs); DEFENSE COSTS ONLY: some agreements limit indemnification to defense costs (attorneys' fees) but not damages; customers must push for coverage of both defense costs AND any damages, settlements, or royalties; INSURANCE REQUIREMENT: many enterprise agreements require the vendor to maintain IP liability insurance; review actual policy limits; umbrella policies; exclusions.
How should enterprise buyers negotiate stronger patent indemnification?
Negotiating points that meaningfully improve customer protection: EXPAND THE TRIGGER: push for indemnification triggered by a demand letter or written claim, not just a filed lawsuit; pre-suit threats cause real business disruption even if litigation never materializes; NARROW THE CARVE-OUTS: combination carve-out: push to limit to 'combinations specifically warned against by vendor in writing'; modification carve-out: limit to 'material modifications by customer not contemplated by the documentation'; open-source carve-out: eliminate or require vendor to disclose all open-source components; ENSURE COVERAGE OF DAMAGES (NOT JUST DEFENSE): confirm the indemnification covers: defense costs; settlements; damages awarded; injunction exposure; costs of implementing a workaround or switching to a non-infringing product; HIGHER OR SEPARATE IP CAP: negotiate IP indemnification with a separate, higher cap than general liability; IP claims warrant higher financial protection than, for example, contract breach; UNCAPPED FOR GROSS NEGLIGENCE/WILLFUL INFRINGEMENT: push to remove financial caps entirely for cases where the vendor knowingly sold infringing products; SETTLEMENT AUTHORITY: customer should have approval rights over settlements that would restrict customer's operations or impose obligations on the customer; SOLE REMEDY CLAUSE: beware 'sole remedy' clauses that make indemnification the exclusive remedy for IP claims; these eliminate contract breach claims if the vendor fails to indemnify properly; PASS-THROUGH OBLIGATIONS: if the vendor is reselling third-party technology, ensure the vendor has obtained appropriate indemnification from that third party AND can pass it through to the customer; REVERSE INDEMNIFICATION: vendors sometimes seek reverse indemnification from customers for claims arising from customer modifications, combinations, or specifications — customers should carefully evaluate what they are committing to.
Related Guides