OCI Support Rewards is an Oracle program that gives you credit toward your Oracle technology software support invoices based on how much you spend on OCI. The standard earn rate returns 25 cents of support credit for every dollar of eligible OCI usage, and customers who hold an Oracle Universal Credits commitment earn at a higher rate of 33 cents per dollar (figures indicative, confirm against your current Oracle agreement). Those credits are applied against the annual support fees you already pay on licensed Oracle technology software such as the database, middleware, and options. For an enterprise carrying a large on premises Oracle support bill, the rewards can offset a meaningful slice of a cost that would otherwise never fall, which is why Support Rewards belongs in the OCI business case, not as an afterthought.
Here is how the mechanism works, what counts, and how a buyer sizes OCI usage and commitments to capture more of it without overspending.
What exactly does OCI Support Rewards reduce?
It reduces your Oracle technology software support fees, the recurring annual maintenance you pay to keep licensed Oracle software supported and patched. It does not reduce your OCI bill itself, and it does not apply to applications support such as Oracle E Business Suite or other Oracle application maintenance. The distinction matters for the business case: OCI Support Rewards takes a fixed, predictable, and historically rising support line and lets your cloud consumption push it down. Because that support line sits outside the cloud budget, finance teams often miss it entirely when they evaluate whether to run Oracle workloads on OCI rather than a hyperscaler.
How does the earn rate actually work?
The program calculates rewards from your eligible OCI usage over a period and accrues credit at the applicable rate. Customers consuming OCI on the standard pay as you go basis earn at the base rate, while customers who hold an annual Universal Credits commitment earn at the higher rate, because Oracle rewards the committed spend that gives it forecast certainty. The credits accumulate and are applied to qualifying Oracle technology support invoices as they come due, so the value lands as a lower support payment rather than a cash refund. Treat the rate as indicative and verify it against your own ordering document, because Oracle adjusts program terms and your contract may carry specific language.
The practical consequence is that the effective cost of running an Oracle workload on OCI is lower than the OCI list price alone suggests, because part of that spend returns as a reduction elsewhere. A buyer who models OCI cost in isolation, ignoring the support offset, will undervalue the platform for exactly the Oracle centric workloads it is built to win.
How do you maximise Support Rewards without overspending?
The goal is to capture more offset from spend you would make anyway, never to inflate OCI usage to chase credits. Three levers matter. First, concentrate eligible Oracle workloads on OCI where they run well, because the more genuine consumption flows through OCI, the more support credit accrues. Second, where a Universal Credits commitment fits a defensible forecast, the higher committed earn rate is worth the structure, but the commitment still has to stand on its own use it or lose it logic. Third, time the application of credits against your largest support invoices so the offset lands where it reduces the biggest fixed payment. Crucially, never let the reward tail wag the dog: spending an extra dollar on OCI to earn a fraction of a dollar back in support credit is a loss, not a saving.
How does this change the OCI versus hyperscaler decision?
For Oracle licensed workloads, Support Rewards is a structural advantage that AWS, Azure, and GCP cannot match, because none of them can credit your Oracle support bill. When you compare the true cost of running an Oracle database on OCI against the same workload on a hyperscaler, the right OCI figure is the run rate minus the support offset, set against the hyperscaler run rate plus whatever Oracle licensing penalty applies there. That comparison frequently favours OCI for database heavy estates, while general purpose and cloud native workloads may still be cheaper elsewhere. The buyer side discipline is to run the comparison workload by workload with the offset included, not to let either an Oracle sales motion or a hyperscaler preference decide it.
Where Support Rewards fits the wider OCI cost program
Support Rewards is one input among several. It interacts with how you size a Universal Credits commitment, how you use license included versus bring your own license pricing on database services, and how you forecast Oracle workload consumption. Read it as part of the whole picture in our OCI cost optimization guide, understand the commitment mechanics in Universal Credits explained for buyers, and make sure the underlying bill is legible by reading your OCI bill line by line before you model the offset.
Frequently asked questions
How much does OCI Support Rewards give back?
Does Support Rewards reduce my OCI bill?
Does Support Rewards apply to Oracle applications support?
Put the support offset in your OCI business case
We model OCI Support Rewards alongside the OCI run rate so the true cost of your Oracle workloads is clear before you commit, and we negotiate Universal Credits from a defensible forecast as an independent advisory that takes zero provider commissions. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee scoped up front or a no risk Gainshare basis. Download the OCI cost guide, or read more on decoding OCI credits and promotions.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.