What are Oracle Support Rewards?
Oracle Support Rewards are a program that offsets your annual technology support bill through OCI consumption, giving you a credit for every dollar you spend on OCI that you then apply against eligible support fees. The intent is plain: Oracle wants on premises customers to move workloads to OCI, and it uses the support bill, which runs at roughly 22 percent of license value with annual escalation, as the incentive. Spend on OCI, and a portion of that spend comes back as a reduction in what you pay to keep your existing licenses supported.
The reward is part of the broader cloud cost picture rather than a licensing change. To see how cloud sizing itself works, read counting vCPUs on AWS and Azure, and for the full virtualization and cloud framework see the Oracle virtualization licensing guide.
Support Rewards lower the support invoice for customers with real OCI workloads. They do not lower your license entitlement or your audit exposure, so use them as a cost lever and never as a substitute for a clean compliance position.
How does the OCI offset work?
The OCI offset works by converting your OCI consumption into a credit that reduces your eligible technology support fees, with a higher credit rate for customers who hold an Oracle unlimited license agreement. In practice you commit to OCI usage, you draw down that commitment as you run workloads, and the resulting reward accrues as a deduction against the support renewal. The more you genuinely consume on OCI, the larger the offset, up to the limits set in your agreement.
The mechanics reward customers who already have a cloud strategy and have workloads that fit OCI. They do not reward customers who commit to OCI consumption they cannot use, because unused commitment is spend without a workload behind it. The decision turns on whether the OCI usage is real, which is why this is a finance and architecture question as much as a licensing one.
What does Support Rewards not reduce?
Support Rewards do not reduce your license entitlement, your deployed quantities, or your exposure if Oracle audits you, because the credit applies only to the support invoice and leaves the underlying compliance position untouched. A customer can earn a substantial reward and still carry an unlicensed option, a virtualization shortfall, or a Java exposure that an audit would surface. The reward saves money on support; it does nothing to close a gap between what you deploy and what you are licensed to run.
This distinction matters because Oracle frames the cloud relationship as a partnership while the audit clause in the Oracle Master Agreement remains fully in force. Declining support spend is itself an audit trigger, so a customer cutting support through rewards should keep its compliance position clean. The standing compliance discipline is set out in the repatriation and the license position article.
A worked example of the offset
Suppose a customer pays a technology support bill and runs a growing set of OCI workloads. As OCI consumption accrues, a credit builds against the support renewal, so the net support cash outlay falls while the workloads run on Oracle's own cloud. The table shows the shape of the trade, with figures indicative only.
| Lever | Effect on support bill | Effect on license risk |
|---|---|---|
| Genuine OCI consumption | Reduced via credit | None |
| OCI commitment without workloads | Reduced, but spend wasted | None |
| Cutting support without rewards | Reduced | May trigger an audit |
The reward rate, the eligible fees, and the OCI commitment terms are contract dependent and set in your Oracle agreement. Indicative figures here illustrate the trade only, so confirm the exact terms before relying on a saving.
What is the buyer move?
The buyer move is to model Support Rewards against real OCI demand, take the offset only where genuine workloads justify the consumption, and keep your compliance position clean so the support saving is not undone by an audit finding. Treat the reward as one input into a cloud and support strategy, not as a reason to commit to OCI you do not need. The strongest position is a customer who reduces support cost through rewards while holding a fully defensible license estate.
Your next step
Support cost and compliance should be managed together, not in isolation. An independent buyer side review models your Support Rewards opportunity against actual OCI demand and confirms your estate is clean before you commit. Read the pillar guide for the full cloud and virtualization framework.
Read the Oracle virtualization licensing guide for the complete cloud cost and licensing framework.