A corporate headquarters district at dusk
Guide · Oracle · Support

Oracle Third Party Support Providers. How to choose.

The independent support market is small, public, and uneven on scope. Size matters less than coverage of your exact modules, versions, and regulatory needs.

Read the Framework Oracle Practice
500+Enterprise clients
$2B+Under advisory
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

The Oracle third party support market is led by two public scale providers and a set of specialists. The right choice depends on your estate, not the brand.

Coverage of your exact modules and versions, the security model, and contractual indemnification matter more than provider size.

This guide walks the market, the selection criteria, and the process. Read it with the third party support guide.

Key takeaways

What every buyer checks before signing a support provider

  • Small market. Two public scale providers and a handful of specialists.
  • Coverage first. Confirm your exact modules and versions are supported.
  • Security model. Ask how vulnerabilities are handled without Oracle patches.
  • Indemnification. The provider should stand behind the legal position.
  • References. Talk to customers running your platform, not a generic list.
  • Exit terms. Know the path back to Oracle or onward before you sign.

Who are the main Oracle third party support providers?

The market is led by two public scale providers and a set of regional specialists. Rimini Street is publicly listed and files detailed disclosures with the United States Securities and Exchange Commission.

Spinnaker Support is the other broad provider, with specialists covering narrower module sets. Provider news and scope are tracked on the Rimini Street press release archive.

The market in brief

  • Scale providers. Broad coverage across database, middleware, and applications.
  • Specialists. Deep on a narrow module or industry set.
  • Selection signal. Match the provider's strength to your estate.

Why public disclosure helps

A publicly listed provider files audited financials and discloses litigation, which lets you assess stability before you commit a multi year support relationship to it.

What should you check before signing a provider?

Check fit, not fame. The provider must cover your exact modules and versions, supply tax and regulatory updates where you need them, and stand behind the legal position.

The pre signing checklist

  • Coverage. Every module and version you run, in writing.
  • Regulatory. Tax, legal, and statutory updates for your jurisdictions.
  • Indemnification. The provider indemnifies you on the support method.
  • Service levels. Response times that match your operational risk.

Provider evaluation matrix

CriterionWhat good looks likeWhy it matters
Module coverageEvery module and version namedGaps become unsupported risk
Regulatory updatesYour jurisdictions coveredPayroll and tax must stay current
Security modelVirtual patching and monitoringReplaces Oracle patches
IndemnificationProvider stands behind methodShifts legal risk off you
ReferencesCustomers on your platformPredicts real satisfaction

How do providers handle security without Oracle patches?

Independent providers cannot ship Oracle's patches, so they secure the estate by other means. The contrast is with Oracle's own Lifetime Support Policy, which gates patches to the premier window.

The security approach

  • Virtual patching. Controls at the network and application layer.
  • Configuration hardening. Reducing the attack surface of the estate.
  • Monitoring. Detection and response in place of vendor patches.

How do you run a third party support selection?

Run it as a structured procurement, not a single quote. Baseline the current support, scope the requirement, and compare providers on fit and indemnification.

The selection process

  • Baseline. Document the current Oracle support scope and cost.
  • Scope. Write the requirement against your exact estate.
  • Compare. Score providers on coverage, security, and indemnity.

Where the common advice on choosing a support provider is wrong

The standard advice is to pick the biggest provider for safety. We disagree. In roughly 18 of the 30 selections we ran across 2024 and 2025, the deciding factor was whether the provider covered the buyer's exact module and version set with strong indemnification, not its overall size. A large provider with thin coverage of your platform is weaker than a specialist who lives in it. The buyer side move is to score every provider against your estate and your indemnification needs, then choose on fit, treating brand and scale as a tiebreaker rather than the headline criterion.

A procurement team comparing support provider proposals
The right provider is the one that covers your exact estate with indemnification, not the one with the largest logo wall.
30
Provider selections reviewed
60 to 70%
Decided on coverage fit
2
Public scale providers

Source: Redress Compliance advisory engagement file, 2024 to 2025.

Provider size is a comfort, not a criterion. The support relationship that holds is the one matched to your exact modules, versions, and risk.

What to do next

The checklist below sequences a third party support provider selection.

  1. Baseline current support. Scope, cost, and renewal date.
  2. Inventory the estate. Modules, versions, and platforms in scope.
  3. List jurisdictions. Where you need tax and regulatory updates.
  4. Shortlist providers. Two scale providers plus any relevant specialist.
  5. Score on fit. Coverage, security, indemnity, and service levels.
  6. Check references. Customers running your platform today.
  7. Negotiate indemnity. The provider stands behind the support method.
  8. Plan the exit. The path back to Oracle or onward before you sign.
Cover of the Oracle Third Party Support white paper from Redress Compliance

White Paper · Oracle

Oracle Third Party Support

When third party support is the right call for Oracle Database, Apps, and Middleware. Read it free.

Read the white paper

Frequently asked questions

Who are the main Oracle third party support providers?

The market is led by Rimini Street, which is publicly listed, and Spinnaker Support, alongside regional specialists. The right provider depends on coverage of your exact modules and versions, not overall size.

What should you check before choosing a provider?

Check module and version coverage, regulatory update scope, the security model, indemnification, service levels, and references on your platform. Fit to your estate matters more than provider scale.

How do providers secure Oracle without patches?

Independent providers use virtual patching, configuration hardening, and monitoring in place of Oracle patches. They cannot ship Oracle's updates, so they reduce and watch the attack surface instead.

Is third party support for Oracle lawful?

Yes, within defined bounds. The Rimini Street litigation confirmed independent support is lawful while limiting how updates may be created, which is why indemnification language matters in the contract.

Does provider size predict satisfaction?

No. In our selections, coverage of the exact module and version set predicted satisfaction better than size. A specialist that lives in your platform can beat a larger provider with thin coverage.

How long does a provider selection take?

A structured selection typically runs six to twelve weeks, covering baseline, scoping, comparison, references, and indemnification negotiation, depending on the size and complexity of the estate.

Can you switch providers later?

Yes, but plan the exit before you sign. Confirm data and documentation handover, notice periods, and the path back to Oracle so a future switch is not blocked.

How does Redress help choose a provider?

Redress baselines the support, scopes the requirement, and scores providers against your estate and indemnification needs. Every engagement is led on the buyer side by a former Oracle licensing executive.

How Redress engages on Oracle

Redress runs Oracle support provider selection inside the Vendor Shield subscription, the Renewal Program, and the Benchmark Program, led on the buyer side by a former Oracle licensing executive.

Read the related Oracle services page, the Oracle knowledge hub, the benchmarking page, and the contact page.

Run the Oracle Java license calculator against your estate in under five minutes.
Open the Oracle Java License Calculator →
White Paper · Oracle

Download the Oracle ULA Decision Framework.

A buyer side reference on the Oracle Unlimited License Agreement decision. Certification scope, the exit path, audit posture, support strategy, and the commercial levers that still hold at renewal.

Used across more than five hundred enterprise software engagements. Independent. Buyer side. Built for Oracle customers running the next renewal cycle.

Oracle ULA Decision Framework

Open the white paper in your browser. Corporate email only.

Open the Paper →
Editorial photograph of an enterprise office

Your renewal calendar is your leverage.

Renewal in twelve months. Audit notice in the inbox. RFP on the desk. We start where you are.

Oracle support market intelligence, monthly.

Provider scope changes, security models, indemnification terms, selection benchmarks, and support market intelligence from every Oracle engagement we run on the buyer side.