Third-party support replaces the first invoice. Production support runs the second. They are different line items, cut by different mechanisms, and — this is the part the sales conversations on both sides tend to blur — neither one replaces the other. Many companies rationally buy both.
What third-party support actually is
Third-party software support firms — Rimini Street and Spinnaker Support are the established names for JD Edwards — sell a direct substitute for Oracle's annual maintenance contract, typically at around half the price. For a company paying Oracle 22 points of license value a year, that is roughly 11 points back, every year, on a line item many CFOs had written off as fixed.
What you get for it, in general terms:
- Break/fix support on the release you are running, usually with responsive SLAs and senior engineers.
- Tax, legal, and regulatory updates built independently of Oracle — a genuine engineering capability, and the part of the offering skeptics most underestimate.
- Support for customizations, which Oracle standard support generally excludes.
- Security guidance through compensating controls and virtual-patching approaches rather than vendor-issued patches.
What you give up
The tradeoffs are just as concrete, and a fair evaluation prices them rather than waving at them:
- No new Oracle deliverables. No ESUs, no Tools releases, no application updates. Your code line is frozen where it stands on the day you leave Oracle support.
- The 9.2 continuous-delivery stream stops for you. Orchestrator enhancements, UX updates, and platform certifications arrive through Tools releases you can no longer take.
- Security posture changes character. Compensating controls can be genuinely effective, but they are a different assurance model than vendor patches, and some auditors and regulated industries treat that difference as material.
- The road back has a toll. Rejoining Oracle support later typically means back-maintenance fees or relicensing. Third-party support is reversible in principle and expensive to reverse in practice — treat it as a multi-year commitment, not a trial.
What production support is — and why it is untouched by all of the above
Production support is the operating layer: the daily queue of incidents and requests, CNC and environment administration, overnight batch runs and their failures, the EDI and banking integrations, the elevated coverage at period-end close. This work exists at identical volume whether your maintenance check goes to Oracle or to Rimini Street. Nobody's maintenance contract reruns your failed UBEs at 2 a.m.
To be explicit about where Allari sits: Allari is not a third-party support provider and does not replace your Oracle contract. That is Rimini Street's and Spinnaker Support's business, and they are credible at it. Allari runs the operating layer — under either maintenance arrangement.
When third-party maintenance makes sense — and when it doesn't
It tends to make sense when: you are stable on 9.2 (or a release you have deliberately chosen not to leave), there is no upgrade or migration in the planning window, the estate is customization-heavy so vendor patches were touching less of what you actually run, and the freed maintenance budget has a named destination.
It tends not to when: your roadmap depends on the Tools release stream — Orchestrator, UX, new platform certifications; a re-platforming or upgrade is plausible within the commitment horizon; or your compliance regime effectively requires vendor-issued patches. Oracle's published support commitment for EnterpriseOne runs through at least 2037, so "Oracle is abandoning JDE" is not, by itself, a reason to leave — the decision should be made on your roadmap, not on fear.
The honest summary: third-party support is a bet that your current release is where you want to live. If that bet is sound, the savings are real and immediate.
How the two savings stack
They stack because they touch different lines. A worked example, in license-value terms:
One is a coupon; the other is a curve. The coupon is bigger on day one. The curve keeps going. A CFO does not have to choose — the point of separating the line items is seeing that the two decisions are independent, and each should be made on its own merits.
