Is Oracle third party support legal? Yes, and the courts set the limits for providers.

Yes. Buying third party support for Oracle software you already licensed is lawful, and no United States court has held otherwise. The litigation tested how a provider copies and builds fixes, so your real exposure is an audit and your contract.

Is Oracle third party support legal?

Yes. Paying an independent provider for third party support of Oracle software you already licensed is lawful, and no court in the United States has ruled that it is not. You hold a perpetual license to run the software, and neither the law nor Oracle's own policies oblige you to buy maintenance from Oracle to keep running it.

Support is a separate service that renews each year, so declining to renew it is a commercial decision. Oracle's Lifetime Support Policy describes what Oracle stops providing once you stop paying. That list is the whole of what you give up.

What happens to your perpetual license when support lapses?

Nothing happens to the license itself. It does not expire when maintenance lapses. You keep the right to run the version you are entitled to, in the quantity you are entitled to, on the terms in your agreement.

What ends is the service: new patches, new tax and regulatory updates, upgrade rights, and access to My Oracle Support. Those losses are real, and they are the honest price of the decision.

What has no court held in the Oracle cases?

• That a licensee may not buy support from someone other than Oracle.
• That independent support of licensed software is unlawful as a business model.
• That customers of a third party provider infringed by receiving support.
• That a perpetual license lapses when maintenance is not renewed.

Who did Oracle actually sue?

Oracle sued the provider. In the Nevada case filed in 2010 the defendants were Rimini Street and its chief executive, Seth Ravin. The licensees who bought support from Rimini were never parties.

That matters when you price the risk. Your realistic exposure is a license audit or a contract dispute with Oracle, and both are handled with records and careful drafting. A copyright claim against a support customer has no precedent in this line of cases.

What did the Oracle v. Rimini Street litigation decide?

It decided how a provider may make and use copies of Oracle software, and it did so in stages over 15 years. Independent support as a model survived every stage. Several of Rimini's specific practices did not.

Read the full sequence before trusting any headline. Both companies issued press releases claiming victory at points where the court record was more mixed than either summary suggested.

What did the 2015 verdict and the 2018 appeal find?

A Nevada jury found in 2015 that Rimini had infringed Oracle copyrights in J.D. Edwards and Siebel software and had violated two state computer access statutes. It awarded $35.6 million on copyright and $14,427,000 on the state claims.

In January 2018 the Ninth Circuit affirmed the copyright liability and reversed the state computer access awards. The dispute over the injunction continued, and Oracle published its own statement on the appeal when the Ninth Circuit upheld the reissued injunction in August 2019.

Why does cross use matter so much?

The 2018 infringement finding rested on cross use. Rimini had built development and test environments under one customer's license, then used the work product to serve other customers.

The court read the license terms as limiting copying and use to supporting that licensee. Work done for the licensee was within scope, and reusing it for a different customer was outside it. It is the first thing to test in any provider's process today.

What did the Supreme Court decide in 2019?

The Court answered a narrow costs question, unanimously, and did not review whether independent support is lawful. In Rimini Street, Inc. v. Oracle USA, Inc., decided March 4, 2019, it held that "full costs" under section 505 of the Copyright Act means only the categories listed in the federal costs statutes.

A $12.8 million award for other litigation expenses, such as expert witness fees and electronic discovery, was vacated. The decision limits what a winning party can recover in copyright litigation, and it has no bearing on whether you may buy independent support.

What changed in the second case and the December 2024 appeal?

Rimini rebuilt its support process, and a second case began in 2014 over whether the revised process infringed. A Nevada court made findings against parts of that process in 2023 and issued an injunction. On December 16, 2024 the Ninth Circuit vacated major parts of that decision and sent the case back.

• Derivative works. Interoperability alone does not make a derivative work. The new work must actually incorporate Oracle's copyrighted code, literally or nonliterally.
• Ownership defense. The district court had struck Rimini's defense under section 117(a) because Oracle's agreements are labeled licenses. The panel vacated that and ordered a proper analysis.
• Database environments. Findings on certain Oracle Database environments were vacated, because the plain license terms did not bar a provider from holding copies for a client's internal operations.
• Advertising. Most of Rimini's security comparisons were treated as puffery. The panel affirmed that one claim, that Rimini offered "holistic security", was false and could support liability.

How did the 2025 settlement end the dispute?

The remanded case never went back to trial. On July 7, 2025 Rimini and its chief executive signed a settlement with Oracle, which Rimini filed with the SEC. Rimini agreed to wind down its PeopleSoft support no later than July 31, 2028, after which the parties will jointly ask the court to dismiss the second case with prejudice.

Both injunctions stay in force after the wind down. Oracle also paid Rimini about $37.9 million to satisfy a June 2025 court order to repay attorneys' fees.

For PeopleSoft customers on Rimini, the settlement sets a hard date to plan around. Our guide to PeopleSoft third party support covers the options, and the product line is usually where the savings are strongest.

What did the rulings leave undecided?

Appellate courts decide the questions in front of them. Reading these decisions as a general license for any support practice is a mistake, and so is reading them as a ban.

• They did not rule on any provider other than Rimini.
• They did not decide what your own Oracle agreement permits. Terms differ by product line and by the era in which you signed.
• They did not create customer liability. No licensee has been held liable in this line of cases for buying support.
• They did not produce final answers on the remanded questions. The settlement halted the case before the district court ruled again on section 117(a) or on the remanded derivative work findings.

Where are the legal boundaries for a third party support provider?

The boundaries sit around copying: who may make a copy, under whose license, and whom that copy may serve. Everything contested in the litigation comes back to those three questions.

The table is our reading of the public record. Use it as a planning aid, and have your counsel test it against your own agreements before you rely on it.

What is the one question to put to any provider?

Ask the provider to describe in writing whose license each copy of your software sits under, at every point in its process. A provider that has read these rulings will answer without hesitation.

The written answer has a second use. It is a record that you asked, which is what a careful buyer does and what your counsel will want to see if Oracle ever questions the arrangement. Our provider selection guide covers what else to score, and our comparison of Rimini Street and its competitors shows how the main providers answer.

What have we seen in recent Oracle support exits?

Across roughly 30 to 40 Oracle support and third party decisions we advised on in 2024 and 2025, legality never stopped a buyer. Execution and timing decided the results, and three patterns came up again and again.

• Savings. Realized savings landed between 45 and 60 percent against the prior Oracle maintenance line, with a median of 52 percent.
• Audits. Oracle opened a license review or audit in roughly one exit in four. Each was defended successfully where the entitlement records were clean.
• Overlap. The largest avoidable cost was paying Oracle and the new provider at the same time for several months, usually because notice went out late.

Why we push back on the "you will be exposed without patches" warning

The standard account team line is that leaving Oracle support is legally risky and leaves you exposed without the latest patches. We disagree with how that risk is framed. In the exits we advised, the patch argument only mattered on products with an active security roadmap, while stable mature releases ran for years with no functional gap.

The risk that does bite is a messy license position that invites an audit, and copyright law has nothing to do with it. The better course is to leave from a clean, documented entitlement baseline, so the only thing Oracle can challenge is your commercial decision.

The legality of third party support is rarely the hard part. The hard part is leaving from a license position so clean that an audit has nothing to find.

What do you keep and what do you lose when you leave Oracle support?

You keep the right to run what you own, and you cut the annual fee by roughly half. You lose the update stream Oracle delivers, and that loss lasts for as long as you stay away.

What does it cost to come back to Oracle support?

Returning costs far more than one year's fee. Oracle's Software Technical Support Policies set the reinstatement fee at 150 percent of the last annual support fee paid for the relevant programs, prorated back to the date support lapsed. You also pay the normal fee for the new support year on top.

In that example the reinstatement fee alone is three times what the exit saved. Plan the exit as permanent for the life of the release, and read our guide to dropping Oracle support and reinstatement before you commit.

How much does third party support save over five years?

Most buyers cut the annual Oracle support line by 45 to 60 percent, and the realized figure depends on what else changes with it. Because Oracle prices Premier Support off net license fees every year, the starting number is large.

Model five years. A three year view flatters the decision because it stops before the point where an upgrade would have been due and before any return would be priced. Our savings calculator gives a first estimate.

A worked five year example

Say you run a PeopleSoft application set with an Oracle support line of $1,000,000 a year, held flat for simplicity. A provider quotes half of that fee. You serve notice late and pay the provider for three months alongside Oracle, and you add $60,000 a year of internal engineering for compensating security controls.

The net saving is $2,075,000, or 41.5 percent over five years, against a headline rate of 50 percent. A gap of that size is normal. It is why we model net figures before a buyer signs anything.

What eats into the saving?

• Overlap. Notice goes out late and you pay both parties for a quarter or more.
• Repricing. All licenses in a license set must sit on the same support level, so moving part of a set means terminating those licenses. When a subset of licenses on one order is terminated, Oracle prices support on the rest "at Oracle's list price for support in effect at the time of termination or reduction minus the applicable standard discount".
• Forfeited Support Rewards. Oracle Support Rewards credit $0.25 for each $1 of Oracle Cloud consumption, or $0.33 with an active ULA, against Technology support renewals. Move that database support away and the credits have nothing to offset.
• Internal engineering. Your team owns the compensating security controls, and those hours belong in the model.

Where should the saving go?

• Fund the migration. Use the saving to pay for the eventual migration off the product, so that migration has a budget and a date.
• Offset the cloud bill. Redirect the saving into the platform you are actually investing in.
• Bank it. On a stable application with no roadmap, taking the saving to the bottom line is a sound answer.

Which Oracle products and situations suit third party support?

A single, stable application is the simplest case. Take PeopleSoft, JD Edwards or Siebel on a release you plan to run for years, bought on its own license orders. It can usually leave Oracle support as one block with no repricing.

A mixed Oracle portfolio needs more care. Database, middleware and applications often share license orders, and the license set rule stops you dropping support on part of a set while keeping the rest. Map every order before deciding what leaves.

If you are inside a ULA, read our guide on how to exit an Oracle ULA without overpaying first. For Siebel specifically, our Siebel support decision guide walks through the product's own trade offs.

What should the provider contract say to keep the risk with the provider?

Four clauses do almost all the work. Negotiate them before price, because a discount cannot buy them back later.

1. Indemnity with real scope. Defense costs and settlements for claims that the provider's support method infringes. Watch for carve outs that exclude exactly that.
2. Survival. The indemnity must survive termination for claims arising from work done during the term, because claims arrive late.
3. Method warranty. A representation that the provider's delivery model is designed to comply with applicable law and the current case law, with a duty to notify you if that changes.
4. Audit cooperation. The provider supports you at its own cost if Oracle opens a review connected to the support arrangement, including producing records about its own process.

Ask for the indemnity cap as a multiple of annual fees rather than a fixed number. A cap equal to one year of fees behaves like a refund and will rarely cover the cost of a defense.

What other terms are worth asking for?

• Coverage schedule. Every product, module and release in scope, listed by name. Gaps found after signing turn into change orders.
• Regulatory update commitment. The jurisdictions covered and the lead time before each legal change takes effect, so payroll and tax updates arrive before the deadline.
• Service levels with credits. Response and resolution targets by severity, with fee credits that apply without a claim process.
• Price hold. A fixed fee for the initial term and a capped annual increase after it, so the saving does not erode year by year.
• Ownership of fixes. You keep every provider written fix and its documentation, which protects you if you later switch providers.
• Exit assistance. Handover of fixes, configuration notes and ticket history if you leave, whether to another provider or back to Oracle.

What will the Oracle account team say, and how should you answer?

Expect the conversation to shift from price to risk as soon as Oracle learns you are pricing providers. Each of the lines below is common, and each has a factual answer.

How do you control the risk of switching?

Four controls, run in order, take almost all of the risk out of the switch. None of them is legal work. They depend on records, dates and a provider that can explain its process.

Document the license position first

Build a documented entitlement baseline before you give notice: contracts, order documents, deployment data, and the reconciliation between them. Do this while you still have Oracle support access, and check each source below.

• Support contracts. My Oracle Support lists each support contract under its Customer Support Identifier. Match every CSI to the order documents behind it.
• Database options and packs. Query DBA_FEATURE_USAGE_STATISTICS on each database to see which options and management packs show usage.
• Application users. PeopleSoft user profiles sit in PSOPRDEFN, JD Edwards in F0092, E-Business Suite in FND_USER and Siebel in S_USER. Reconcile active accounts against your licensed metric.
• Installation media and patches. Oracle Software Delivery Cloud holds the installation media for the versions you licensed. Patches, patch sets and support documents sit behind My Oracle Support, so download those before the contract ends.

Our Oracle practice builds this baseline at a fixed fee, and the wider Oracle licensing library covers each product's metrics.

Time the exit to the renewal

Serve notice against the support anniversary, with the contractual notice period counted backwards from it. A missed date usually buys another full year at 22 percent.

Choose a provider whose practice matches the record

Ask the provider how its process changed after the 2018 appeal and after the December 2024 decision. A serious provider will have a clear answer and will put it in writing.

Prepare the audit response before it arrives

Assume Oracle will open a review and have the answer ready before notice goes out. In every review we handled after an exit, the defense that worked was documentation prepared in advance. If a letter does arrive, our note on what to do when an Oracle audit letter arrives sets out the first steps.

What to do next

1. Ask the roadmap question. How long will you run this release? Under two years and the switch rarely pays.
2. Build the entitlement baseline. Contracts, orders, deployment data and the reconciliation, finished before any notice goes out.
3. Have counsel read your agreements. Product lines and eras differ on what an agent may do on your behalf.
4. Model five years. Include repricing, forfeited Support Rewards, internal engineering and the price of a return. Our software spend health check benchmarks your Oracle support line against peers.
5. Shortlist providers on fit, then negotiate. Coverage of your exact modules and versions comes first, then indemnity scope, survival, method warranty and audit cooperation, then price.
6. Time notice to the anniversary. Count the notice period backwards and put the date in the diary of two people.
7. Run the archive window. Pull every patch, media file and document you are entitled to before access ends.
8. Prepare the audit response. Assume a review, and be ready to answer it within days. The full Oracle third party support guide has the checklists.

Frequently asked questions