Oracle DRCC pricing. Where the money actually goes.

DRCC has one number that matters and three that decide whether it is survivable. The one is the consumption commitment. The three are the drawdown mechanics, the licensing position, and the support rewards you either collect or leave on the table.

This page is the money view. What a Dedicated Region is, and what your building has to provide, sits in the Dedicated Region guide.

What are you actually paying for on a DRCC deal?

You are paying for consumption of OCI services, delivered on hardware Oracle owns and operates inside your building. There is no capital purchase and no separate rack subscription line. The commitment is the product.

That single meter design is what makes DRCC economics different from a database platform, where a fixed rack subscription sits alongside elastic compute. On DRCC, the fixed and the elastic are the same number.

What the commitment covers

• The infrastructure. Racks, servers, storage and network fabric, owned, shipped, installed and refreshed by Oracle.
• The operation. Patching, monitoring, hardware maintenance, feature rollout and secure media handling, run by Oracle.
• The services. The OCI services you provision, metered on the same units as a commercial region and drawn against your credits.

What it does not cover

• Your facility. Floor space, power, cooling, fire suppression and the staff who escort Oracle engineers are your cost, on a different budget line.
• Your circuits. Private connectivity through FastConnect means carriers, cross connects and lead times you buy yourself.
• Licenses you do not bring. If you are not using BYOL, the license is inside the service rate, and that rate is higher.
• Oracle applications. Fusion Cloud and other SaaS are separate agreements at separate rates, and they are excluded from Support Rewards.
• Implementation. Migration, integration and any Oracle professional services are quoted and billed apart from the commitment.

How does DRCC pricing actually work?

You commit to an amount of Universal Credits, and consumption debits that balance as you use services. Oracle's own description is that credits "are debited as you use OCI services over the course of a year", which is the whole mechanic in one sentence.

The commitment is the floor. It is paid whether you consume it or not, and it is the number that decides the business case.

Drawdown and the service period

Three things govern how the balance behaves, and all three are written in your ordering document rather than on a web page.

1. The service period. Credits are typically committed and drawn within a defined period, most often annual. Establish in writing what happens to an unused balance when that period closes.
2. The drawdown rate. Consumption is priced from the rate card in effect, so the rate card and the commitment are two separate negotiations.
3. The ramp. A flat commitment across a five year term assumes a migration that lands on schedule. A stepped commitment tied to named workloads does not.

Ask for the unused credit treatment explicitly. If the answer is that unused credits do not carry forward, that is a legitimate answer, and it is also the strongest argument you have for a conservative floor.

What happens when you overshoot the commitment

You keep your rate. Oracle states on its pricing page that if you consume all your credits before the end of the contract, "you still get the same contracted rate for services", explicitly contrasting this with providers who revert to list price on overage.

That is a genuine advantage and it changes the risk profile. Overshooting the floor is the cheap failure mode. Undershooting is the expensive one.

What happens when you undershoot it

You pay for what you did not use. There is no published mechanism that returns unconsumed commitment, and mid term reductions are difficult because the commitment is tied to installed infrastructure.

• The arithmetic is brutal. A commitment 30 percent above real consumption across a five year term wastes one and a half years of spend.
• The remedy is structural. Negotiate a ramped floor with each step tied to a named workload and a date, not a calendar year.
• The fallback is review points. If a ramp is refused, ask for annual review points with a defined resize window.

Where the published rates actually live

Cloud at Customer and Dedicated Region services appear in Oracle's PaaS and IaaS public cloud global price list PDF, alongside a part number and a metric for each line. Oracle keeps the current documents on its pricing page.

Cite the part number and the revision date of the PDF when you challenge a quote. We explain how to read and diff those documents on the price list PDF page.

What is included in the commitment and what is licensed separately?

The commitment covers the OCI services you consume and the hardware they run on. Everything that is not an OCI service is separate, and that boundary is where business cases quietly fail.

Build your own total cost line that includes the last three rows. In several reviews, the internal hosting cost was large enough to change which option won, and it had never been added to the comparison at all.

How does licensing and BYOL work on DRCC?

Exactly as it does on public OCI. You either take a license included rate, where the Oracle license is inside the hourly price, or you bring your own licenses and take the lower rate. The deployment framework sits in the Oracle Dedicated Region documentation.

License included against BYOL, worked

The comparison is not simply the rate difference. BYOL looks cheaper on the rate card and is only cheaper in total if you already own the entitlements and are already paying their support.

1. Take the license included rate for the service and shape you actually need.
2. Take the BYOL rate for the same shape, and add the annual support you pay on the entitlements you are assigning.
3. If those entitlements would otherwise be terminated, count their support as an avoidable cost, which makes BYOL look worse.
4. If those entitlements are staying anyway for other reasons, count their support as sunk, which makes BYOL look better.

That step three is where most models go wrong. BYOL is only free if the support bill was going to exist regardless.

The policy is not a contract term

Oracle's cloud licensing rules sit in a policy document, not in your ordering document. Oracle can revise it, and it has revised comparable policies before.

• Snapshot it. Save the version in force on the day you sign, with the date, and store it with the contract.
• Reference it. Where the deal depends on a conversion assumption, get that assumption stated in the ordering document itself.
• Do not double count. An entitlement assigned to DRCC cannot simultaneously cover a server on your own floor, and you need a record showing which is which.

Where an Unlimited License Agreement changes the answer

If you hold a ULA, two things change at once. Deployments on a Dedicated Region may or may not count toward your certification, depending on the wording of your agreement, and your Support Rewards accrue at the higher rate.

Read the cloud clause in your own ULA before you model anything. The certification treatment of cloud deployments varies between agreements, and it is not safe to assume the general case applies to you.

Can DRCC consumption cut your on premises support bill?

Yes, and this is the most underused lever in the whole deal. Oracle Support Rewards convert cloud consumption into credits that retire invoices for on premises Oracle technology support.

The published earn rates

Oracle's Support Rewards FAQ states rewards accrue at 25 percent of consumption, or 33 percent for Unlimited License Agreement customers, and may be applied to any eligible open invoice for on premises support of Oracle technology programs.

• At 25 percent. A one million dollar annual DRCC commitment, fully consumed, accrues 250,000 dollars of rewards in that year.
• At 33 percent. The same consumption under a ULA accrues 330,000 dollars.
• Across a five year term. That is between 1.25 and 1.65 million dollars of support invoice relief on the same numbers, which is not a rounding error in any business case.

Note the Cloud at Customer nuance. Oracle states rewards accrue on the portion delivered under Universal Credits, but the base rack subscription portion is not eligible. On DRCC the whole thing is Universal Credits, so the exposure to that exclusion is smaller.

The 12 month expiry that catches people

Rewards are not a bank balance you can leave alone. Oracle states rewards are valid for 12 months from the date they are accrued and deposited, and expire if unused at the end of that period.

1. Map your on premises technology support renewal dates against the months your rewards will land.
2. Confirm which invoices are eligible, since Fusion Cloud applications and third party lines are excluded.
3. Assign one named owner for redemption. In our reviews this was the single most common source of forfeited value.
4. Model rewards as a reduction to the support line, not as a reduction to the DRCC commitment. They are separate ledgers.

White Paper · Oracle

Oracle CIO Complete Playbook

The five year plan to control Oracle spend. Read it free.

Read the white paper

When does the DRCC floor actually pay?

When you would have spent the money anyway, and a rule stops you spending it in a commercial region. Those two conditions have to hold together. Either one alone produces a bad deal.

The break even test, in four lines

1. Take your funded, dated year one workload plan and price it at the DRCC rate card.
2. Compare that figure to the proposed floor. If the floor is materially higher, the gap is pure waste for the whole term.
3. Add your facility cost, circuits and migration effort to the DRCC side.
4. Subtract the Support Rewards you can realistically redeem in the same 12 month windows.

Run the same four lines against a commercial region for the identical workloads. If DRCC only wins once you assume year four consumption, you are not comparing options. You are hoping.

Three signals the floor is too high

• The forecast came from the business case. If the same spreadsheet justified the project and sized the commitment, it is optimistic twice over.
• The ramp is flat. A flat floor across a five year term assumes a migration that does not slip, which no migration has ever done.
• The discount grew with the commitment. A better unit rate bought with a larger floor is only a saving if you consume the larger floor.

Where the common advice on Oracle DRCC is wrong

The common advice is to commit big, because a larger commitment buys a better unit rate and the rate is what you pay forever. We disagree. In the DRCC deals we reviewed, the commitment dominated total cost and the rate improvement never recovered the cost of an unconsumed floor. Oracle's own pricing terms already protect you on the upside, since consuming credits early keeps your contracted rate rather than reverting to list. That asymmetry should push you the other way. Commit small, protect the rate, and let the ramp carry the growth you actually deliver.

Oracle protects you if you consume too much and does nothing if you consume too little. Read that asymmetry as instruction, and size the floor low.

What should a buyer do next?

1. Build a year one consumption forecast from funded, dated workloads only, separate from the business case forecast.
2. Price that forecast against the published rate card and compare it to the proposed floor. Quantify the gap over the whole term.
3. Negotiate the commitment and the rate card as two separate items, and ask for a rate hold for the term.
4. Ask in writing what happens to unused credits at the end of each service period.
5. Count owned entitlements and model BYOL against license included, including the support you will still pay.
6. Model Support Rewards at your applicable rate and map redemption against your support renewal calendar.
7. Add facility, circuits and migration cost to your side of the comparison.
8. Get ramp, review points, refresh, removal and exit terms written before signature.
9. Benchmark the same workloads in a commercial region and keep that comparison on the table.

Related reading

• Dedicated Region guide. What it is and what your building must provide.
• Cloud at Customer against a Dedicated Region. Which platform fits which problem.
• Reading the Oracle price list PDF. Where the part numbers and rates come from.

Frequently asked questions

How is Oracle DRCC priced?

On Universal Credits against a consumption commitment. There is no separate hardware line. You pay the committed amount whether or not you consume it, and services debit that balance at the rates in your ordering document.

What happens if we consume more than the commitment?

You keep your contracted rate. Oracle states on its pricing page that consuming all your credits before the end of the contract does not push you to list price, which it contrasts with other providers. Overshooting is the cheaper failure mode.

What happens if we consume less than the commitment?

You pay for it anyway. There is no published mechanism that refunds unconsumed commitment, and mid term reductions are hard because the commitment is tied to installed infrastructure. This is why the floor should be sized to funded demand only.

Does DRCC consumption earn Oracle Support Rewards?

Yes. Oracle publishes an accrual of 25 percent of consumption, or 33 percent for Unlimited License Agreement customers, applied to eligible open invoices for on premises Oracle technology support. On Cloud at Customer, the base rack subscription portion is excluded, but a Dedicated Region is consumption throughout.

How long do Support Rewards last?

Twelve months. Oracle states rewards are valid for 12 months following accrual and expire if unused. Map your support renewal dates against the months rewards will land, and give one named person responsibility for redemption.

Can we use BYOL on DRCC?

Yes, for eligible programs, at a lower service rate than license included. The saving is real only if you already pay support on those entitlements for other reasons. Add that support cost to the BYOL side before you compare.

Where can we see the published DRCC rates?

In Oracle's PaaS and IaaS public cloud global price list PDF, which carries a part number and a metric for each line and includes Dedicated Region and Cloud at Customer sections. Cite the part number and the revision date of the document when challenging a quote.

Can we reduce the DRCC commitment during the term?

Rarely, and never easily. The commitment funds dedicated infrastructure already installed in your building. Build ramp steps, review points and a resize window into the original deal, because the time to negotiate the floor down is before signature.