Oracle vs Rimini Street: Support Comparison, Legal Battle, and What It Means for Your Enterprise

The Oracle Support Problem That Created Rimini Street

Oracle charges annual support at 22% of the original licence fee, with fees increasing by 8% per year. For a large enterprise with $50 million in Oracle licence investment, year-one support costs $11 million. In year five, those same support fees reach approximately $15 million — for the same software, the same customisations, and often the same version that was deployed at the start. Year ten support reaches approximately $21 million.

This escalating cost trajectory, combined with widespread enterprise frustration about Oracle support quality — slow response times, generic documentation-based answers, and a perceived lack of focus on individual customer issues — created the market opportunity that Rimini Street was built to exploit.

Rimini Street launched in 2005 with a simple proposition: provide enterprise-grade Oracle support for approximately half what Oracle charges, with better response times, more personalised service, and support for older software versions that Oracle had moved to limited or extended support. For many enterprises, particularly those not planning to upgrade their Oracle applications in the near term, it was a compelling offer.

How Oracle Support and Rimini Street Support Differ

Understanding the substantive differences between Oracle support and Rimini Street support is essential for making an informed decision. They are not equivalent services — each has meaningful advantages and genuine limitations.

Oracle's Official Support: Strengths and Weaknesses

Oracle's support model provides access to the full breadth of Oracle's development organisation. The key advantages are access to official security patches and critical patch updates (CPUs), new version access and upgrade entitlement, official product roadmap information, and the contractual assurance of Oracle's Lifetime Support Policy which guarantees Premier Support for defined periods.

The practical weaknesses are well-documented among enterprise customers. Support is frequently handled by junior staff who rely on the same online documentation that customers can access themselves. Response times for all but the most critical issues are often measured in days rather than hours. Oracle's support model is also volume-oriented — a customer paying $500,000 annually often receives a similar quality of support interaction to one paying $5 million.

Rimini Street's Model: What You Get and What You Don't

Rimini Street's model assigns named senior engineers to each customer account, with typical response times under two minutes for critical P1 and P2 issues. Its support covers custom code and modifications — an area where Oracle support provides no assistance at all. For enterprises with heavily customised Oracle EBS, PeopleSoft, JD Edwards, or Siebel deployments, this coverage of custom code support is a significant differentiator.

What Rimini Street cannot provide is access to Oracle's official new patches, critical patch updates, or future Oracle product versions. Rimini develops its own updates for customer environments, addressing security vulnerabilities through its own analysis and patching methodology rather than applying Oracle's official patches. This approach works well in practice for many organisations — Rimini's security updates have been independently validated in numerous customer environments — but it creates a philosophical and contractual difference from official Oracle patching that some regulated industries or security-sensitive organisations find difficult to accept.

The 15-Year Legal Battle: What Happened and Why It Matters

Oracle sued Rimini Street for copyright infringement in 2010, alleging that Rimini had improperly copied Oracle's software and support materials to provide its services. The litigation wound through US courts for fifteen years, resulting in multiple verdicts, appeals, and counter-appeals that established important precedents for the third-party support industry.

Oracle won multiple rounds in the litigation, establishing that certain of Rimini Street's original support practices — specifically the automated bulk downloading of Oracle's support materials — constituted copyright infringement. Rimini paid damages and attorney's fees over the course of the litigation and changed its service delivery practices to comply with copyright law.

The critical legal conclusion from the full litigation history is that third-party Oracle support is legal when delivered within copyright law boundaries. Rimini's core model — using customers' own licensed materials to provide support services on those customers' behalf — was upheld as legitimate. Only the specific practices involving unauthorised copying were found to be infringing.

The 2025 Settlement and PeopleSoft Wind-Down

In July 2025, Oracle and Rimini Street reached a confidential settlement ending the final outstanding litigation. As part of the settlement terms, Oracle returned $37.8 million to Rimini Street (a portion of fees Rimini had previously paid Oracle under earlier judgments), and Rimini Street agreed to wind down all support for Oracle PeopleSoft products by 31 July 2028.

The PeopleSoft wind-down is the most significant practical consequence of the settlement for enterprise customers. Organisations that moved to Rimini Street for PeopleSoft support must now make a decision: return to Oracle support before 2028, migrate to another third-party support provider, or accelerate their PeopleSoft modernisation or replacement project.

Rimini Street is required to notify all affected PeopleSoft customers about the wind-down, provide quarterly progress reports to Oracle, and issue a public statement confirming completion when the wind-down is finalised. Customers should already have received notification if they are on Rimini Street PeopleSoft support.

Financial Comparison: Oracle Support vs Third-Party Support

The financial case for third-party Oracle support depends significantly on the specific product, version, and contract terms. However, the general comparison is consistent across large enterprise deployments.

Oracle charges 22% of the perpetual licence fee annually, with 8% annual increases. For an Oracle Database Enterprise Edition deployment with $10 million in licence value, year-one support costs $2.2 million. Year two: $2.38 million. Year five: $3.04 million. Over five years, cumulative Oracle support payments on this deployment exceed $12.2 million.

Rimini Street typically charges approximately 50% of Oracle's then-current support rate, often with flat or low-rate fee escalation. Using the same example, year-one Rimini support would be approximately $1.1 million, with year-five costs potentially still near the year-one figure if fees are flat. Five-year cumulative savings versus Oracle support can exceed $5 million on this single deployment.

The magnitude of savings explains why Rimini Street achieved significant enterprise adoption. For organisations with large Oracle Application footprints — EBS, PeopleSoft, JD Edwards, Siebel — that are not actively planning Oracle upgrades, the five-year savings are substantial enough to fund significant technology investment elsewhere.

When Third-Party Oracle Support Makes Sense

Third-party Oracle support is not appropriate for every situation. The decision depends on your Oracle software roadmap, regulatory environment, and operational requirements. The circumstances where third-party support tends to generate the highest value without unacceptable risk are:

• Stable legacy application deployments: Enterprises running Oracle EBS, JD Edwards, or Siebel with no near-term plan to upgrade to Oracle Fusion Cloud applications are strong candidates. The official patches Oracle provides for mature versions add marginal security value compared to the third-party alternatives.
• Heavily customised environments: Organisations with extensive Oracle customisations that Oracle's own support does not cover can gain materially from Rimini's custom code support coverage.
• Oracle support cost reduction negotiations: Even if you ultimately remain on Oracle support, the existence of Rimini Street as a credible alternative provides negotiating leverage. Oracle has offered meaningful support discounts to enterprises that credibly demonstrate they are evaluating third-party alternatives.
• Long support lifetimes for database technology: Oracle Database customers running stable versions who have no near-term cloud migration plans can often move to third-party support for database support costs without meaningful risk.

When to Stay with Oracle Support

There are situations where remaining on Oracle's official support is clearly the right choice. Organisations that are actively migrating to Oracle Fusion Cloud applications need to maintain Oracle support to access upgrade paths and new version entitlements. Oracle Cloud applications (SaaS) include support in the subscription fee and the third-party support model does not apply.

Highly regulated industries — financial services, healthcare, government — that have specific regulatory requirements for vendor-backed security patching may face compliance difficulties if they move to third-party support. The question of whether Rimini's security updates satisfy applicable regulatory requirements needs specific legal review rather than a general assumption.

And now, for PeopleSoft specifically, the 2025 settlement creates a clear constraint: Rimini Street support for PeopleSoft ends by 2028. Organisations currently on Rimini Street for PeopleSoft need to either plan their transition back to Oracle support or accelerate their PeopleSoft replacement timeline.

What Enterprises Should Do Now

The Oracle vs Rimini Street landscape in 2026 is more complex than it was before the 2025 settlement. PeopleSoft customers on Rimini support have a clear deadline. Other Oracle application customers face an ongoing decision about whether the cost savings justify the service and patch differences.

The most effective approach is a structured evaluation that considers: the five-year cost trajectory under Oracle support vs third-party alternatives, your Oracle software roadmap and cloud migration timeline, your industry's regulatory requirements for patch provenance, and your organisation's actual utilisation of Oracle support services today. Many enterprises paying Oracle annual support fees receive very few Oracle support engagements per year — in those cases, the cost-benefit of third-party support is particularly compelling.

Redress Compliance provides independent analysis of Oracle support alternatives — including Rimini Street, Spinnaker Support, Support Revolution, and others — without commercial relationships with any third-party support provider. Our assessment focuses on total cost of ownership, contractual risk, and strategic fit with your Oracle roadmap.