The Real Cost of Rimini Street: What JDE Customers Discover After Year 3

Rimini Street, Inc. (Nasdaq: RMNI) was founded in 2005 and has built a defensible, real business around a single insight: Oracle's annual software maintenance fees — charged at approximately 22% of original license cost — represent one of enterprise IT's most persistent margin extractions. By replacing that relationship with third-party support at roughly half the cost, Rimini Street has served more than 3,100 active clients and generated $421.5 million in revenue in fiscal year 2025.

For JDE customers on Oracle EnterpriseOne 9.2, the Rimini value proposition is specific and genuine:

• Replace Oracle's annual maintenance fee with Rimini Support™ at approximately 50% of Oracle's fee
• Receive tax, legal, and regulatory (TLR) updates delivered by Rimini's engineers rather than Oracle's
• Get break/fix support, custom code support, and interoperability guidance for your existing JDE version
• Remove the implicit Oracle upgrade mandate — Rimini commits to supporting your current release for up to 15+ years
• Access Rimini Protect™ for security coverage that works around (rather than through) Oracle source code

The pitch lands. For organizations whose primary pain is Oracle's support bill or the pressure to upgrade on Oracle's timeline, Rimini Street solves a real problem at real savings. Their 4.9/5.0 average client satisfaction score, validated by Gartner Peer Insights and multiple Stevie Awards including Best Use of AI in Customer Service (2026), reflects genuine service delivery capability.

The question this article examines is different: What does the total picture look like after Year 1, Year 2, and Year 3? What costs are not visible in the Rimini contract? What capabilities does a JDE customer lose permanently — or expensively reclaim? And is there a third option that neither Oracle nor Rimini Street is motivated to describe?

Rimini Street's economics are straightforward. Oracle charges enterprise software maintenance at approximately 22% of original license fee per year — a fee that Oracle has raised annually and that carries a reported 90%+ profit margin. Rimini Street charges approximately 50% of whatever Oracle charges, delivering the margin difference through engineer-intensive support operations rather than through software development or IP investment.

This model has two structural properties JDE customers need to understand:

1. Rimini cannot give you what Oracle builds. Rimini Street does not have access to Oracle's source code. Their security solutions (Rimini Protect™) work through virtual patching, configuration hardening, and behavioral monitoring rather than through patching the underlying code. This works — and for many CVEs it provides faster response than Oracle's own patch cycle — but it is categorically different from vendor patches.

2. Rimini's business is stable but not growing. Full-year 2025 revenue was $421.5 million — a 1.7% decrease from 2024's $428.8 million. Annualized Recurring Revenue (ARR) was $411.4 million, a 0.8% decline year-over-year. Revenue Retention Rate was 88% in both 2024 and 2025 — meaning approximately 12% of subscription revenue does not renew annually.

3. PeopleSoft is now exiting. Rimini Street announced in July 2024 that it would wind down all Oracle PeopleSoft support, generating approximately $30 million in annual revenue (about 7% of total). The July 2025 settlement with Oracle codified this wind-down deadline as July 31, 2028. For JDE customers, this is a data point about how product-line decisions get made at Rimini — and a reminder that third-party support relationships can change.

No conversation about Rimini Street is complete without the litigation record. This is not a competitive smear — it is a material business consideration for any organization signing a multi-year support contract with a vendor whose legal history directly shapes how it can and cannot provide service.

The Timeline

January 2010: Oracle sues Rimini Street in the District of Nevada for copyright infringement, alleging Rimini used automated tools to mass-download Oracle software and support materials — including JD Edwards, PeopleSoft, and Siebel products — far in excess of customer license authorizations.

October 2015: After a five-year civil trial, a jury awards Oracle $35.6 million in copyright infringement damages and $14.4 million in computer fraud damages. With attorneys' fees, costs, and interest, the total reaches $124 million. A permanent injunction is issued.

September 2016: Oracle is awarded an additional $46.2 million in legal fees. Rimini Street pays a total of approximately $90 million after a partial reversal of some claims by the Ninth Circuit in 2018–2019.

January 2022: The Court finds Rimini Street in contempt of the 2018 injunction on five issues — ordered to pay $630,000 plus Oracle's legal costs.

September 2024: In the "Rimini II" case (filed 2014), the District Court awards Oracle $58.5 million in attorneys' fees and costs — subsequently vacated in June 2025 following a Ninth Circuit remand.

July 7, 2025: Oracle and Rimini Street announce a confidential settlement resolving Rimini II. Oracle returns approximately $37.8 million to Rimini Street, while retaining approximately $22.5 million. Rimini Street agrees to complete its PeopleSoft wind-down by July 31, 2028. Neither party admits liability.

Rimini Street's contract delivers on its stated promise. The Year 1 savings are real. For a JDE customer paying Oracle $1 million per year in maintenance, the 50% reduction frees $500,000 annually. Over three years, that is $1.5 million in avoided Oracle fees. Here is what accumulates on the other side of the ledger.

Cost Bucket 1: Technical Debt from Deferred ESUs and ASUs

Oracle delivers JDE EnterpriseOne updates through Electronic Software Updates (ESUs) and Automated Software Updates (ASUs), typically multiple times per year. When an organization moves to Rimini Street, it stops applying Oracle's update stack. Over three to five years, the gap between an organization's JDE environment and Oracle's current update state widens. If the organization ever needs to return to Oracle support, upgrade to a future JDE release, pass an Oracle audit, or integrate Oracle-native AI or cloud features — it must first remediate that gap at substantial cost.

Cost Bucket 2: Locked Out of Oracle's JDE Innovation Roadmap

JDE E1 9.2 is not a static platform. Oracle has delivered continuous updates through 25 releases since the 2015 GA date — including Orchestrator enhancements, AI/ML integrations, UX One capabilities, and cloud infrastructure services. Premier Support extends through at least December 2037. If the organization plans to deploy JDE Orchestrator, leverage Oracle's AI extensions, integrate with Oracle Cloud Infrastructure, or participate in Oracle co-innovation programs — these capabilities require Oracle support status. Rimini customers are locked out.

Cost Bucket 3: Return-to-Oracle Complexity

Industry data shows that third-party support customers average 4.3 years before returning to vendor support. When they do, organizations must inventory and re-apply deferred patches/ESUs, confirm license compliance (Oracle may audit at re-entry), reconcile Rimini-applied customizations against Oracle's current code baseline, and potentially renegotiate Oracle support terms under current pricing. The technical remediation cost can be substantial depending on how wide the update gap has grown.

Cost Bucket 4: Security — The Patch Gap Risk

Rimini Protect™ is a genuine security product with demonstrated real-world effectiveness. However, the fundamental constraint is structural: Rimini does not have Oracle's source code and cannot issue patches for Oracle JDE core application vulnerabilities the way Oracle can. For regulated industries — manufacturing with export compliance, food & beverage with FDA traceability, government contractors with CMMC requirements — this assessment burden has material compliance and audit implications.

Cost Bucket 5: IT Team Capacity — The Invisible Non-Saving

This is the cost bucket that Rimini Street's economics never address — because it is not a Rimini Street problem. When an organization switches to Rimini Street, the Oracle support relationship changes. The team's operational workload does not. Every help desk ticket, every environment issue, every access request, every batch job failure, every integration monitoring task — all of it remains with the internal IT team. The 35–45% of IT capacity consumed by unplanned work before Rimini is the same 35–45% consumed after Rimini.

The standard Rimini Street TCO argument compares only two variables: Oracle's annual maintenance fee vs. Rimini's annual fee. This framing omits the operational cost of running JDE — which consistently exceeds software support fees as a proportion of total JDE TCO.

The following three-path comparison uses normalized assumptions based on a mid-market JDE customer paying $800,000 annually in Oracle maintenance.

The decision to move from Oracle direct support to Rimini Street involves risk categories that go beyond vendor satisfaction scores. The matrix below rates each risk dimension across three scenarios.

JDE is a unique ERP context. It has a highly customized implementation profile — most JDE environments are extensively modified, making the "custom code support" benefit of Rimini Street more material than it would be for an out-of-box deployment.

Where Rimini Street Works Well for JDE

• Organizations on JDE EnterpriseOne 9.1 or older facing Oracle's effective end of support can extend their environment's life without a mandatory upgrade to 9.2
• Organizations with heavy JDE customization who find Oracle's support of modified code inadequate
• Organizations where the primary constraint is Oracle's 22% annual maintenance fee and there is no near-term plan to deploy new JDE modules
• Organizations that want to exit the Oracle upgrade treadmill and redirect budget to other IT priorities

Where Rimini Street Creates Risk for JDE

• JDE World A9.4 customers: Oracle's Premier Support ended April 2022, transitioning to Sustaining Support in April 2025. If you are on World A9.4 with Rimini, you are dependent entirely on Rimini's own update development capability with no Oracle backstop.
• Organizations planning JDE Orchestrator expansion: Rimini's model freezes your environment at its current state. Orchestrator capabilities in Release 24 and Release 25 require Oracle-supported 9.2 environments.
• Organizations in regulated manufacturing: EDI, serialization, lot traceability, and compliance reporting modules receive Oracle-level updates through ESUs that Rimini cannot replicate at the source-code level.
• Organizations considering Oracle Fusion migration: If Fusion is on your 3–5 year horizon, the JDE-to-Fusion migration tooling and support resources are only available through Oracle support status.

There is a conversation that neither Oracle nor Rimini Street is motivated to have with JDE customers. Oracle wants to sell you support plus future upgrades to Oracle Fusion. Rimini Street wants to sell you a support contract at half Oracle's price. Neither of them is asking: After we change your support vendor, does your IT team have the capacity to execute the roadmap?

The answer, consistently, is no.

Across 27 years and 150+ organizations, Allari has found that the primary constraint for most JDE IT leaders is not which vendor holds the support contract. It is that 35–45% of IT execution capacity is consumed by unplanned operational work — help desk escalations, access requests, environment failures, integration firefights — before the team can begin any planned work.

This is a different problem than Rimini Street solves. Rimini Street changes the support vendor relationship. Allari's Embedded Outcome Teams™ absorb the operational workload — all L1–L4 support, monitoring, IAM, application management, environment management — from inside your IT function. Not as a helpdesk overlay. As embedded operational custody with shared outcome ownership and forensic-grade transparency through OpenBook™.

The two models are not mutually exclusive. An organization can use Rimini Street to reduce Oracle support costs while using Allari to recover the operational capacity of the team. These interventions operate at different layers of the stack.

Before choosing between Oracle direct support and Rimini Street, the right diagnostic question is not "which vendor is cheaper?" — it is "what is my actual constraint?"

If your primary constraint is Oracle support cost or upgrade pressure: Rimini Street solves that problem directly. The 50% fee savings are real and verified. The <2-minute P1/P2 response SLA consistently outperforms Oracle's support portal. If you are paying Oracle $1M+ per year and see no roadmap value in Oracle's JDE updates, the Rimini value proposition is sound.

If your primary constraint is IT team capacity: Rimini Street does not address that problem. If roadmap work is consistently deferred because the team cannot get ahead of operational volume — if your JDE administrators are spending 60–70% of their week on unplanned work — the constraint is operational architecture, not software vendor selection.

If both constraints are present: The two solutions are stackable. Use Rimini Street for support cost reduction. Use Allari for operational capacity recovery. The interventions are at different layers and are not in conflict.

Related Reading