The support base is the largest cost a certified estate carries. Oracle Support Rewards offers one of the few levers that can bend it down, but only where the OCI workload behind it makes sense on its own.
By Daniel Voss · Ex Oracle LMS · 4 June 2026
Oracle Support Rewards lets you earn credits on OCI consumption and apply them against your technology support bill, which after certification is the largest running cost you carry. The offset is real but conditional: you only earn it on OCI spend you actually use, so it pays when the workload is one you would run anyway or one that is genuinely cheaper on OCI. Routing workloads to OCI purely to chase the reward can cost more than it saves. The rate and eligibility depend on your specific agreement, so model the offset against the true cost of the move.
After certification your support continues at the ULA level and does not fall because you certified. It is the dominant line in the running cost of the estate, and it compounds with a small annual uplift. Most of the obvious ways to reduce it run into the matching and repricing rules, which can turn an apparent saving into a wash. That is what makes Support Rewards interesting: it reduces the effective support cost without touching the support agreement itself, by crediting a separate stream of OCI spend against the bill.
The programme is worth understanding precisely because clean reductions to the base are scarce. It does not require you to cancel support, restructure a set, or trigger a reprice. It works alongside the existing support relationship, applying earned credits to lower what you actually pay. For an organisation whose five year cost model is dominated by the base, a lever that sidesteps the pricing rules is rare enough to take seriously.
You earn a reward for every unit of qualifying OCI consumption, and you apply that reward against your Oracle technology support invoice. The earning rate can be higher for organisations with certain agreements in place, so the value of the offset is not uniform across customers. The mechanics are straightforward, but the economics turn entirely on one question: would you run the OCI workload regardless?
The offset is real value when the OCI consumption is something you would do anyway. A workload that belongs on OCI for technical reasons, a migration already planned, or a new project that fits OCI well all generate consumption you were going to pay for, and the support reward then reduces your support bill as a bonus on top. In this case the offset is close to free, because the spend that earns it was always going to happen.
The offset turns negative when you move a workload to OCI only to earn the reward. If running the workload on OCI costs more than running it where it sits today, and the only justification is the support credit, you can spend more on consumption than you save on support. The reward is a discount on a bill you create. Chasing it without the workload making sense on its own is paying to save, which is rarely a saving at all.
Let the workload decide, then take the reward. Support Rewards is a strong lever when it rides on OCI spend you would commit to anyway, and a weak one when it drives the decision. Start from where each workload genuinely belongs on technical and commercial merit. Where that lands on OCI, the support offset is real money you should claim. Where it does not, the reward is not a reason to move. The discipline is to keep the offset as the consequence of a sound decision, never the cause of an unsound one.
Consider an anonymized software company that had a development and test estate it was already planning to consolidate onto OCI for unrelated reasons. Because the consumption was happening regardless, the Support Rewards credits it earned reduced its technology support bill at no extra cost, bending the support base down in its five year model. A second anonymized company, seeing the same headline rate, shifted a stable production workload onto OCI purely to earn the reward, and found the consumption cost exceeded the support it offset. The figures are indicative, but the pattern is the rule: the offset paid where the move was justified anyway and cost money where it was not. The reward was identical. Only the underlying decision differed.
Support Rewards is one offset among several, and it only counts inside a full view of the running cost. See how the support base behaves and why it dominates in the cost model of a certified estate, understand the pricing rule that constrains direct reductions in terminating support on unused licenses, and ground your post certification cost work in our post certification audit defense guide.
Book a ULA assessment and we will model where Support Rewards genuinely lowers your support base and where the OCI move would cost more than it saves.