Is Oracle Third-Party Support Legal?

Is Oracle Third-Party Support Legal?

Yes – Oracle third-party support is legal for enterprises running Oracle’s on-premise software. Court rulings (notably in the Oracle vs. Rimini Street case) have affirmed that Oracle customers can choose independent support providers, as long as licensing rules are respected.

CIOs and sourcing leaders are increasingly leveraging third-party support to slash costs and extend the life of stable Oracle systems.

This advisory offers an in-depth analysis, practical insights, and guidance on utilizing third-party support in a compliant and strategic manner.

The Support Dilemma: Why This Question Arises

Oracle’s software support fees are notoriously high – typically about 22% of the license price per year, with regular increases.

Enterprises maintaining large Oracle estates pay millions annually just to receive vendor updates and basic support.

Many IT leaders ask, “Isn’t there a cheaper way to support our Oracle systems?” Third-party support has emerged as that alternative, promising 50% lower fees and more personalized service.

However, Oracle’s aggressive stance against third-party providers and past lawsuits have sown doubts about legality.

The result is a dilemma for CIOs: stick with Oracle’s costly support or switch to an independent provider and risk the vendor’s wrath? Understanding the legal landscape is key to making an informed decision.

Key insight: It is legal for Oracle licensees to use third-party support.

Oracle cannot cancel your license for switching support vendors. But there are compliance considerations (and vendor pushback tactics) to be aware of, which we will explore.

What Is Third-Party Support for Oracle?

Third-party support means using an independent company (outside of Oracle) to provide software maintenance and support for Oracle products.

Instead of paying Oracle for annual support on databases, ERP, or other on-premise software, a customer contracts a certified third-party expert firm to handle bug fixes, troubleshooting, tax/regulatory updates, and general assistance.

Key characteristics of third-party support services:

• On-Premises Focus: It applies to Oracle on-premise software (e.g., Oracle Database, E-Business Suite, PeopleSoft, JD Edwards, Siebel). You own a perpetual license, so you can run the software and seek support elsewhere. (Oracle’s cloud/SaaS products are excluded – those subscriptions inherently include Oracle’s support and can’t be supported by outsiders.)
• No Oracle Patches: Third-party providers cannot ship Oracle’s proprietary patches or new versions. Instead, they often develop their own fixes and workarounds for issues and guide security and regulatory compliance updates.
• Vendor-Independent Expertise: These providers employ former Oracle engineers and experts. They support your customizations and performance tuning needs – often areas Oracle’s standard support won’t fully cover.
• Typical providers include firms such as Rimini Street (the largest player) and Spinnaker Support, among others. They support thousands of Oracle customers globally under a model that emphasizes cost savings and extended support timelines.

By utilizing third-party support, enterprises can continue to run their Oracle systems while avoiding payment of Oracle’s maintenance fees.

This raises the question: will Oracle allow this, and is it within your legal rights? The short answer: yes, with certain constraints to manage.

Court Rulings: Third-Party Support Is Legal

The legality of Oracle’s third-party support was at the center of a landmark legal battle: Oracle vs. Rimini Street. Oracle sued Rimini Street (a prominent third-party support provider), alleging copyright infringement and contract violations in how Rimini delivered support.

After years of litigation, the outcomes have clarified the legal status:

• Customers’ Right to Choose: Courts have affirmed that Oracle licensees have the right not to renew Oracle support and instead hire a third-party support provider or self-support their systems. Choosing independent support does not, in itself, violate your Oracle license.
• Third-Party Services Permissible: It was upheld that third parties, such as Rimini Street, can legally offer support services for Oracle products, provided they adhere to the license terms. This means the concept of third-party support is lawful.
• IP and Process Limitations: The court ruled that some of Rimini Street’s methods were illegal, specifically the copying of Oracle’s software onto their own systems to develop patches. Essentially, third-party providers must avoid infringing Oracle’s intellectual property (no unauthorized copying or distribution of Oracle’s code). Today, compliant providers only work on customer-owned environments or use tools that don’t require illegal copying.
• No Ban on Leaving Oracle Support: Importantly, Oracle cannot force customers to stay on its support. Other than losing access to Oracle’s updates, there’s no legal penalty for leaving. Your perpetual license remains valid even if you stop paying Oracle for support.

Bottom line: Third-party support has been validated in court as a legal alternative. Oracle’s attempts to portray it as “illegal” have been rejected – it’s the manner of delivery that was at issue, not the right to obtain independent support.

Modern third-party providers operate within legal guidelines established by these rulings.

Why Enterprises Embrace Third-Party Support

With legality confirmed, many organizations are turning to third-party support for strategic benefits.

Key reasons enterprises (including numerous Fortune 500 companies) have made the switch:

• Dramatic Cost Savings: Independent support contracts typically cost 50% of Oracle’s standard support fees. For example, if you pay Oracle $2 million yearly, a third-party might charge about $1 million for the same coverage – freeing significant budget. Additionally, companies avoid ancillary costs (forced hardware upgrades, etc.), achieving up to 70–90% total savings over several years.
• Extended System Lifespan: Oracle typically ends “Premier Support” for products after 5 years, prompting upgrades or expensive extended support. Third-party support allows you to run stable legacy versions indefinitely with full support. Organizations can keep a reliable ERP or database version for 10-15+ years without an unwanted upgrade dictated by Oracle’s timeline.
• Better Service Quality: Many CIOs report more responsive, personalized support from third-party vendors. Providers like Rimini Street assign senior engineers to each client and often promise faster issue resolution. You avoid the bureaucratic ticket queues of vendor support. For critical systems, this high-touch model improves uptime and satisfaction.
• Support for Customizations: Oracle’s support policy does not cover custom code or modified configurations in depth; however, third-party support will troubleshoot and assist with your customizations, as they recognize each client’s unique environment.
• Freedom from Forced Upgrades: With independent support, you won’t be pressured into cloud migrations or software upgrades just to stay supported. You decide when (and if) an upgrade makes business sense. This flexibility is invaluable for organizations with heavily customized or stable systems that meet their needs as they are.
• Proven Approach: Third-party support is no longer a fringe option – it’s utilized by thousands of organizations worldwide across various industries, including manufacturing, government, finance, and more. Seeing peers successfully save money and run stable operations with third-party support gives confidence that it’s a low-risk, mainstream strategy now.

In short, enterprises utilize third-party support to reduce costs and gain control over their Oracle roadmap, without compromising system reliability.

Oracle vs. Third-Party Support – Key Differences and Cost Comparison

To evaluate this option, it’s important to understand how third-party support differs from Oracle’s official support in practice. Below is a high-level comparison:

Takeaway: Third-party support can significantly reduce costs and maintain the operation of older systems with personalized service. In exchange, you forego Oracle’s updates and must be diligent about license compliance.

It essentially swaps Oracle’s high-cost, one-size-fits-all support for a lower-cost, tailored service – with the trade-off that you give up automatic access to new Oracle releases (unless you re-engage Oracle).

Risks and Compliance Considerations

Using Oracle third-party support is legal, but it does introduce some considerations and risks to manage:

• Security Updates: Without Oracle’s patches, you rely on your provider for critical bug and security fixes. Top third-party providers do issue patches/workarounds for known vulnerabilities. Still, in rare cases, a serious security flaw might only be fully fixed by upgrading to a new Oracle version. Mitigation: Before leaving Oracle support, apply all the latest Oracle patches. After switching, work closely with the provider on security monitoring and have a plan if a future upgrade becomes necessary for security reasons.
• License Compliance: Your Oracle license remains in effect, and you must adhere to its terms. Oracle can still audit your usage even if you’re off their support. Some organizations fear that leaving Oracle support could increase audit scrutiny (since you’re no longer a paying customer). Mitigation: Conduct an internal license audit and clean up any compliance issues before switching. Ensure you aren’t using any Oracle features or extra modules beyond what you purchased. After switching, maintain accurate records and periodically review compliance to avoid any surprises.
• Oracle Contract Pitfalls: Be aware of Oracle’s policies that could affect you:
  • The Matching Support Levels clause means you generally cannot drop support on a subset of licenses for a given Oracle product. If you try to keep some licenses on Oracle support and let others lapse, Oracle may re-price the supported licenses at full list price (wiping out savings). Solution: When moving to third-party support, typically take the entire product environment off Oracle support.
  • If you ever want to return to Oracle’s support (for example, to upgrade in the future), Oracle will charge a reinstatement fee – often equivalent to back pay for the lapsed years plus a penalty. This can be significant. Solution: Factor this into your long-term plan. Many companies that switch to third-party support do so with a long-term perspective, with no intention of returning to Oracle unless absolutely necessary.
  • You will lose access to Oracle’s online support portal, updates, and certifications while off support. This is expected, but ensure your team is prepared for that gap (third-party support will provide their knowledge base and help, but it’s not Oracle’s official resources).
• Relationship with Oracle: Choosing an independent support vendor can strain your relationship with Oracle’s sales and account reps. They may strongly discourage the move, claim it’s risky, or insinuate you could face legal issues (a common FUD tactic). They might also be less inclined to offer discounts on other products since you’re reducing your spend. Mitigation: Be transparent with executive leadership about why you’re switching (cost/value reasons) and maintain a professional dialogue with Oracle. In many cases, Oracle will still sell you new licenses or cloud services in the future, but expect some pushback. Remember, it’s your right to optimize support costs.

Despite these considerations, none are show-stoppers if managed well. Thousands of companies have navigated them successfully.

The key is to do your homework: understand your contracts, choose a reputable third-party provider, and have a solid transition plan.

Oracle’s Perspective vs. Customer Rights

It’s important to recognize Oracle’s point of view, even as you exercise your rights:

• Oracle’s Stance: Oracle publicly maintains that customers get the best quality and security from Oracle’s own support. They argue that only the vendor has the latest patches and full knowledge of the software. Oracle also has a vested financial interest in keeping customers on its support (which can be half of Oracle’s revenue on some products). Thus, the company has fought third-party providers in court and often scares customers with compliance warnings.
• Reality and Your Rights: Despite Oracle’s posture, it cannot forbid you from seeking third-party support. As long as you comply with your license agreement (no unlicensed use of Oracle intellectual property), you are not breaking any law or contract by using an independent provider. Even Oracle’s executives have implicitly acknowledged that third-party support is legitimate when done correctly – it’s competition, not a violation. And in regions like the EU, competition laws support customers’ freedom to choose support services.
• No Support ≠ No License: A critical reminder – ending your Oracle support contract does not terminate your right to use the software. You have a perpetual license for the version you own. So your business can continue running Oracle applications indefinitely, with or without Oracle’s support. Oracle’s software license agreements do not require you to purchase support; it’s typically optional (albeit heavily encouraged).
• Support vs. Cloud Subscriptions: Please note that this discussion applies to on-premise licenses. If you use Oracle’s Cloud SaaS products, you cannot separate support – it’s bundled in the subscription. Oracle can stipulate terms there that don’t allow outside support. But for the vast installed base of Oracle on-premise ERP and databases, the choice is yours.

In summary, Oracle may not like it, but the customer is in control. You have leverage to negotiate better terms or opt out of Oracle support entirely.

Knowing that third-party support is a lawful option gives sourcing and IT executives a powerful tool to optimize costs and demand more value from Oracle.

Recommendations (Expert Tips)

If you’re considering third-party support for Oracle systems, here are some practical recommendations to ensure success:

• 1. Perform a License Health Check: Before changing support, audit your Oracle licenses. Confirm you have the proper entitlements for all deployments. Resolve any compliance gaps proactively to avoid issues later (especially if Oracle decides to audit).
• 2. Determine Support Scope Strategically: Identify which Oracle systems are good candidates for third-party support. Stable, mature systems that you don’t plan to upgrade soon (or ever) are prime candidates. Mission-critical systems can also be switched if the provider has strong capabilities, but weigh the risk tolerance.
• 3. Choose a Reputable Provider: Stick with established third-party support vendors (like Rimini Street or Spinnaker Support) who have a proven track record. Vet their legal compliance approach – ask how they deliver support without violating Oracle’s IP. Check references from similar customers.
• 4. Negotiate Clear SLAs: Ensure the contract with the new provider includes service level agreements that meet your business needs (response times for critical issues, etc.). Good third-party support should match or exceed the responsiveness you had from Oracle.
• 5. Archive Oracle Materials: Before your Oracle support ends, download all relevant patches, documentation, and knowledge base articles available to you. While not intended for distribution, these resources are for your internal use and can serve as valuable references once you no longer have access to Oracle’s support portal.
• 6. Secure Executive and Legal Buy-In: Brief your leadership and legal department on the plan. Explain the cost benefits and legal basis (court rulings) that support this move. Having executive sponsorship will help if Oracle escalates concerns. Your legal team should also review contracts (Oracle’s and the new provider’s).
• 7. Time Your Transition: Align the switch with your Oracle support renewal dates. Typically, you’d time the cutover to third-party support right when Oracle support lapses (at the end of your paid period) to avoid overlapping costs. Avoid mid-term cancellations if possible, since Oracle generally doesn’t refund unused support.
• 8. Plan for the Long Term: Going independent is usually a multi-year strategy. Plan to stay on third-party support for an extended period to maximize savings. If you anticipate needing an Oracle upgrade in a year or two, consider whether leaving support now or later makes sense (e.g., you might renew Oracle support until after a planned upgrade, then switch).
• 9. Monitor and Reassess: Continuously measure the results after switching. Track cost savings, system performance, and support responsiveness. If the third-party provider meets or exceeds expectations, you’ve validated the decision. If not, you can adjust (e.g., address issues with the provider, or in an extreme case, consider returning to Oracle support).
• 10. Stay Informed: Keep up with any changes in Oracle’s policies or legal landscape. Although third-party support is now well established, continue to monitor industry news. This will help you address any new Oracle tactics or ensure your provider stays fully compliant with the latest requirements.

Checklist: 5 Actions to Take

For CIOs and sourcing professionals ready to explore Oracle third-party support, here’s a simple step-by-step checklist:

1. Assess Your Environment: List all Oracle systems and their versions. Mark those that are stable and do not require upcoming upgrades. Verify when each support contract expires and what you’re paying.
2. Review Contracts and Policies: Pull out your Oracle license and support agreements. Look for clauses on support policies (e.g., matching service levels, reinstatement fees). Consult your legal team to interpret any complex terms related to third-party support or termination.
3. Engage Potential Providers: Reach out to leading third-party support vendors for an initial discussion or evaluation to explore potential opportunities. Request a cost savings analysis – most providers can quickly estimate how much you’d save. Also, ask how they handle security patches and compliance.
4. Internal Alignment: Present the findings to your internal stakeholders (IT leadership, finance, procurement). Build a business case highlighting the ROI (e.g. “50% cost reduction equals $X million saved annually”) and the plan to mitigate any risks (security, compliance).
5. Plan the Transition: If you decide to proceed, coordinate a timeline for the switch. Notify Oracle (if required by contract) that you won’t renew support for certain products. Ensure all relevant patches/documentation are downloaded beforehand. Have the third-party provider ready to onboard your systems immediately after Oracle support expires, ensuring a seamless transition with no support gap.

Following this checklist will help you transition smoothly and transparently, with everyone on the same page.

FAQs

Q: Can Oracle penalize us or terminate our software license if we switch to a third-party support vendor?
A: No, Oracle cannot cancel your existing license simply because you chose not to renew its support. Your right to use the software (perpetual license) remains intact. The worst-case scenario is that if you later want Oracle support again, you’d pay a reinstatement fee. But Oracle cannot void your license for using third-party support – it’s your contractual right to decide who maintains your software.

Q: Will we still get updates and security patches without Oracle support?
A: You will lose access to Oracle’s new patches, upgrades, and official security updates released after you leave Oracle support. However, third-party support providers supply their own patches, fixes, and security mitigations for issues that arise. They will not have Oracle’s new versions, so essentially, you’ll be stuck with your current software version. Many companies mitigate this by fully patching to the latest Oracle updates before switching, then relying on the provider for subsequent fixes. It’s a trade-off: you give up Oracle’s future patches, but you avoid forced upgrades and get custom fixes as needed.

Q: Is third-party support only for older systems, or can we use it for critical, newer applications as well?
A: You can use it for both, depending on your situation. It’s commonly used for stable, older systems (e.g., an ERP that’s several versions behind but meets all your needs). In such cases, third-party support enables them to run securely far beyond Oracle’s official support timeline. However, many enterprises also place mission-critical production systems under third-party support – including core databases and applications – if they determine that the service quality meets their needs. The key is evaluating the provider’s capabilities and your risk tolerance. Some organizations might keep very new, rapidly evolving Oracle products on Oracle support, while moving mature ones to third-party support. It’s not an all-or-nothing decision; you can mix and match based on where it makes sense.

Q: How does using an independent support provider affect our relationship with Oracle?
A: It can become more transactional and potentially tense, but it doesn’t sever the relationship entirely. Oracle sales teams may push back, as you’re cutting a revenue stream. You might lose any “goodwill” discounts on future purchases in the near term. However, Oracle will still be willing to sell you licenses or cloud services if you want them – they are not likely to refuse your business. Be prepared for some aggressive retention efforts from Oracle when they become aware of your plans. Internally, ensure your executives are aligned on the decision so that Oracle’s messaging doesn’t cause panic. In time, many customers find that Oracle accepts their choice, especially if they remain a license customer for other products.

Q: Are there any regions or laws that impact third-party support differently (for example, outside the U.S.)?
A: Generally, the legality of third-party software support is upheld in major markets worldwide. In the United States, the precedent from the Rimini Street case applies. In the European Union, there are strong antitrust and competition laws that support customers’ rights to use independent maintenance services (and prevent vendors from locking you in unfairly). Some countries’ public sectors even encourage seeking competitive support bids to reduce costs. Always check local regulations, but there is no region known to outright ban third-party support for Oracle. The key is always the same: ensure your usage is compliant with the license terms, regardless of who provides support.

Download Procurement Advisory Playbook: Transitioning from Oracle Support to Third‑Party Support.

💸 Realize Tangible Financial Benefits Beyond Just Cost Savings

• Save 50%+ annually on Oracle support fees — and avoid costly forced upgrades.
• Extend the life of stable systems without paying for software you don’t need.
• Understand the total cost reduction: license optimization + deferred hardware/software spend.
• Learn how third-party support frees up budget for innovation, not just maintenance.

Read more about our Third Party Transition Service.

Do you want to know more about our Third Party Advisory Services?

Please enable JavaScript in your browser to complete this form.

Name *

First

Last

Email *

Company

Message *

Submit