Oracle PeopleSoft Support by Third Party: Costs, Risks, and Alternatives

The Oracle PeopleSoft Support Cost Crisis

Oracle's PeopleSoft support model is built on annual escalation. The vendor charges 22 percent of net licence fees per year for maintenance and support. Unlike many enterprise vendors that escalate support at 3 to 4 percent annually, Oracle PeopleSoft support increases at 8 percent per year—compounding directly into your budget.

Consider an organisation with $1 million in PeopleSoft licences. Year 1 support cost is $220,000. By year 5, that same support has grown to $323,000—a 47 percent increase for the exact same licences. By year 10, support costs reach $476,000. At this point, you are paying more in annual support for licences you already own than you did for the original licence acquisition.

This cost escalation is not discretionary. It is a mandatory condition of Oracle support contracts. Organisations cannot negotiate the 8 percent escalation rate. Organisations cannot cap support cost increases. The only choice is to continue paying or exit Oracle support entirely and absorb the exit costs and risks.

What Oracle PeopleSoft Support Actually Covers

Before evaluating third-party alternatives, you must understand what you are paying for. Oracle PeopleSoft support provides five distinct benefits: bug fixes delivered through PeopleSoft Update Manager (PUM), tax and regulatory updates (critical for Payroll modules), security patches for vulnerabilities, cumulative feature bundles (CFBs) and feature packs that enhance capability, and access to My Oracle Support (MOS) portal to create and track service requests.

The PUM patches are granular fixes to known issues. Tax updates are the most business-critical component—US Payroll, UK Payroll, and global multi-country payroll all depend on Oracle's annual and quarterly tax law updates. Security patches address zero-day vulnerabilities and known exposures. Feature bundles add optional functionality without major version upgrades. MOS access enables you to engage Oracle support engineers for complex issues.

The Third-Party Support Landscape

The PeopleSoft support market shifted significantly in 2024. Rimini Street, which was the dominant third-party PeopleSoft support provider for over a decade, exited PeopleSoft support entirely. Organisations that relied on Rimini for cost savings must now transition to alternative providers.

Spinnaker Support: The Leading Alternative

Spinnaker Support has emerged as the primary third-party PeopleSoft support provider. Spinnaker operates a "clean room" development model, meaning it does not download or reverse-engineer Oracle patches. Instead, Spinnaker's engineering team independently creates fixes for reported bugs, provides tax and regulatory updates, delivers security patches, and supports custom code modifications.

Spinnaker's pricing averages 50 percent of Oracle's support rate, roughly $110,000 per year for an organisation paying $220,000 to Oracle. Spinnaker supports any active or even extended-support PeopleSoft release. Spinnaker covers bug fixes, tax updates, regulatory updates, security patches, upgrade support, and custom code modifications. For organisations stable on a specific PeopleSoft version with minimal plans for major upgrades, Spinnaker provides substantial cost savings.

The critical limitation is verification. You must evaluate Spinnaker's track record for tax and regulatory updates in your specific payroll regions. If you run US Payroll, UK Payroll, or complex multi-country payrolls, verify that Spinnaker's historical update coverage matches your requirements before signing.

Support Revolution: The European Alternative

Support Revolution is a UK-based provider covering Oracle and SAP software maintenance. Support Revolution offers similar coverage to Spinnaker—bug fixes, tax and regulatory updates, security patches, and custom code support. Pricing is comparable to Spinnaker, approximately 50 percent of Oracle support fees.

Support Revolution is optimised for European customers, particularly UK and EU-based organisations. If your primary payroll footprint is European, Support Revolution may offer faster response times and deeper familiarity with UK and European tax regulations. For organisations with primarily US payrolls, Spinnaker has deeper coverage history.

Rimini Street: Historical Context

Rimini Street exited PeopleSoft support in 2024. If your organisation currently uses Rimini for PeopleSoft, you must transition to an alternative provider. Rimini still provides support for Oracle Database, Oracle Fusion, Oracle E-Business Suite, and some other Oracle products, but PeopleSoft support is no longer available. Any Rimini PeopleSoft customers must evaluate Spinnaker or Support Revolution before Rimini's support contract expires.

In-House Support: The DIY Option

Some large organisations bring support in-house using their own Oracle-certified DBA teams supplemented by PeopleSoft consultants. This approach eliminates third-party support costs entirely but requires significant internal investment. You must maintain Oracle certification on your DBA team, retain PeopleSoft specialists, and accept responsibility for bug fixes, tax updates, and security patches.

In-house support is viable only if your PeopleSoft system is stable with minimal complex issues, your DBA team has deep PeopleSoft expertise, and you have budget capacity to handle unexpected bugs or security incidents independently. For most organisations, this approach trades cost savings for increased operational risk.

Cost Comparison: Oracle vs. Third Party

Let us walk through a realistic cost scenario. An organisation has $5 million in PeopleSoft licences across US Payroll, Human Resources, and Financial modules.

• Oracle Support Year 1: $5M × 22% = $1,100,000
• Oracle Support Year 5: $1,100,000 × (1.08^4) = $1,496,000 (36% increase)
• Oracle Support Year 10: $1,100,000 × (1.08^9) = $2,204,000 (100% increase)
• Spinnaker Support: Approximately $550,000 per year (50% of Oracle Year 1 rate)
• 5-Year Savings (Spinnaker): $3.2 million compared to Oracle trajectory
• 10-Year Savings (Spinnaker): $8.8 million compared to Oracle trajectory

These are substantial savings. But the decision to switch requires careful evaluation of the risks associated with leaving Oracle support.

What Third-Party Support Does Not Cover

Third-party PeopleSoft support has explicit limitations that organisations must understand before switching.

New Major Feature Releases

Third-party providers cannot deliver Oracle Cloud PeopleSoft, which is a fundamentally different product from on-premises PeopleSoft. If your organisation plans to migrate to Oracle Cloud PeopleSoft within the contract period, you will need Oracle support for the cloud platform regardless of your on-premises support choice.

Major Version Upgrades

Upgrading from PeopleSoft 9.1 to 9.2, or from an older PeopleSoft version to a significantly newer one, is a major undertaking. Third-party providers support the upgrade process, but you cannot use third-party support to remain on unsupported versions indefinitely. Oracle has extended PeopleSoft support to at least 2037, so staying on a current version is viable long-term, but major upgrades require careful planning.

PeopleSoft Update Manager (PUM) Access

Oracle's PeopleSoft Update Manager is the distribution mechanism for new patches and updates. If you leave Oracle support, you lose access to PUM for new patch bundles published by Oracle. Third-party providers create their own security fixes and cumulative patches, but you will not receive Oracle's official PUM bundles. This is manageable as long as your third-party provider is actively maintaining your PeopleSoft version.

Quarterly Security Patches

Oracle publishes quarterly security patches for critical vulnerabilities. Third-party providers create their own security fixes, but there is an inherent time lag. If Oracle announces a zero-day vulnerability and publishes a patch, Spinnaker or Support Revolution will need days or weeks to assess the vulnerability and release a fix. During that window, your PeopleSoft system carries additional risk.

Direct Oracle Development Team Access

For extremely complex or novel bugs, Oracle support customers can escalate to Oracle's development team. Third-party providers do not have this escalation path. If your PeopleSoft system encounters a deeply complex issue that requires Oracle engineering, you cannot resolve it within the third-party support model.

The Tax and Regulatory Risk

The largest decision factor for PeopleSoft support switching is tax and regulatory coverage. This is not theoretical—it is the most common reason organisations stay with Oracle support despite the cost.

If you operate US Payroll, you need quarterly federal tax updates and annual state tax updates. If you operate UK Payroll, you need quarterly National Insurance updates and annual tax code changes. If you operate multi-country payrolls in France, Germany, Brazil, or other complex jurisdictions, each region requires country-specific tax updates.

Spinnaker Support and Support Revolution both provide tax and regulatory updates, but you must evaluate their historical coverage against your specific payroll footprint. Ask for references from customers running similar payroll configurations. Request documentation of update history for your specific countries and payroll modules. Verify that the third-party provider's update cycle matches the regulatory update requirements in your jurisdictions.

If you make a tax update mistake and miss a critical regulatory change, you expose the organisation to payroll penalties, audit risk, and potential legal liability. This is not a situation where you can "wait and see" if the third-party provider delivers the required update. Validate regulatory coverage before signing the third-party support agreement.

Oracle Re-Entry Costs

If you leave Oracle PeopleSoft support and later decide to return, Oracle charges "back-support fees" covering the period you were unsupported. Back-support fees are calculated at 150 percent of the fees that would have been due during the gap period.

If you leave Oracle support for three years, you owe 150 percent of three years of support fees to re-enter. For an organisation paying $1.1 million per year, three years of back-support costs $4.95 million. This makes returning to Oracle support extremely expensive.

Back-support fees are a strong incentive to plan your exit carefully. Do not leave Oracle support expecting to return in one or two years if circumstances change. The re-entry penalty is severe enough that you should only exit if you are confident in the long-term viability of your PeopleSoft system on third-party support.

Oracle's Legal Position and Litigation History

Understanding Oracle's past litigation against support competitors is important context for evaluating third-party risk.

Oracle vs. Rimini Street

Oracle sued Rimini Street multiple times for copyright infringement, alleging that Rimini downloaded Oracle patches and used them as the basis for Rimini's own support products. Oracle won judgements against Rimini in federal court. As a result of this litigation, Rimini changed its business model and eventually exited several support areas, including PeopleSoft.

Spinnaker's Clean Room Model

Spinnaker Support operates a "clean room" development model specifically to avoid the litigation risks that surrounded Rimini. Spinnaker does not download Oracle patches or reverse-engineer Oracle code. Instead, Spinnaker's engineers independently create fixes based on bug reports and testing. This is more expensive and time-consuming than copying Oracle patches, but it is legally defensible.

As of 2026, Oracle has not successfully sued Spinnaker for PeopleSoft support. Spinnaker's clean room model appears to meet Oracle's copyright and patent requirements, although no court has definitively ruled on this.

Legal Risk Assessment

The legal risk of using third-party support is non-zero but manageable. Oracle could theoretically sue Spinnaker or Support Revolution in the future. However, both providers operate under explicitly disclosed models that do not copy Oracle code. The precedent from litigation against Rimini suggests that as long as third-party providers do not reverse-engineer or replicate Oracle's code, they can operate legally.

The more practical risk is business continuity. If Oracle were to successfully sue a third-party provider and force them out of business, your PeopleSoft support would terminate. This is why evaluating the provider's financial stability and market position is important. Spinnaker is well-established and well-funded, but no vendor is immune to catastrophic legal or business risk.

When Third-Party Support Makes Sense

Third-party PeopleSoft support is the right choice only under specific conditions. If these conditions do not apply to your organisation, staying with Oracle support is likely the safer decision.

Condition 1: Stable PeopleSoft Version

Your organisation must be stable on a PeopleSoft version with no plans for major upgrade in the next 2 to 3 years. If you are planning PeopleSoft 9.1 to 9.2 upgrade within 12 months, stay with Oracle support through the upgrade, then evaluate third-party for post-upgrade years.

Condition 2: Support Costs Are a Budget Pressure

Support cost escalation must be material to your organisation. If PeopleSoft support is a small line item in IT budget, the complexity and risk of switching is not justified. If support is a significant and growing cost, the savings justifies the transition effort.

Condition 3: Oracle Cloud Migration Is 3+ Years Away

You must have at least 3 years of runway on PeopleSoft before committing to Oracle Cloud. Oracle Cloud is a different product, and you will need Oracle support for the cloud migration and cloud operations. Third-party support is only appropriate for the on-premises phase.

Condition 4: Stable PeopleSoft Operations

Your PeopleSoft system must be running well with minimal complex bugs, performance issues, or custom code complications. If you are constantly creating support tickets for complex issues, you need Oracle's escalation path and development team access. Third-party support is optimised for stable systems.

Condition 5: Payroll Coverage Confidence

You must be confident that your third-party provider has strong coverage in your specific payroll countries and jurisdictions. If you are uncertain about regulatory update coverage in your regions, the risk of a missed tax update outweighs the cost savings.

Decision Framework: Stay or Switch

Use this structured framework to decide whether to stay with Oracle PeopleSoft support or evaluate third-party alternatives.

Step 1: Audit Current Oracle Support Spend

Calculate your organisation's current annual Oracle PeopleSoft support fee and project it forward 5 and 10 years using 8 percent annual escalation. This is the cost baseline. If the 5-year and 10-year costs do not create budget pressure, stay with Oracle.

Step 2: Map Critical Support Dependencies

Document which PeopleSoft features depend on Oracle support. Specifically: Which payroll jurisdictions require tax updates? Which modules generate open support requests? Which custom code modifications require Oracle escalation? Which security or performance issues require Oracle's diagnostic tools?

Step 3: Evaluate Third-Party Proposals

Request formal proposals from Spinnaker Support and Support Revolution. Request references from customers with similar payroll configurations. Ask for update history documentation covering your specific countries and modules. Verify response SLAs and escalation processes match your requirements.

Step 4: Negotiate with Oracle

Use the third-party proposal as leverage in Oracle negotiations. Oracle frequently offers 10 to 20 percent support discounts when organisations demonstrate credible third-party alternatives. This alone can justify the evaluation process.

Step 5: Execute Structured Exit Plan

If switching to third-party support, do not simply let Oracle support expire and switch. Instead: Close all open Oracle support tickets before transition. Ensure the third-party provider is fully prepared with your PeopleSoft environment details. Coordinate the transition with tax update cycles to ensure no regulatory gaps. Plan for 30-60 days of parallel support if possible. Document the transition in writing with clear responsibility assignments.

The Broader Oracle Portfolio Context

Your PeopleSoft support decision must align with your broader Oracle strategy. If you are planning Oracle Cloud migration within 3 to 5 years, or if you are evaluating Oracle Fusion as a replacement for PeopleSoft, the third-party support evaluation changes.

Third-party support is a bridge strategy for organisations staying on on-premises PeopleSoft. It is not a long-term alternative to Oracle Cloud. If your organisation's direction is Oracle Cloud, your support strategy should reflect that direction, and third-party support is temporary at best.

Conversely, if your organisation has decided to remain on PeopleSoft for the long term—leveraging Oracle's commitment to support through 2037—third-party support becomes a sustainable strategy for cost management over the next 5 to 10 years.

Key Takeaways

Oracle Support Cost Escalation Is Mandatory: Oracle PeopleSoft support increases at 8 percent per year, not 3-4 percent. After 10 years, support costs double. This is not negotiable in standard Oracle contracts.

Third-Party Alternatives Offer Real Savings: Spinnaker Support and Support Revolution provide approximately 50 percent cost savings compared to Oracle support, equating to millions of dollars over 5-10 years for medium to large PeopleSoft deployments.

Regulatory Coverage Is Critical: The largest risk when switching to third-party support is inadequate tax and regulatory updates for your payroll jurisdictions. Verify coverage before committing.

Rimini Street Has Exited: If you currently use Rimini for PeopleSoft support, you must transition to Spinnaker or Support Revolution before Rimini support ends.

Back-Support Penalties Are Severe: Returning to Oracle support after switching to third-party costs 150 percent of the missed fees. Plan your exit carefully if you anticipate potential re-entry.

Evaluate Based on Specific Conditions: Third-party support makes sense only if you have a stable PeopleSoft version, adequate runway before Oracle Cloud migration, minimal complex bugs, and confidence in regulatory coverage.

Use Third-Party Leverage for Oracle Discounts: Even if you ultimately stay with Oracle, evaluating third-party alternatives often yields 10-20 percent Oracle support discounts through competitive negotiation.