The 15-year legal battle between Oracle and Rimini Street fundamentally shaped the third-party software support landscape. This independent advisory provides CIOs, sourcing executives, and legal teams with the complete timeline, key rulings, strategic implications, and practical guidance for navigating support alternatives with confidence.
The Oracle vs Rimini Street case was never really about one provider. It was about whether Oracle could maintain its monopoly on support for its own products. The outcome has permanently changed the leverage equation between Oracle and its customers. Understanding this case is essential for any CIO evaluating their Oracle support strategy. For a comprehensive assessment of whether third-party support is right for your organisation, see Is Oracle Third-Party Support Legal?
Oracle, one of the world's largest enterprise software vendors, generates substantial revenue from annual support contracts, typically charging approximately 22% of licence value per year. Rimini Street emerged as a third-party support provider promising Oracle customers equivalent maintenance at roughly 50% lower cost, directly threatening this revenue stream.
In 2010, Oracle filed a lawsuit (the "Rimini I" case) accusing Rimini Street of copyright infringement and unauthorised use of Oracle's software to deliver these services. Oracle alleged that Rimini copied Oracle software code and updates beyond what customer licences permitted, effectively using Oracle's intellectual property to serve multiple clients simultaneously.
Rimini Street countered that it only used Oracle's materials within the rights of customers' licences and that it had already adjusted any processes Oracle found problematic. This conflict set the stage for a high-stakes legal showdown between software IP rights and customers' desire for cheaper, more flexible support. For context on Oracle's broader history of licensing disputes, see Oracle vs Mars Lawsuit.
| Year | Event | Detail |
|---|---|---|
| 2010 | Oracle files lawsuit ("Rimini I") | Oracle initiates suit alleging massive intellectual property theft by Rimini Street in its third-party support activities. Case filed in the U.S. District Court in Las Vegas, Nevada. |
| 2014 | Rimini II case launched | Rimini Street files for a declaratory judgment that its revised, post-2014 support processes no longer infringe Oracle's rights. Oracle countersues claiming continued violations. Rimini has by this point substantially restructured how it delivers support. |
| 2015 | Jury verdict favours Oracle | A Las Vegas jury finds Rimini Street liable for copyright infringement and awards Oracle approximately $50 million in damages, plus additional sums for other claims and legal fees totalling over $100 million. A permanent injunction is issued. |
| 2018-2019 | Appeals and Supreme Court rulings | The Ninth Circuit upholds the core finding of copyright infringement but reduces some damages. The U.S. Supreme Court limits Oracle's ability to recover certain legal fees. Crucially, 23 of Oracle's 24 original claims are overturned or dismissed. The remaining infringement deemed "innocent" (unintentional). The permanent injunction remains in effect. |
| 2021-2022 | Contempt proceedings | Oracle accuses Rimini of violating the injunction. A court finds Rimini in contempt on several technical points and orders a minor fine of approximately $630,000. Five other alleged violations are rejected, reflecting that many of Rimini's practices were within legal bounds. |
| July 2023 | Second injunction and corrective statement | A court issues a second injunction tightening restrictions on how Rimini delivers Oracle support (including banning certain automation tools) and compels Rimini Street to issue a public "corrective statement" about past marketing claims. |
| July 2025 | Settlement and end of the saga | Oracle and Rimini Street reach a confidential settlement concluding all litigation. Key terms: Oracle returns $37.8 million to Rimini Street. Rimini agrees to wind down PeopleSoft support by 2028. Both sides drop remaining claims. Neither admits wrongdoing. |
The courts confirmed that Oracle's software licences and intellectual property rights are enforceable. Third-party providers cannot copy or distribute Oracle's software or updates beyond what a customer's licence allows. Rimini Street's early practices of cloning environments and distributing Oracle updates across multiple clients were found to violate copyright law.
Critically, through appeals and the Rimini II proceedings, the legal process also validated much of Rimini Street's revised support model. By 2014, Rimini had altered its methods, working exclusively within each client's licensed software environment and no longer reusing Oracle code across customers. The courts recognised these changes. Nearly all Oracle claims beyond the early infractions were dismissed. The final judgments characterised the remaining infringement as "innocent," suggesting no wilful misconduct once processes were adjusted.
The permanent injunctions now effectively serve as operating guidelines for the entire third-party support industry.
| Injunction Requirement | What It Means in Practice | Impact on the Industry |
|---|---|---|
| Work only with legitimately licensed customers | Providers must verify that each customer holds valid Oracle licences for the software being supported. | Ensures third-party support is a complement to, not a replacement for, proper software licensing. |
| No unauthorised copying of source code | Providers cannot create generic development environments populated with Oracle software to service multiple customers. Each client's work must stay isolated. | Established the "single-customer environment" model as the legal standard. |
| No cross-client distribution of Oracle updates | Third-party providers can develop their own fixes, but cannot package and distribute Oracle's original patches broadly. | Drew a clear line between proprietary Oracle patches and independently developed workarounds. |
| Truthful marketing | Providers must not misrepresent their services or Oracle's offerings in marketing materials. | Raised the standard for transparency in how third-party support is marketed to enterprises. |
These outcomes strike a balance: Oracle's IP rights are protected, but a clear pathway remains open for third-party support firms to operate legally. The legal battle drew an explicit line between what constitutes "legal third-party support" and what crosses into infringement, providing CIOs with the clarity they need to make informed decisions.
For CIOs and sourcing professionals, the most important takeaway is that utilising third-party support for Oracle software is a legally permissible option. Despite 15 years of litigation, the outcome confirms that customers have a choice beyond Oracle's own support, provided the third-party provider respects software licence terms. See Is Oracle Third-Party Support Legal?
| Impact Area | What Changed | What It Means for CIOs |
|---|---|---|
| Third-party support confirmed legal | Despite 15 years of litigation, courts validated that third-party support is a lawful option when providers respect licence terms. | Customers have a genuine choice beyond Oracle's own support. The legal uncertainty that previously discouraged adoption has been substantially resolved. |
| Cost savings validated | Third-party support can reduce annual fees by 50% or more, extending the life of existing software investments without forced upgrades. | Enterprises must still ensure strict compliance with Oracle's licensing rules when engaging a third party. The court rulings have largely mapped out the dos and do nots. |
| Vendor relationship dynamics | Oracle typically denies access to new software updates, patches, and support once you leave its maintenance programme. Reinstating Oracle support later requires back-payment of lapsed fees. | Customers who opt for third-party support should expect a potentially strained relationship with Oracle. However, Oracle lost most claims and eventually settled, which may moderate its approach. |
| Negotiation leverage permanently changed | Knowing that third-party support is a legally validated alternative gives CIOs real leverage. Simply having a third-party option on the table yields Oracle concessions. | Enterprises can negotiate better terms with Oracle by credibly evaluating a switch. Even without switching, this leverage routinely yields 15 to 30% concessions on pricing and contract flexibility. See Contract Negotiation Service. |
| Industry-wide precedent | The Oracle vs Rimini Street precedent established that third-party support providers can survive legal scrutiny if they develop rigorous compliance processes. | Potentially encourages a more competitive market for support alternatives across all enterprise vendors, not just Oracle. See Major Third-Party Support Providers. |
One of the primary drivers behind the Oracle vs Rimini Street conflict was the promise of cost savings. Third-party support can provide significant financial relief, but there are trade-offs.
| Aspect | Oracle Premier Support | Third-Party Support |
|---|---|---|
| Annual fee | ~22% of licence cost per year (standard). | ~50% lower than Oracle's fee. Approximately 11% of licence value. |
| Annual increases | Regular uplifts of 3 to 8% per year. | Typically flat or tied to minimal inflation. Many contracts lock the rate. |
| Supported versions | Current and recent versions only. Older versions require costly extended support or are unsupported. | Supports older versions indefinitely, even after vendor end-of-support, with custom patches for tax, legal, and regulatory updates. |
| Scope of support | Standard software issues. Limited or no help with customisations or integrations. | Broader scope including bug fixes, performance tuning, and assistance for customisations. No access to Oracle's new patches, but provides workarounds and fixes. |
| Upgrades and new features | Access to new patches, updates, and upgrade rights while on support. Oracle often pushes upgrades to latest versions. | No direct access to Oracle's new patches or major upgrades. Focus is on maintaining current system. Upgrades are optional. |
| Service quality | Tiered ticket system. Can be slow for non-critical issues. No support for custom code. | Dedicated senior engineers. Often faster response times. Will troubleshoot custom code and integrations. |
| Contract flexibility | Leaving Oracle support incurs reinstatement penalties (back-support fees). Contracts often tied to all Oracle products. | Typically more flexible annual contracts. Can cover only selected systems. Easier to negotiate terms. |
| Compliance risk | None. Using vendor's own support channel. | Requires compliance diligence. Provider must follow licence rules as clarified by the legal case. Choose a reputable provider. |
A Fortune 500 company pays $5 million annually in Oracle support fees, subject to 5% annual uplifts. Five-year cost with Oracle: $5.0M + $5.25M + $5.51M + $5.79M + $6.08M = $27.63 million. Five-year cost with third-party support at 50% savings and flat rate: 5 x $2.5M = $12.5 million. Potential five-year saving: $15.13 million, freed up for innovation, cloud migration, or other strategic initiatives. See Oracle Support Costs 2026 for a comprehensive guide to reducing Oracle support spend.
| # | Recommendation | Why It Matters |
|---|---|---|
| 1 | Thoroughly review licence agreements. Before engaging a third-party provider, have licensing experts review your Oracle Master Agreement and ordering documents. Verify which environments and software copies the provider can use. | Prevents compliance exposure and ensures you and the provider clearly understand contractual boundaries. |
| 2 | Vet the provider's compliance practices. Ask how they deliver services. Do they avoid sharing Oracle code between clients? Do they follow the injunction guidelines from the Oracle vs Rimini Street case? | A reputable provider will be transparent about its compliance model. This diligence protects your organisation from inherited legal risk. |
| 3 | Secure software assets before switching. Download all relevant patches, updates, and documentation while still on Oracle support. You may lose access to Oracle's support portal after termination. | Having a repository of official updates for your current version is valuable and typically permitted for licensees. |
| 4 | Consider hybrid approaches. Maintain Oracle support for critical systems and use third-party support for stable, less-critical systems or older modules. | Balances risk and reward. Allows you to evaluate service quality before committing the full estate. See Third-Party Support for Middleware and Apps. |
| 5 | Leverage negotiation power. Use the credible option of third-party support as leverage in Oracle renewal negotiations. Oracle sales teams are often authorised to offer discounts when they know a customer is seriously evaluating alternatives. | Even if you ultimately stay with Oracle, this tactic routinely yields 15 to 30% concessions on support pricing. See Contract Negotiation Service. |
| 6 | Plan for the long term. If you switch, be prepared for Oracle to withhold upgrades. Ensure your business can operate on its current software version for an extended period and have a roadmap for eventual modernisation. | Third-party support buys time and budget, but you need a strategic exit plan, whether that is cloud migration, SaaS adoption, or a return to Oracle support. |
| 7 | Stay informed on legal developments. Although this case is settled, the landscape can evolve. Monitor new rulings, Oracle policy changes, or licence term modifications that may affect third-party support. | Oracle may revise contract language in new agreements to discourage third-party support. Proactive awareness lets you negotiate protections. |
| Step | Action | Detail |
|---|---|---|
| 1 | Assess your support needs | Inventory your Oracle-based systems and identify which are stable and can be maintained without frequent vendor updates. Older ERP modules that do not require new features are the strongest candidates for third-party support. |
| 2 | Crunch the numbers | Calculate current annual Oracle support costs including escalating uplifts and compare against third-party quotes. Factor in hidden costs of Oracle support (forced upgrades, shelfware support) versus third-party (potential one-time transition costs, future reinstatement fees if returning to Oracle). |
| 3 | Review contracts and compliance | Have your legal team review Oracle licence agreements, particularly the Oracle Master Agreement, to ensure moving to third-party support will not violate clauses or trigger unwanted consequences such as audit escalation or reinstatement penalties. |
| 4 | Engage stakeholders | Discuss the plan with application owners, the CFO for cost approval, and risk/compliance officers. Ensure everyone understands the benefits (cost savings, extended support life) and the responsibilities (maintaining compliance, relying on an alternative support channel). |
| 5 | Select and pilot a provider | Choose a reputable third-party support provider with proven Oracle expertise and compliance practices. Consider starting with a pilot on a non-mission-critical system. Monitor service quality and compliance during the pilot before migrating more critical systems. |
Yes. The Oracle vs Rimini Street legal battle confirmed that third-party support is legal as long as the provider operates within the bounds of the customer's software licence. Courts upheld Oracle's intellectual property rights but also made it clear that companies like Rimini Street can offer support services if they do not copy or share Oracle's software unlawfully. Customers can legally choose third-party support instead of Oracle's support. It is a matter of doing it the right way. See Is Oracle Third-Party Support Legal?
Both sides can claim partial victory. Oracle won early verdicts and established that some of Rimini's original methods infringed its rights. However, Rimini Street won on most claims through appeals. By 2019, only one minor infringement was upheld, labelled "innocent." In the 2025 settlement, Oracle returned $37.8 million to Rimini Street, and Rimini continues to operate with some adjustments including winding down PeopleSoft support by 2028. For customers, the takeaway is that Rimini Street survived the legal battle and third-party support remains a viable option.
It means you have options. You are not strictly bound to purchase support only from Oracle. Third-party support is a legitimate alternative, especially for older, stable systems. However, if you leave Oracle's support, you will not receive official updates or direct Oracle assistance. You will rely on the third-party for bug fixes, regulatory updates, and technical guidance. Many customers accept this trade-off for the 50% cost savings and more personalised service. The legal battle's outcome provides confidence that choosing such an alternative is not a breach of your contracts, as long as it is done properly.
Oracle cannot legally punish you for using third-party support. However, you should expect Oracle to enforce its contractual rights: once you drop Oracle support, you lose access to new patches, and rejoining later typically requires back-support fees for the lapsed period. Oracle sales representatives may strongly discourage the move. Oracle has also been known to track customers who leave and may be less inclined to offer favourable terms in other areas. Despite this, many enterprises have successfully used third-party support for years. Being careful and documenting everything minimises friction. See Oracle Audit Defence.
Pros include 50% cost savings on annual maintenance, more responsive service with dedicated senior engineers, ability to run stable software longer without forced upgrades, and support for customisations that Oracle typically declines. Cons include no new product updates or enhancements from Oracle (you essentially freeze your software version aside from necessary regulatory patches the third party provides), dependency on the provider's expertise for complex issues, and ongoing compliance responsibility to ensure licence rules are followed. Third-party support is best suited for stable, mission-critical systems where cost savings and extended longevity outweigh the need for the latest features. See Transitioning to Oracle Third-Party Support: A CIO's Guide.
As part of the 2025 settlement, Rimini Street agreed to wind down its support for Oracle's PeopleSoft product line by 2028. This was a concession to Oracle as part of the broader resolution. However, Rimini Street continues to provide support for many other Oracle products, including Oracle Database, E-Business Suite, JD Edwards, and Siebel. If your organisation uses PeopleSoft and currently relies on Rimini Street, you should plan for either returning to Oracle support or identifying an alternative provider by the 2028 deadline.
Absolutely, and this is one of the most effective strategies we see. Simply having a credible third-party support evaluation on the table changes the dynamic with Oracle. Oracle sales teams are authorised to offer discounts of 15 to 30% (sometimes more) on support renewals when they know a customer has a genuine alternative. The key is making the evaluation credible: obtain formal quotes from providers, involve procurement leadership, and communicate the timeline clearly. Even if you ultimately stay with Oracle, the savings from this leverage alone can be substantial. See Oracle Contract Negotiation Service.
Oracle typically responds with a combination of fear-based messaging (implying legal risks, security vulnerabilities, or loss of IP rights), retention offers (discounts, bundled cloud credits, or flexible upgrade terms), and contractual enforcement (emphasising reinstatement fees). The best approach is to remain fact-based. The legal risks have been largely resolved by the Oracle vs Rimini Street case. Security can be managed through third-party patches and your own controls. Oracle cannot terminate your perpetual licences for choosing a different support provider. Having an independent advisory firm manage the process ensures your team can evaluate options objectively, without vendor pressure influencing the decision.
Our independent advisory team helps enterprises assess, negotiate, and transition to third-party support, or use the option as leverage for better Oracle terms. We work exclusively in your interest, never for the vendor.
Third-Party Support AdvisoryIndependent assessment, provider evaluation, transition planning, and Oracle negotiation leverage. Fixed-fee engagements. No vendor conflicts.