The indemnification clause in an Oracle agreement is the provision under which Oracle agrees to defend the buyer, and to pay the resulting costs, if a third party claims that the licensed Oracle software infringes that third party's intellectual property. It reads like standard language that no one negotiates, and in most deals no one does. That is the problem. The default Oracle indemnity is narrower than buyers assume, it carries exclusions that can remove the protection in exactly the situations where it matters, and it sits alongside a limitation of liability that caps the very remedy the indemnity promises. A buyer who treats the clause as boilerplate accepts a level of risk it never priced. This note explains what the standard language covers, where it falls short, and how a buyer should approach it in a negotiation.
What the indemnity actually covers.
The core promise is straightforward. If a third party sues the buyer alleging that the Oracle software, as delivered by Oracle, infringes a patent, copyright, or trade secret, Oracle will take over the defence of the claim and pay the damages or settlement that results. In exchange the buyer must notify Oracle promptly, give Oracle control of the defence, and cooperate. If the software is found to infringe, Oracle typically reserves the right to procure the buyer a right to keep using it, to modify it so it no longer infringes, or, as a last resort, to take it back and refund a depreciated portion of the fees.
That last remedy is where buyers are often surprised. The refund is not the full price paid. It is usually the licence fee reduced by a depreciation schedule, so a buyer several years into a perpetual licence may recover very little even though the software is withdrawn. The indemnity protects against the lawsuit, but the fallback remedy can leave the buyer without the software and without meaningful compensation. Understanding this is part of the wider discipline of reading what an agreement really says, which is the subject of our note on the Oracle licence agreement.
The exclusions that matter.
The standard indemnity does not apply to every infringement claim. It carves out several categories, and the carve outs are where exposure hides. The indemnity usually does not cover claims arising from the buyer's combination of the Oracle software with other products not supplied by Oracle, from the buyer's modification of the software, from the buyer's continued use of an infringing version after Oracle has supplied a non infringing one, or from the buyer's use of the software outside the scope of the licence.
Each exclusion is reasonable in isolation, but together they remove the protection in the realistic case. Enterprise software is always combined with other systems, frequently customised, and sometimes run in configurations the licence did not anticipate. A buyer that integrates Oracle software into a wider estate, which is to say every buyer, should understand that the combination exclusion can be read broadly by a vendor under pressure. The buyer should test the exclusions against its actual deployment rather than assuming the indemnity will respond.
How the liability cap undercuts it.
The indemnification clause does not stand alone. It interacts with the limitation of liability clause, and that interaction decides how much the indemnity is really worth. In many Oracle agreements the indemnity is subject to the general liability cap, which is often expressed as a multiple of the fees paid in a recent period. If the cap applies to the indemnity, then Oracle's exposure to defend and pay for an infringement claim is limited to that figure, no matter how large the third party claim turns out to be.
A buyer who wins the argument that Oracle must indemnify, only to find that the indemnity is capped at a fraction of the third party damages, has not been protected at all. The negotiation point is to carve the indemnity out of the liability cap, so that infringement defence is uncapped or subject to a much higher sub cap. Oracle resists this, but the principle is sound. The party that controls the intellectual property should carry the unlimited risk that it infringes. For the broader picture of how a buyer should approach the bargain, see the negotiation frameworks note.
Where the negotiation leverage sits.
Buyers assume indemnification is non negotiable. It is not. The leverage to improve it exists at the same moments as the leverage to improve price, which is at a new purchase, a large renewal, or a contract consolidation. When Oracle wants a signature, the buyer can put the indemnity on the table alongside the commercial terms. The asks that tend to succeed are removing or narrowing the combination exclusion to reflect ordinary integration, carving the indemnity out of the liability cap, and clarifying that the refund remedy is calculated on a basis the buyer can accept.
The buyer who raises these points early, framed as risk allocation rather than as distrust, often finds Oracle willing to move on at least some of them. The buyer who waits until a claim arises has no leverage at all. Timing the request to the commercial cycle matters, and the same timing logic that governs price applies here, as set out in the year end leverage note.
Indemnity in a cloud agreement.
The indemnity question changes shape in an Oracle cloud subscription. In a SaaS or infrastructure subscription the buyer does not hold a perpetual licence to refund, so the fallback remedy is different, and the combination and modification exclusions apply differently because the buyer controls less of the environment. The buyer moving Oracle workloads to a subscription model should read the indemnity afresh rather than assuming it mirrors the on premises agreement.
The cloud agreement also introduces the vendor's own third party components, and the buyer should confirm that the indemnity covers the whole service as delivered, not only the parts Oracle wrote. For buyers structuring cloud commitments the wider commercial considerations are covered in the OCI universal credits deal page, and the licence portability questions in the Oracle Database product page.
Documenting the position.
Whatever the buyer negotiates, the position must be documented in the agreement itself rather than in correspondence. An indemnity improved in an email exchange but left out of the signed contract is worthless when a claim arrives. The buyer should ensure that every concession on exclusions, on the liability cap interaction, and on remedies is captured in the executed document, and should keep the full record of how the language was reached. The discipline of documenting commercial positions is set out in the document trail note.
The buyer should also map the indemnity against its insurance. Some infringement exposure may be covered by the buyer's own policies, and the interaction between the contractual indemnity and the insurance position should be understood so the buyer knows where the real protection lies. This mapping is part of the contract review discipline rather than an afterthought.
Engaging an independent advisor.
An independent advisor reads the indemnification clause against the buyer's actual deployment, identifies which exclusions could remove the protection, tests the interaction with the liability cap, and builds the negotiation asks that improve the position at the moments the buyer holds leverage. The advisor sits on the buyer side and treats the indemnity as a commercial term to be negotiated rather than as boilerplate to be accepted. For the full contract reading service this sits within see our contract review service, and for the related wider framework read the Oracle Negotiation Playbook.
A European financial services buyer engaged an advisor before signing a large new licence agreement in 2024. The advisor identified that the indemnity was fully subject to the liability cap and that the combination exclusion was drafted broadly enough to cover the buyer's standard integration pattern. The advisor negotiated the indemnity out of the cap and narrowed the exclusion, so the protection responded in the realistic scenario rather than only in theory. The improvement cost nothing because it was traded as part of a deal Oracle wanted to close.