Rimini Street vs Spinnaker Support vs SAP: Independent Maintenance Comparison 2026

SAP Enterprise Support costs 22% of your net licence value every year — and rising. With SAP ECC mainstream maintenance ending in 2027 and Extended Maintenance adding a further premium, more enterprises than ever are asking whether third-party support from providers like Rimini Street or Spinnaker Support is a viable alternative. This comparison gives you the honest forensic analysis SAP's account team won't.

We've reviewed the commercial terms, service level agreements, and real-world client experiences across all three options. The conclusion isn't simple — but the data is clear: for the right enterprise profile, third-party maintenance can represent a €2–5M annual saving with manageable risk. For others, it introduces dependency and compliance exposure that makes it the wrong choice entirely.

The Three Options: What Each Provider Actually Offers

SAP Enterprise Support (with or without Extended Maintenance)

SAP's standard maintenance offering costs 22% of net licence value annually. During mainstream maintenance (until end of 2027 for ECC), this includes legal and regulatory updates, security patches, new SAP Notes, access to SAP Support Portal, and cloud integration updates. After 2027, SAP Extended Maintenance provides a reduced service at an additional ~2% surcharge — security and critical statutory patches only, no new functionality, no new Notes.

Rimini Street

Rimini Street is the largest independent enterprise software maintenance provider globally. They offer third-party support for SAP (primarily ECC), Oracle, and other enterprise platforms at approximately 50% of the incumbent vendor's maintenance fee. Their service model promises a dedicated support engineer per account, faster initial response times than SAP's standard SLA, and coverage of security patches and tax/regulatory updates through proprietary tooling rather than SAP Notes.

Spinnaker Support

Spinnaker Support is the second-largest third-party SAP maintenance provider. They position as a higher-touch, more customised alternative to Rimini Street, with dedicated engineers and a reputation for stronger service levels on complex ECC environments. Pricing typically ranges from 40–50% of SAP's maintenance fee, comparable to Rimini Street but often with more flexibility on contract terms.

Head-to-Head Comparison

Comparison Dimension	SAP Enterprise Support	Rimini Street	Spinnaker Support
Annual Cost	22% net licence value	~11% net licence value	~10–11% net licence value
Post-2027 ECC Premium	+2% (Extended Maintenance)	No change	No change
Initial Response SLA	P1: 4 hours (standard)	P1: 10 minutes (dedicated eng)	P1: 15 minutes (dedicated eng)
Security Patches	SAP Notes — comprehensive	Proprietary patches — adequate for most	Proprietary patches — adequate for most
Tax/Regulatory Updates	Comprehensive	Covered for 60+ countries	Covered for 50+ countries
New SAP Notes Access	Yes	No	No
SAP Support Portal Access	Yes	No	No
Future SAP Product Access	Yes — S/4HANA, BTP, etc.	No — standalone support only	No — standalone support only
Migration Support	Via SAP services	Re-entry possible but complex	Re-entry possible but complex
Contract Flexibility	Annual, tied to licence	Negotiable 1–5 year terms	Negotiable, often more flexible than Rimini
Litigation History	N/A	Settled SAP copyright lawsuit 2014	No major IP disputes

The Real Cost Comparison Over Three Years

For an enterprise with €60M in SAP net licence value, the three-year cost comparison (2027–2030, assuming Extended Maintenance period) is stark:

Provider	Year 1 Cost	Year 2 Cost	Year 3 Cost	3-Year Total
SAP (incl. Extended Maint.)	€14.4M (24%)	€14.4M	€14.4M	€43.2M
Rimini Street (~11%)	€6.6M	€6.6M	€6.6M	€19.8M
Spinnaker (~10.5%)	€6.3M	€6.3M	€6.3M	€18.9M

The three-year saving potential is €23–24M — material enough to fund a significant portion of an S/4HANA migration programme. This is not a trivial number for any enterprise CFO to dismiss without forensic analysis.

Rimini Street: Strengths and Weaknesses

Strengths

• Global scale: Rimini Street has supported over 5,000 clients across 130+ countries and has the deepest bench of independent SAP support engineers globally
• Dedicated engineering model: Each client is assigned a Primary Support Engineer (PSE) with deep knowledge of that client's specific SAP landscape — contrasting with SAP's ticket-based routing model
• Faster response: Rimini Street's P1 SLA of 10-minute initial response substantially outperforms SAP's standard 4-hour window
• Tax and regulatory coverage: Coverage across 60+ countries with a dedicated regulatory updates team
• Price certainty: Fixed contract terms without the pricing escalators embedded in SAP maintenance contracts

Weaknesses

• IP litigation history: Rimini Street settled a significant copyright infringement lawsuit with SAP in 2014 (paying $356M). While the legal issues were resolved, it signals that SAP has been aggressive in pursuing IP claims against the business model
• No access to SAP's IP: Rimini Street cannot legally distribute SAP Notes, SAP code, or SAP-authored content. Their patches are independently developed
• Cloud integration gap: Enterprises using BTP, SuccessFactors, or other SAP cloud products alongside ECC cannot get integrated support through Rimini Street — creating a split-support model
• Migration complexity: Re-entering SAP maintenance after using Rimini Street requires careful planning and may trigger back-maintenance claims

Spinnaker Support: Strengths and Weaknesses

Strengths

• Higher-touch service model: Spinnaker positions as a premium provider with smaller client ratios per engineer than Rimini Street, often resulting in more personalised service
• Cleaner IP position: No major IP litigation history with SAP, which enterprise legal teams find more comfortable
• Contract flexibility: Spinnaker is frequently cited as more commercially flexible than Rimini Street on contract structure, notice periods, and custom SLA arrangements
• Strong for complex ECC landscapes: Enterprises with deeply customised ECC environments report high satisfaction with Spinnaker's ability to support non-standard configurations

Weaknesses

• Smaller scale: Less global reach than Rimini Street — important for multinationals with regulatory requirements in less-common jurisdictions
• Narrower regulatory coverage: 50+ countries vs Rimini's 60+ — may not cover all of your statutory update requirements
• Same fundamental limitations: Like Rimini Street, no access to SAP Notes, SAP Support Portal, or future SAP product entitlements

When Third-Party Maintenance Makes Sense

Third-party maintenance from Rimini Street or Spinnaker Support is commercially sound when your situation matches this profile:

• Your ECC environment is stable and frozen — no new development, no ongoing customisation, no cloud integration requirements
• You have a clear, funded migration plan for S/4HANA with a go-live date of 2028–2030, meaning you only need maintenance coverage for a defined window
• Your regulatory and statutory update requirements are covered by the provider's country coverage — verify this explicitly for every jurisdiction where you operate
• Your security and compliance posture can accept proprietary patches rather than SAP-authored Notes — this requires a legal and security review
• You are not planning to use additional SAP cloud products (BTP, SuccessFactors, Concur) that would require active SAP support entitlements

When to Stay with SAP Support

SAP maintenance remains the better commercial choice when:

• Your migration to S/4HANA is imminent (2027 or early 2028) — the administrative and contractual friction of switching and returning isn't justified by 12–18 months of savings
• You are actively consuming SAP cloud products — SAP BTP, SAC, SuccessFactors — that require integrated SAP support entitlements
• You operate in jurisdictions with complex, frequently-changing statutory requirements that neither Rimini Street nor Spinnaker has demonstrated deep coverage for
• Your SAP landscape is actively evolving — new customisations, integration projects, or functionality rollouts that require access to SAP Notes and the Support Portal
• Your enterprise's risk profile requires the certainty of SAP's own IP and contractual accountability

Regardless of which path you take, our SAP support cost reduction advisory can help you challenge your current maintenance rate, negotiate better Extended Maintenance terms, and structure the transition to third-party support if that's the right call. The Extended Maintenance cost analysis provides additional context on SAP's post-2027 pricing.

Negotiating Whichever Path You Choose

One critical insight regardless of your decision: both SAP maintenance fees and third-party maintenance contracts are negotiable. Enterprises that engage either provider without independent benchmarking data consistently overpay.

For SAP: the 22% Enterprise Support rate is the starting point, not the floor. Volume discounts, ELA structures, and commitment-based reductions are all available for enterprises willing to negotiate. Our SAP contract negotiation team has benchmarking data from hundreds of maintenance negotiations.

For third-party: Rimini Street and Spinnaker both have list rates, but both are commercially flexible. Committing to multi-year contracts, larger scopes, or specific migration timelines can reduce the headline rate below their standard 50%-of-SAP-rate starting point.

Related Resources

• SAP Extended Maintenance 2027–2030: What It Costs and Whether It's Worth Paying
• SAP Standard Support vs Enterprise Support: Which One Do You Actually Need in 2026?
• SAP Enterprise Support Alternatives: How to Cut Your 22% Annual Fee
• SAP Third-Party Maintenance: The Complete Guide to Alternatives and Savings
• SAP Support Cost Reduction Service
• Contact SAP Licensing Experts