Rimini Street Oracle Support: The Complete Independent Guide for 2026

Rimini Street: Company Background and Market Position

Rimini Street was founded in 2005 by Seth Ravin, who had previously built a similar model at TomorrowNow (later acquired by SAP). Ravin's insight was that Oracle's legacy on-premises applications — PeopleSoft, JD Edwards, Siebel — were in long-term maintenance mode for most customers, and that Oracle's 22% annual support charge with an 8% annual uplift was significantly above the cost of the actual support delivered. Rimini Street offered to provide equivalent or better support at approximately 50% of Oracle's fee, with flat-rate renewals.

The model proved durable. By 2026, Rimini Street supports thousands of enterprise clients across 180+ countries and has generated cumulative savings of billions of dollars for clients relative to Oracle's standard support pricing. Despite a long-running legal dispute with Oracle that began in 2010, Rimini Street's core business has grown consistently, reflecting genuine market demand for an alternative to Oracle's support model.

What Rimini Street Covers: Product Scope in 2026

Rimini Street's Oracle support coverage as of 2026 spans the following product families.

Oracle Database

Rimini Street supports Oracle Database across all major versions in active enterprise use, including Oracle 12c, 18c, 19c, and earlier versions. Database support includes break-fix for production issues, performance tuning assistance, security guidance and virtual patching for known CVEs, and interoperability support for operating system and middleware upgrades. Rimini Street does not provide Oracle-issued quarterly security patches — instead, it delivers Rimini Protect, a security-focused service that addresses vulnerabilities through compensating controls, configuration hardening, and custom patches developed by Rimini's security team.

For organisations running Oracle Database on stable versions with no plans to upgrade, Rimini Street's Database support is typically a strong fit. The version freeze limitation — inability to upgrade to the next major Oracle Database release while on TPS — is relevant only if a version upgrade is planned. For environments running Oracle 19c (Oracle's long-term release), which has extended Premier Support through 2027 and extended coverage thereafter, the version freeze question becomes less urgent.

Oracle E-Business Suite

Oracle EBS is one of Rimini Street's most established product support areas. Rimini supports EBS R11i and R12 across all modules — Financials, Supply Chain, HCM, Manufacturing, Projects, and CRM. Custom code support is included in Rimini Street's standard EBS contract, which is a significant differentiator versus Oracle Premier Support, which does not cover customer-developed customisations. Rimini's EBS engineers are typically senior-level practitioners with deep module-specific expertise built through years of supporting complex, multi-country EBS implementations.

The EBS version freeze is the principal trade-off. Rimini Street EBS support does not include access to Oracle-issued patches, ATG rollup patches, or EBS Technology Coexistence patches that allow EBS to run on newer Oracle Database or JDK versions. For organisations running EBS 12.2 with no plans to upgrade to EBS 12.2.x minor releases or a hypothetical EBS 13, this is typically manageable. The critical question is whether any planned integration with Oracle Fusion Cloud modules — Oracle HCM Cloud, Oracle Cloud Financials — requires a specific EBS patch level, which would preclude TPS for the integration period.

JD Edwards EnterpriseOne and World

JD Edwards is one of Rimini Street's historically strongest product lines. Rimini has supported JDE since its earliest days and has deep expertise across both EnterpriseOne (on Oracle Database and IBM i) and JD Edwards World (IBM i only). Support covers manufacturing, distribution, financial management, asset management, and real estate modules. Custom code and integration support is included. For JDE environments stable on EnterpriseOne 9.0, 9.1, or 9.2, Rimini Street's JDE support delivers the TPS value proposition with minimal transition risk.

Siebel CRM

Siebel CRM represents the clearest long-tail TPS case in Oracle's application portfolio. Oracle acquired Siebel in 2006 and the product has operated in a maintenance mode since the early 2010s. Rimini Street's Siebel support covers all active Siebel versions including Siebel 8.1, 8.2, and IP releases, including support for Siebel Open UI implementations. For organisations committed to running Siebel for five to ten more years, Rimini Street's TPS delivers savings at Oracle's 8% annual uplift rate that compound into substantial cumulative reductions over the support lifecycle.

Oracle Hyperion

Rimini Street supports Oracle Hyperion products including Hyperion Financial Management (HFM), Hyperion Planning, Hyperion Essbase, and Financial Data Quality Management. Hyperion is a common TPS scenario because many organisations have invested heavily in Hyperion customisations and consolidation configurations that make migration to Oracle EPM Cloud complex and expensive. Rimini's Hyperion support allows organisations to extend the life of their Hyperion investment while evaluating cloud alternatives at their own pace rather than on Oracle's upgrade timeline.

Oracle Fusion Middleware

Rimini Street's Fusion Middleware support covers Oracle WebLogic Server, Oracle SOA Suite, Oracle Service Bus, Oracle Forms and Reports, Oracle ADF, and Oracle Identity and Access Management components. See the related article on Oracle third-party support for middleware and applications for detailed coverage guidance on this product family.

Oracle Retail

Rimini Street is one of few TPS providers offering Oracle Retail support, covering Oracle Retail Merchandising System (RMS), Oracle Retail Sales Audit, Oracle Retail Invoice Matching, and related Retail suite components. This coverage is valuable for retail organisations with substantial Oracle Retail implementations not scheduled for migration to Oracle Retail Cloud.

PeopleSoft: Wind-Down by July 2028

The most significant coverage change in Rimini Street's 2025 and 2026 portfolio is the announced wind-down of Oracle PeopleSoft support. In connection with the July 2025 settlement of the Oracle v. Rimini Street litigation, Rimini committed to completing its PeopleSoft support wind-down by July 31, 2028. Organisations currently on Rimini Street PeopleSoft support should plan for this transition. Options include migrating to Spinnaker Support (which has no announced PeopleSoft wind-down), transitioning to Oracle Premier Support, or using the wind-down period to accelerate a PeopleSoft to Oracle HCM Cloud or Workday migration.

Rimini Street Pricing Model

Rimini Street does not publish list prices, and pricing is negotiated based on the specific Oracle products in scope, the licence value basis for the support fee calculation, and the contract term. The general principle is that Rimini Street's annual fee will be approximately 50% of Oracle's annual support fee for the same scope. Oracle's annual support fee is itself calculated at 22% of the net licence value with an 8% annual uplift applied each year.

Rimini Street's contracts typically run for one, two, or three years with an option to extend. Annual escalators, if any, are substantially below Oracle's 8% uplift and are frequently zero for multi-year contract terms. This means the savings gap between Oracle and Rimini Street widens each year of the contract, as Oracle's fee base continues to compound at 8% while Rimini's fee base remains flat.

A representative example: an organisation paying Oracle 1,000,000 USD annually in Database and EBS support would pay approximately 500,000 USD to Rimini Street for the same scope. In year three, Oracle's fee would have grown to approximately 1,166,400 USD (three years of 8% uplift), while Rimini's fee (assuming zero escalation) would remain at 500,000 USD. The three-year cumulative saving approaches 1,000,000 USD on a 1,000,000 USD starting Oracle support base.

Rimini Street Service Model: What You Get

Dedicated Senior Engineer Model

Rimini Street assigns a dedicated senior engineer as the primary support contact for each client. This engineer develops familiarity with the client's specific Oracle environment — versions, customisations, integrations, and historical issue patterns — over the life of the support engagement. The dedicated engineer model contrasts with Oracle's My Oracle Support model, where support is delivered through a tiered ticketing system with rotating analysts who have no client-specific context.

Rimini Street publishes response time commitments of under two minutes for Priority 1 and Priority 2 issues, achieved by routing P1/P2 tickets directly to the dedicated engineer or escalation pool rather than through a general queue. For organisations where Oracle application downtime has a direct financial impact, this response time commitment is a significant operational consideration.

Custom Code Support

Oracle Premier Support does not cover customer-developed customisations to Oracle applications. Rimini Street includes custom code support in its standard contract, covering diagnosis, bug fixes, and performance remediation for customer-developed PLSQL, Java extensions, Oracle Forms customisations, and integration code. For heavily customised EBS, JD Edwards, or PeopleSoft environments — which describes the majority of large Oracle application customers — this inclusion removes a material operational gap that exists under Oracle Premier Support.

Rimini Protect: Security Services

Rimini Protect is Rimini Street's security-focused service layer, available as a standalone or bundled with support contracts. Rimini Protect addresses the principal TPS security concern — the absence of Oracle-issued quarterly CPU security patches — through a combination of virtual patching (deploying compensating controls at the network, application, or database layer to mitigate known CVEs without applying Oracle patches), configuration hardening assessments, and security advisory services. Oracle's quarterly Critical Patch Updates are the primary security maintenance mechanism for Oracle on-premises software, and understanding how Rimini Protect addresses the CVEs in each CPU is an important part of the TPS security evaluation.

Rimini Manage: Managed Services

Rimini Manage extends Rimini Street's offering beyond pure break-fix support into application management services — proactive monitoring, release management, performance management, and functional administration support. For organisations looking to reduce internal Oracle application management headcount alongside support cost reduction, Rimini Manage provides a pathway to outsource a larger portion of the Oracle application operations function to Rimini Street.

The 2025 Oracle v. Rimini Street Settlement: What It Means

The legal relationship between Oracle and Rimini Street was one of the most consequential in enterprise software over the past fifteen years. Oracle first sued Rimini Street in 2010, alleging copyright infringement based on Rimini Street's practice of downloading Oracle support materials from My Oracle Support to support Rimini's clients. Oracle won a trial verdict in 2015 and ultimately obtained approximately 90 million USD in damages, fees, and costs through subsequent proceedings.

However, in December 2024, the Ninth Circuit Court of Appeals issued a landmark ruling that vacated all material copyright findings against Rimini Street, reversed the Lanham Act judgment, and set aside the injunction that had constrained Rimini Street's support methodology. This ruling significantly strengthened Rimini Street's position and set the stage for the July 2025 settlement.

The July 2025 settlement terms: Oracle agreed to return approximately 37.8 million USD to Rimini Street from the attorneys' fees and costs previously paid. Neither party admitted liability or wrongdoing. The settlement included no blanket prohibition on Rimini Street's Oracle support business. The one material operational commitment was Rimini Street's agreement to complete the wind-down of PeopleSoft support by July 31, 2028 — a wind-down that Rimini had announced before the settlement.

For enterprise IT and procurement teams evaluating Rimini Street in 2026, the practical implications are clear: the principal legal uncertainty that complicated Rimini Street evaluations for the prior decade has been resolved. Rimini Street's Oracle support services (excluding the PeopleSoft wind-down) are not subject to any active injunction or legal proceeding. The settlement does not prevent Rimini Street from continuing to develop and deliver its TPS model for Database, EBS, JD Edwards, Siebel, Hyperion, Middleware, and Oracle Retail products.

When Rimini Street Is the Right Choice

Rimini Street is typically the right choice when an organisation has a large, diverse Oracle portfolio spanning multiple product families, requires a single TPS partner with deep coverage breadth, has significant custom code across Oracle applications that benefits from Rimini's included custom code support, operates in multiple geographies requiring 24x7x365 global support coverage, and is interested in managed services capability beyond pure break-fix support.

The combination of breadth, scale, dedicated senior engineering, custom code support, and the security-focused Rimini Protect layer positions Rimini Street as the strongest overall TPS offering for large enterprise Oracle environments — subject to the PeopleSoft caveat.

When Rimini Street Is Not the Right Choice

Rimini Street is not the right choice if PeopleSoft is a core part of your Oracle TPS requirement and you need coverage certainty beyond July 2028. Spinnaker Support is the appropriate alternative for long-term PeopleSoft TPS. Rimini Street is also potentially not the right choice if your organisation has strict IP compliance requirements that make Rimini Street's historical litigation a disqualifying factor — in that scenario, Spinnaker's stricter IP protocols and absence of litigation history may be determinative. For mid-market organisations with focused Oracle Database and EBS requirements, Support Revolution's cost advantage and simplicity may outweigh Rimini Street's broader capabilities.

Practical Evaluation Steps: Assessing Rimini Street for Your Environment

The following steps should be completed before contracting with Rimini Street or any Oracle TPS provider.

Step 1: Complete a Licence Compliance Review

Before transitioning any Oracle product to TPS, conduct an internal licence compliance review. Identify any licence gaps that Oracle could use as an audit claim after the support transition. Oracle is more likely to initiate a licence audit against customers who exit support, and unresolved compliance issues create financial exposure that can negate TPS savings. A clean licence position before transition is non-negotiable.

Step 2: Confirm Version and Configuration Coverage

Request a formal Statement of Work (SOW) from Rimini Street that explicitly lists every Oracle product version and patch level in scope. Do not assume that general product coverage includes your specific version and configuration. The SOW should specify Rimini's coverage scope, exclusions, and the methodology for delivering security patching for your Oracle versions. Compare the Rimini Protect security approach against the actual CVEs in Oracle's most recent Critical Patch Updates to assess the adequacy of the security coverage for your environment's risk profile.

Step 3: Map Integration Dependencies

Identify every Oracle product that integrates with the products being transitioned to Rimini Street. If Oracle EBS integrates with Oracle Database, and Oracle Database integrates with Oracle Middleware, transitioning each to TPS independently creates potential support gap questions at the integration boundaries. Map the dependencies and confirm with Rimini Street how integration-layer issues are handled when the support boundary crosses product lines.

Step 4: Check ULA and PULA Status

If your Oracle licences are governed by an active Unlimited Licence Agreement (ULA) or Perpetual ULA (PULA), do not transition to TPS before certifying the agreement. Certify the ULA first to crystallise your licence entitlements, then evaluate TPS for the resulting certified licence position. Transitioning during an active ULA creates compliance and commercial risks that are difficult to unwind. Oracle's CSI (Customer Support Identifier) structure must also be reviewed to ensure that TPS transition is executed in a way that does not inadvertently create compliance gaps through CSI restructuring.

Step 5: Structure the Contract Carefully

Review the Rimini Street contract against the following key provisions: scope definition (explicit list of Oracle products, versions, and configurations covered), custom code coverage scope, security support methodology, SLA response time commitments and remedies, annual escalator terms, contract term and renewal provisions, termination rights and notice periods, and indemnification provisions related to IP claims. Engage legal counsel for the IP indemnification review — understanding how Rimini Street's contract allocates IP liability is important given the company's litigation history, even after the 2025 settlement.

The Oracle TPS Decision Framework provides a systematic five-dimension scoring approach for evaluating Rimini Street against your specific Oracle environment. For independent advisory support on Rimini Street evaluation, contract negotiation, or TPS transition management, contact the Redress Compliance Oracle team. We have no commercial relationship with Rimini Street or any TPS provider and provide evaluation services based solely on your organisation's interests.