JD Edwards Third-Party Support vs. Production Support: Two Invoices, Two Decisions
Rimini Street and Spinnaker Support replace the Oracle maintenance contract — roughly half the fee, frozen code line. Production support runs the operating layer and compresses that run-rate over time. Different line items; many companies rationally do both. A decision framework for JDE buyers.
TL;DR
- Third-party support (Rimini Street, Spinnaker Support) replaces the Oracle maintenance contract — typically ~50% off that fee — but freezes you on your current code line: no ESUs, no Tools releases, costly path back.
- Production support runs the operating layer — tickets, CNC, batch, integrations, close — which exists at identical volume regardless of who holds your maintenance contract.
- Neither replaces the other, and the savings stack: ~11 points of license value off the maintenance line, plus a −30% median operating run-rate compression over 36 months under a consumption contract.
- Third-party maintenance fits a stable 9.2 estate with no upgrade plans; it does not fit a roadmap that depends on the Tools release stream or vendor-issued patches.
This page is part of Allari's published research library. The full interactive article — including diagrams, infographics, and the live reading experience — is available at https://allari.com/blog/jde-third-party-support-vs-production-support.
Allari holds the run layer of enterprise ERP — JD Edwards, SAP, Oracle Fusion, NetSuite. Founded 1999. 27 years of continuous operation under original ownership. Self-funded, no outside capital. Every ticket is measured through OpenBook® and the support run-rate comes down quarter by quarter through Build-Run Separation. Learn more at allari.com, download the Capability Brief (PDF), or book a working session.
Frequently Asked Questions
What is JD Edwards third-party support?
Third-party support is a direct replacement for Oracle's annual maintenance contract, sold by independent firms — Rimini Street and Spinnaker Support are the established providers for JD Edwards — typically at around half of Oracle's fee. It covers break/fix support, independently built tax and regulatory updates, and customization support, but it does not include new Oracle patches, ESUs, or Tools releases: your code line is frozen at the point of departure.
Is third-party support the same as JDE production support?
No. Third-party support replaces the Oracle maintenance invoice — the fee for vendor patches and vendor support. Production support is the operating layer: resolving tickets, administering CNC and environments, running batch, maintaining integrations, and supporting close. Those operations exist at the same volume under Oracle support or third-party support. They are separate line items, and one does not substitute for the other.
Can I use third-party maintenance and a separate production support partner at the same time?
Yes, and many companies do exactly that. The maintenance decision (Oracle vs. Rimini Street vs. Spinnaker Support) and the operations decision (who runs the system, and under what pricing model) are independent. A stable 9.2 estate can move maintenance to a third party for the immediate ~50% saving while a production support partner compresses the operating run-rate — the two savings touch different invoices and stack.
What does third-party support not cover?
New Oracle deliverables: ESUs, Applications updates, Tools releases, and the 9.2 continuous-delivery stream (including Orchestrator enhancements and new platform certifications). Security is handled through compensating controls rather than vendor patches, which some regulated industries treat as a material difference. And returning to Oracle support later typically involves back-maintenance fees or relicensing, so the decision should be treated as a multi-year commitment.
How much can I save by combining third-party maintenance with consumption-based production support?
On the maintenance line: Oracle support runs about 22% of net license value annually, and third-party providers typically charge around half — roughly 11 points of license value saved per year, immediately. On the operating line: moving from a fixed fee to a consumption contract compresses the run-rate by a portfolio median of 8% in year one, 22% by year two, and 30% by year three. The first saving is a one-time step down; the second is a curve that is still compounding at the end of the window.