Session 16 called it the alternatives horizon; this session maps it. What Rimini Street and Spinnaker Support actually sell at roughly half the Oracle fee, and what they can never provide. The decade of Oracle versus Rimini Street litigation that punished specific practices and left the model itself standing. The no vendor patches question answered with compensating controls instead of slogans, the fit profile that separates frozen estates from actively developed cores, the bridge strategy that funds migrations from the support savings, and the switch executed with the reinstatement door priced before anyone signs.
The presenter in this session is an AI generated avatar. The curriculum and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.
A taught session with three knowledge checks: the is it legal executive question answered without hedging, the no vendor patches objection weighed as a per workload tradeoff with compensating controls, and the CFO's move everything proposal corrected to the split estate. It closes with one four workload portfolio assigned honestly, banking $190K a year without losing wanted coverage anywhere.
The full narration of this session, section by section, for reading and reference.
Welcome back, session nineteen of forty. Twice this module, an alternative has appeared at the edge of the frame: third party support, roughly half price, disciplining every renewal conversation just by existing. Today it gets the full hour, because it deserves one, and because almost nobody discusses it honestly. Oracle's account teams describe it as reckless and legally dubious. The providers describe it as free money. Both descriptions are marketing, and the truth, as usual, is more useful than either: third party support is a specific, legal, well established trade, half the price and better service on what you already run, in exchange for the vendor's patch and version stream, and whether that trade wins depends entirely on the workload. Today: the model, what providers actually deliver, the legal history that settled the big question, the security debate handled with engineering instead of slogans, the fit profile, the bridge strategy that funds migrations, and the execution mechanics. By the end, you'll be able to evaluate it properly, and even if nothing ever moves, that evaluation pays at every renewal. Let's look at it straight.
Five takeaways. One, you'll explain the model, what firms like Rimini Street and Spinnaker Support actually sell, and just as important, what they structurally cannot sell, because the boundary is the whole decision. Two, you'll state the law accurately: the is it legal question has a clean answer with a decade of litigation behind it, and you'll be able to give that answer to an executive in two sentences. Three, you'll handle security honestly, the no vendor patches objection weighed with compensating controls and patching history, per workload, the way security decisions actually get made. Four, you'll match the fit: the frozen and the migration bound on one side, the actively developed and the subscribed on the other, and the split estate as the usual right answer. And five, you'll use it either way: as an executed move for the workloads that fit, or as the priced alternative that turns every renewal conversation honest, which, remember, was the retention counter's entire mechanism last session. The alternative you never price is the leverage you never have. Let's price it.
Four numbers. Roughly fifty percent, the standard third party price point, half the Oracle fee for the same estate. Hold that against session sixteen's compounding table and the number gets loud: a five hundred thousand dollar stream becomes two fifty, every year, without the uplift escalator. Fifteen plus years, the age of the independent support industry at enterprise scale. This is not a startup experiment; thousands of Oracle and SAP estates run on it, including household names you'd recognize from the case studies in today's reading. One, the landmark legal saga, Oracle versus Rimini Street, which we'll cover properly, because its outcome is the industry's charter and every executive will ask about it. And zero, the change to your license position: the licenses remain yours, perpetual, exactly as session seven classified them, the compliance obligations continue, and Oracle's audit rights continue, which means module one's records discipline retires never, a point we'll repeat because it is the most commonly forgotten fact in every third party conversation. Session sixteen called this the alternatives horizon. Today the horizon gets a map.
What the providers actually sell, five cards. First, break fix without source access: named engineers who diagnose and resolve issues in your environment, and here's the part that surprises people, typically including your custom code, the extensions and integrations Oracle's standard support always excluded. For heavily customized estates, third party service is often genuinely better, not just cheaper. Second, tax and regulatory updates: independent research teams keep payroll, tax, and compliance content current, which is the one update stream frozen ERP estates actually consume. Third, old versions, indefinitely: the release Oracle moved to sustaining support, full price for no patches, gets full service from the provider for as long as you choose to run it. The forced upgrade clock stops. Fourth, security by compensation: no Oracle patches, and instead virtual patching, hardening, and monitoring around the frozen core, we'll examine that trade properly in the security check. And fifth, the card that matters most, what is never included: new Oracle versions, Oracle's patches, and the practical upgrade path. Those flow only from Oracle support. That's the trade, whole and honest: half the price, arguably better service on what you have, no road to what Oracle ships next. Everything else in this session is detail on that sentence.
The comparison table, five dimensions, no thumb on the scale. Annual cost: Oracle at twenty two percent of net, compounding upward at the uplift; third party at roughly half the current Oracle fee, and typically without the automatic escalator. New versions and patches: included with Oracle while the product is current; never included with third party, the version you hold is the version you keep, permanently. Old version coverage, and watch this row invert: Oracle's service declines through extended to sustaining, less and less for the same price; third party provides full service on old versions indefinitely, so for aging estates the cheaper option is also the better service. Custom code: outside Oracle's standard scope, typically covered by third party, the second inversion. And the return path: from Oracle support there's nothing to return from; from third party, going back to Oracle means session eighteen's reinstatement mathematics, the back fees and the penalty, so the door mostly swings one way. Read the table honestly and no column wins in general. The left column wins for platforms consuming Oracle's stream; the right column wins for platforms that stopped consuming it years ago. Which means the entire decision is the fit profile, and we're getting there. First, the question every executive asks within thirty seconds. Knowledge check one.
Knowledge check one, the executive question. Is third party support even legal? A, no, only Oracle may support Oracle software. B, yes, unambiguously: the model is lawful, established by long litigation, though specific improper practices by one provider were penalized. C, it operates in a legal gray zone best avoided. Or D, only for companies outside the United States. Pause here. What did the courts actually decide?
The answer is B, and you should be able to deliver it without hedging, because hedged answers to this question cost companies millions in avoided savings. The Oracle versus Rimini Street litigation ran more than a decade, through multiple rounds and appeals, and became the industry's defining case law. What it established: providing independent support for software a customer lawfully licenses is legal. The model stood. What it punished: specific historical practices in how one provider copied and hosted Oracle's support materials, and those rulings forced process changes across the whole industry, which, from a buyer's perspective, made the industry cleaner. So the executive summary is two sentences: the model is settled law; the diligence question is whether a specific provider's current processes comply, and mature providers answer that with documentation on request. A is the impression years of vendor messaging was built to create, and it misstates the law. C converts a resolved question back into fog, and this course has priced what fog costs often enough. D invents geography. And carry the corollary everywhere: on third party support, your licenses, compliance obligations, and Oracle's audit rights all continue unchanged. The support contract moved; the license relationship didn't. Records discipline, forever. The history itself, briefly, next.
The legal history in four sentences, because your executives will want the shape of it. The saga: Oracle sued Rimini Street in 2010, and the litigation ran across multiple rounds, verdicts, appeals, and injunction proceedings for over a decade, producing the case law the entire industry now operates under. What stood: the core model, independent engineers supporting software the customer lawfully licenses, working from the customer's own entitled materials, was never struck down, and courts affirmed explicitly that lawful competition in the support market is exactly that, lawful. What fell: specific copying and hosting practices from the provider's earlier era, cross use of one customer's materials for another, hosting Oracle software on provider systems in ways the licenses didn't permit, were found infringing and penalized, with damages and injunctions that reshaped industry processes. And what it means for you: the question is not whether third party support is legal, that's answered; the question is whether a specific provider's current processes are clean, which is a due diligence checklist, not a legal risk. Ask the provider to walk you through their compliance with the rulings. The good ones have the answer rehearsed, documented, and slightly weary, because everyone asks. Now, the harder objection. Security.
Knowledge check two, the real objection. Without Oracle's quarterly security patches, are we exposed? A, no, patches never mattered anyway. B, yes, fatally: unpatched Oracle software cannot be run responsibly. C, it is a real, manageable tradeoff: compensating controls and honest workload selection decide it, and the answer differs per system. Or D, only if the provider is small. Pause here, and ask: what was the frozen estate's patching reality before the switch?
The answer is C, and the reasoning is a template for every security tradeoff you'll ever referee. Start by granting the objection its truth: no new Oracle security patches will arrive, ever, and option A's breeziness about that is how bad decisions get made. But then apply context, because security decisions live in context: the natural third party candidates are frozen estates whose own patching records show no quarterly update applied in years. Those systems are already living without the thing being given up; the invoice just hasn't noticed. For them, the provider's compensating controls, virtual patching at the network and perimeter layer, configuration hardening, monitoring guidance, often improve the effective security posture over the do nothing baseline that actually existed. B overshoots by treating vendor patch currency as the only legitimate security model. It isn't: isolation, segmentation, and compensating controls are real engineering, security teams approve such architectures every day, and a frozen internal system behind three network layers is a different risk than an internet facing one. The discipline is per workload assessment: exposure, data sensitivity, actual patching history, available mitigations, with security at the table from day one, session eighteen's sign off order. Systems genuinely consuming Oracle's patch stream stay put. Systems that stopped consuming it years ago are candidates. The question was never patches or no patches. It was invoice or no invoice, for patches nobody applies. Now, the fit profile in full.
The fit profile, four categories, and this slide is the entire decision. Fits: the frozen estate. Stable versions, no upgrade plans, sustaining tier invoices, the fourth category from session sixteen's audit, which, you may now notice, was built to feed this session. These systems surrendered Oracle's value proposition years ago and kept paying full price for it. Fits: the migration bound. Systems with a real retirement or replatform date, where the question is not whether to leave Oracle's stream but how cheaply to exit. Full support until the end, at half price, no forced upgrades on the way out, we'll build this into the bridge strategy next. Does not fit: the current estate. Workloads that genuinely consume new versions, quarterly patches, and certifications, the actively developed ERP, the database platform with an upgrade on the roadmap. The trade takes away exactly what these systems use, and no discount compensates for a roadmap you need and can't have. And cannot fit, note the different verb: subscriptions. SaaS and cloud services embed support inside the subscription; there is no separate support contract to move. Third party support is a perpetual license play, full stop, which is one more quiet argument for the perpetual estate you already own. Four categories, every workload lands in exactly one, and the audit already did the sorting. The bridge, next.
The bridge strategy, the classic deployment, five cards. The setup: a stable Oracle estate with a genuine migration destination, cloud native replacement, SaaS successor, different platform entirely, sitting three to five years out, currently unfunded or underfunded. Sound familiar? It's most large IT roadmaps. The move: the frozen estate switches to third party support at its renewal dates, whole sets, session seventeen rules, security signed off per workload. The funding, and here's why this play gets board approval: the fifty percent saving, often seven figures annually on a large estate, funds the migration program that retires the very estate being supported. The support line item becomes the transformation budget. The endgame: systems retire off third party support directly into decommissioning, and the one way door problem evaporates, reinstatement mathematics only matter if you're going back, and nobody is going back, the destination was the point. And the discipline, because every elegant strategy has a failure mode: the bridge needs a real destination and a real date. Without them, it's not a bridge, it's just cheaper stagnation, comfortable, permanent, and quietly accumulating the risks of an aging estate with no exit. A bridge to somewhere: excellent strategy. A bridge to nowhere: a decision postponed at half price. Execution mechanics, next.
Executing a switch, five disciplines, most of them familiar because this is module four's machinery pointed at a new destination. One, move whole sets: the switch is a support termination toward Oracle, so session seventeen's rules govern, complete sets, renewal dates, written notice per the policies. The set map decides what can move cleanly, as it decides everything in this module. Two, harvest while entitled: in the months before Oracle coverage ends, download the patches, updates, and documentation your licenses entitle you to. You're entitled while supported; after the date, the portal closes. Do it systematically, catalogued, because that archive is part of what the provider will support you on. Three, onboard the provider early: environment discovery, knowledge transfer, and case history migration start before Oracle coverage ends, so day one on third party support has no gap. The mature providers have this down to a program; let them run it. Four, keep every record: this cannot be said often enough, the licenses did not move, the audit exposure did not move, and module one's evidence discipline continues untouched. An estate that relaxes its records because support moved has misunderstood what moved. And five, expect the campaign: a third party switch on real money gets Oracle's attention, retention offers, sharpened audit posture, relationship pressure through executives. All of it anticipated, all of it manageable, and the records are what make it boring. Final check, and it's the CFO's question.
Knowledge check three. The CFO, delighted by the economics, proposes moving the entire Oracle estate to third party support, including the actively developed ERP platform. Right call? A, yes, half price on everything is the whole point. B, no: fit is per workload, the frozen estate moves, and the actively developed platform that consumes patches and versions stays on Oracle support. C, no, because third party support is never advisable. Or D, yes, provided the switch happens mid term for speed. Pause here. Which workloads consume what the trade gives up?
The answer is B, and the CFO's enthusiasm is worth honoring even while correcting it, because the economics are real, that's what makes over application the characteristic failure. Walk the estate: the frozen half, old versions, no upgrades planned, sustaining invoices, moves, saves half, and probably gets better service, with security's per workload blessing. The actively developed ERP is different in kind: it applies quarterly patches, it has a version upgrade on the funded roadmap, it needs new certifications as the stack around it moves. Every one of those flows only from Oracle support. Moving it saves half the fee and forfeits the entire roadmap, a trade the platform's own plans forbid, and rebuying the path later means reinstatement mathematics. So the answer is the split estate: fit assessed per workload, sets separated accordingly, session seventeen's architecture proving its worth yet again. A is the inflated basket's cousin, enthusiasm applied uniformly where analysis should discriminate. C burns seven figures of legitimate savings to avoid making distinctions, the opposite error, equally expensive. D trips on mechanics we've now covered twice: switches execute at renewal dates with notice, and mid term gestures forfeit paid coverage for nothing. And the split carries one more virtue: it's the honest answer to Oracle when the campaign arrives. The workloads that value your support still buy it; the ones that stopped receiving value stopped paying. That sentence survives every escalation, because it's simply true. Let's see the split, priced.
One estate's support portfolio, assigned honestly, four workloads. The ERP platform, active: patches applied on schedule, an upgrade planned for next year. It stays on Oracle support, four hundred thousand a year, and last session's negotiation capped its uplift at zero for three years. Right platform, right stream, right price. The legacy database estate: frozen four years, sustaining tier, the audit's fourth category. It moves to third party: two hundred twenty thousand becomes one hundred ten, service arguably improves, security signed off on the isolation architecture. The retiring middleware: migration funded, three year runway to decommissioning. The bridge: one hundred sixty becomes eighty, and the eighty thousand annual saving flows directly into the migration budget that retires it. No reinstatement question, because the road ends in retirement. And the cloud subscriptions: support embedded, nothing to move, unchanged, the category that cannot fit. Net effect: one hundred ninety thousand dollars a year recovered, the ERP's upgrade path untouched, every security decision made per workload with signatures, and a migration part funding itself. Notice what made the split possible: the audit sorted the estate, the set map made the moves clean, and the fit profile assigned each workload honestly. The alternative, deployed like an instrument instead of an ideology. That's the session.
Session nineteen in three sentences. One, third party support trades Oracle's patch and version stream for roughly half the price and often better service on what you already run, a trade that is settled law, delivered by a mature industry, and entirely workload dependent. Two, the fit is the frozen and the migration bound, never the actively developed or the subscribed, and the security question is answered per system, with compensating controls weighed against actual patching history rather than slogans in either direction. Three, whether or not a single workload ever moves, the priced alternative disciplines every renewal conversation you will ever have, which is why evaluating it honestly is among the highest leverage hours in this course. Next session closes module four with the event the whole module has been arming you for: the renewal negotiation itself. The timeline that opens at T minus six, the full menu of winnable asks, the leverage inventory, the escalation ladder past the renewal desk's scripted no, and the multi year strategy. Every tool from sessions sixteen through nineteen, deployed on the one date a year that matters. See you in session twenty.
Homework, about an hour. One, run the fit profile: every workload from your baseline audit marked fits, does not fit, or cannot fit, starting with the sustaining tier lines session sixteen flagged, they're the natural first candidates. Two, price your alternative: the fitting candidates at half their current fees, totaled. That number is renewal leverage from the moment it exists on paper, whether or not anyone ever moves, and next session spends it. Three, check the patch reality: for each candidate, when was the last Oracle patch actually applied? Pull the change records. Systems years behind are already living the tradeoff, unpriced, and that fact reframes the security conversation before it starts. Four, sketch one bridge: your most migration ready estate, its destination, its date, and what half its support fee would fund. If the numbers make the migration self funding, you've found a board slide. And five, draft the due diligence list: five questions for any provider, process compliance with the case law, references at your scale and stack, security controls in detail, onboarding methodology, and exit terms. Having the list ready makes the eventual conversation professional instead of exploratory. That's the hour. See you in session twenty, where module four closes.
Five reads, all free on redress compliance dot com. First, dropping Oracle support and reinstatement, the one way door in full contractual detail, today's return path question answered properly. Second, the Avis case study, eight million dollars saved over three years with third party support on a WebLogic estate, the bridge strategy executed at scale with real numbers. Third, the Adecco case study, a hybrid support strategy saving twelve million euros, the split estate worked at a global company, today's final check in the wild. Fourth, the American Airlines case study, twelve million dollars off Oracle spend over three years, support optimization as a full program with the alternative in its toolkit. And fifth, optimizing your Oracle license footprint before renewal, where the third party option sits inside the wider reduction program. That's session nineteen. A legal model, an honest trade, a fit profile that does the deciding, a bridge that funds its own destination, and an alternative that disciplines every renewal just by being priced. One session left in module four: the negotiation. See you there.