Oracle Dedicated Region. The commitment and the building.

An Oracle Dedicated Region is two decisions bolted together. You commit to years of consumption, and you commit to hosting Oracle owned racks in a room that meets Oracle's environmental specification. Most buyers negotiate the first and discover the second in the site survey.

That sequence is backwards. The building decides whether the deal is deliverable at all, and the facilities lead is almost never in the room when the commitment gets signed.

What does Oracle actually install when you buy a Dedicated Region?

Oracle installs a complete, self contained OCI region inside your facility and then runs it as a managed service. You do not buy the hardware. Oracle owns it, ships it, racks it, patches it and refreshes it.

On its Dedicated Region page, Oracle describes an expandable footprint starting as small as three racks and scaling to more than 450, delivering over 200 OCI services behind your perimeter.

How small is the smallest Dedicated Region now?

Smaller than most buyers assume, and getting smaller. The entry configuration has been cut twice since launch, which changes who can credibly consider it.

• June 2022. Oracle announced a redesigned OCI Dedicated Region requiring 60 to 75 percent less data center space and power on average, at a stated figure of around 1 million dollars a year for a typical customer.
• September 2024. At its annual conference Oracle announced Dedicated Region25, starting at only three racks with a 75 percent smaller launch footprint and deployment measured in weeks.
• Today. The three rack entry point and the 450 rack ceiling are both published on Oracle's product page, so the range is public even though your price is not.

The practical effect is that the room requirement is now within reach of a mid sized enterprise data hall. The commitment requirement moved much less.

What is not in your region on day one?

Parity with public OCI is not instant, and the region is deliberately isolated. Oracle's own Dedicated Region FAQ is explicit that the region is managed through its own console and is not connected to Oracle's commercial public cloud regions.

• Service catalog lag. New OCI services land in commercial regions first. Ask for the current Dedicated Region service list in writing, not the marketing count.
• Separate control plane. Identity, tenancy and billing are managed separately. Cross region features that assume a public region may simply not apply.
• Connectivity is your job. Oracle points at FastConnect for dedicated private connections, which means circuits, carriers and lead times you procure yourself.
• Availability target. The FAQ cites a compute availability objective of 99.95 percent across fault domains, which is a service target, not a promise about your building.

What must your data center provide before Oracle will build it?

You provide the room, the power, the cooling, the network drops and the people. Oracle provides and operates everything inside the racks. That split is stated on Oracle's product page and it is the part of the deal that has no negotiation lever at all.

The environmental numbers your facilities lead will be asked to sign

Oracle publishes the engineering specification for the rack families that go into these deployments. The numbers below come from Oracle's site requirements documentation and its site checklists.

• Rack envelope. Roughly 2000 mm high, 601 mm wide, 1237 mm deep, with populated racks weighing in the region of 470 to 900 kg.
• Clearance. 1219 mm at the front for cold air intake and 914 mm at the rear for exhaust. This is clearance, not aisle width, and it is measured from the rack face.
• Raised floor. Minimum 46 cm depth, with floor to ceiling height of at least 3.2 m, and permission to lift tiles for cabling and service.
• Cooling. Perforated tiles rated 400 CFM or greater, with a full rack typically needing four of them, and front to back airflow with no rack exhausting into another rack's intake.
• Temperature and humidity. Operating range 5 to 32 degrees Celsius with an optimal band of 21 to 23 degrees, and relative humidity optimally 45 to 50 percent, non condensing.
• Power. Two PDUs per rack, options in the 15, 22 and 24 kVA range depending on region and phase, one dedicated breaker per power cord, receptacles within 2 m of the rack, feeds from two separate grids, and a UPS.

None of that is exotic for a purpose built data hall. All of it is a problem in a converted server room, a leased suite where you do not control the tiles, or a facility already running near its cooling ceiling.

The access route is where projects actually slip

The rack has to get from the loading dock to the tile, intact. Oracle's documentation specifies the route, and the route is what your building either has or does not.

• Doorways. Minimum 2184 mm height and 1270 mm width with the shipping pallet, or 2040 mm by 640 mm once unpacked.
• Elevators. Minimum internal depth of 1625 mm with pallet, 1240 mm without, plus a rated dynamic load for the rack in transit.
• Ramps. Maximum incline of 6 degrees, and an access route free of raised pattern flooring that would catch castors.
• Delivery. A tail lift or side lift on the carrier, plus dollies, pallet jacks, steel plates or floor covers as the route demands.
• Staging. An air conditioned, protected unpacking area, to avoid thermal shock and particle contamination before the rack reaches the floor.
• Facility basics. Emergency power shutoff, a fire protection system, antistatic flooring, and somewhere to keep spare parts.

Badges, background checks and the camera rule

Oracle field engineers have to get into your data hall, sometimes at short notice, for the life of the contract. The checklist asks you to declare your access rules up front, and those rules become an operational constraint on Oracle's ability to serve you.

• Clearances. You state what background checks or security clearances Oracle personnel need, and how many days notice you require.
• Devices. You state whether laptops, phones and cameras are permitted on the floor. In defense and government sites this is routinely no, which changes how remote hands work.
• Escorts. If every visit needs an escort, your own staffing model becomes part of Oracle's maintenance service level.
• Labor rules. You declare whether union labor is required for delivery or installation, which affects both cost and scheduling.

Write these constraints into the contract as customer obligations with agreed notice periods. Otherwise a delayed repair caused by your own badge process becomes an argument about Oracle's service credits.

What are you actually committing to, and for how long?

A multi year consumption commitment, with the initial hardware footprint sized on the consumption you forecast for your first year. Oracle's own FAQ describes a five year consumption based commitment and says the starting footprint is based on the customer's forecasted first year consumption.

Read that twice. The forecast is not just a planning artifact. It sets how much iron arrives, and the iron sets the floor you pay.

What Oracle has published about the commitment, and when

The public numbers have moved, and knowing the history is leverage. Oracle has restated the entry point twice, which tells you the floor is a commercial choice rather than a physical constant.

• 8 July 2020. Oracle's launch blog for Dedicated Region Cloud at Customer stated a 500,000 dollar per month consumption based commitment over three years, sold purely on consumption.
• 21 June 2022. Oracle's press release stated a redesigned region needing 60 to 75 percent less space and power, at around 1 million dollars a year for a typical customer.
• Current. The FAQ describes a five year consumption based commitment. The term got longer while the annual number got smaller, which is a different deal, not a cheaper one.

Total contract value is the number to compare, not the annual figure. A smaller annual floor across a longer term can commit you to more money than the original three year deal did.

Why the year one forecast is the whole negotiation

Because it is used twice, and only one of those uses is discussed. It sizes the equipment Oracle ships, and it anchors the floor you are asked to sign.

1. Your architects produce a forecast to justify the business case, so it is optimistic by construction.
2. Oracle sizes the initial footprint from that forecast, because it has to order hardware against something.
3. The floor is then set at a level that makes the footprint economic for Oracle.
4. The migration slips, as migrations do, and you pay the floor anyway for the remaining years.

The fix is unglamorous. Build a deliberately conservative year one forecast, and negotiate a ramped floor with named workloads and dates attached to each step up.

The consumption forecast you write to get the project approved is the same document Oracle uses to size your floor. Write it as if you will be held to it, because you will be.

Which licensing posture do you land in on day one?

The same two options as public OCI: license included rates, or bring your own license against programs you already own with active support. Nothing about the region being in your building changes the choice.

What it does change is timing. The posture has to be settled before the footprint is sized, because a BYOL estate and a license included estate consume credits at very different rates for the same workload.

Settle BYOL before the site survey, not after

If you intend to bring owned Database licenses, count them before the forecast is written. A large owned estate lowers your credit burn, which lowers the defensible floor, which lowers the footprint Oracle needs to ship.

• Count what you own. Processor and Named User Plus entitlements with current support, verified against your ordering documents rather than a support renewal quote.
• Check the conversion rules. Oracle's cloud licensing terms sit in a policy document, which Oracle can revise. Snapshot the version you relied on and date it.
• Avoid double counting. A license applied to the region cannot simultaneously cover a server on your own floor.
• Keep the support line visible. BYOL lowers the cloud rate but you still pay support on the underlying licenses, so the saving is smaller than the rate card implies.

The full money mechanics, including what the fee covers and what is billed separately, sit on our DRCC pricing and licensing page. If you are still choosing between a region and a database platform, start with the Cloud at Customer comparison.

When does a Dedicated Region fit, and when does it not pay?

It fits when a rule, not a preference, forbids the data from leaving your control, and when you would consume the floor regardless. Everything else is a public region conversation.

The three drivers that survive scrutiny

Only three reasons hold up under a hard read, and cost is not one of them.

• Sovereignty. A law, a license condition or a supervisory expectation requires the data and the control plane to remain in a jurisdiction, or under your physical control, and no commercial region satisfies it.
• Latency. A production process, a trading system or an industrial control loop needs single digit millisecond access to cloud services, and the nearest commercial region cannot deliver it.
• Regulation of the operator. Your regulator restricts who may physically access the media, or requires exit and audit rights that a shared region cannot give you.

Test each one against a written source. A supervisory expectation you can cite is a driver. A risk committee's discomfort is a preference wearing a driver's clothes.

Six situations where a Dedicated Region does not pay

These are the cases where we have advised buyers to walk away, or to buy something smaller.

• The workload is one database estate. You are buying 200 services to run one. A database platform is the cheaper answer.
• The residency rule is satisfied by a commercial region. If Oracle already operates a region in country and your rule says in country, the case evaporates.
• Your migration is unfunded past year one. A floor that outruns a stalled migration is the most common way this deal goes wrong.
• You do not control the facility. In a leased suite you may not be able to guarantee tile depth, floor loading or a second power feed for five years.
• The estate is shrinking. If you are consolidating or divesting, a five year floor is the wrong shape for a shrinking demand curve.
• Nobody owns day two. If no named team has capacity for escorted access, capacity planning and power reporting, the region will be operationally orphaned.

Where the common advice on Oracle Dedicated Region is wrong

The standard advice is to size a Dedicated Region for your three year target state so you have room to grow into it. We disagree. Across the Dedicated Region engagements we supported, sizing to the future state meant paying a large annual floor for capacity the migration had not filled, and the commitment ran a median 35 percent ahead of real consumption in the early years. Oracle can add racks later, and its own material advertises expansion to more than 450 racks. Buy for the workloads you have funded and dated. Growing into a region is a project. Paying for one you have not filled is a subscription to your own optimism.

35%

Median floor above real year one use

10 to 15

Dedicated Region engagements 2024 to 2025

5 yr

Typical committed term we negotiate against

Source: Redress Compliance advisory engagement file, 2024 to 2025.

Who runs it after go live, and who gets the call at 3am?

Oracle runs everything inside the racks. You run the room, and the room is on your uptime, not Oracle's. Oracle's FAQ puts data center uptime, physical facility compliance, and holding temperature and humidity within agreed levels squarely on the customer.

That is a reasonable split, but it has a sharp edge. If your chiller fails, the region degrades, and the availability objective was never a promise about your plant.

The responsibility split that surprises people

Three obligations move to you that would sit with Oracle in a commercial region.

• Facility availability. Power and cooling continuity for the Oracle racks is your obligation, for the length of the term.
• Environmental compliance. You have to keep the hall inside the agreed envelope continuously, not on average.
• Access provisioning. Oracle needs timely physical access for maintenance, and your process governs how fast that happens.

Oracle retains hardware maintenance, troubleshooting, patching, feature rollout, and secure media handling and destruction in its own controlled area. Ask to see that process documented before you sign, particularly if your regulator will want it.

What an outage looks like when the region is in your building

Different from a public region outage in one important way: you are now a participant in the incident, not just a customer of it.

1. Detection is joint. Your building management system may see the cause before Oracle's telemetry sees the symptom.
2. Escalation crosses two organizations, and the boundary is physical rather than logical.
3. Remediation may require a person on your floor, at your notice period, with your badge process.
4. Root cause is often about the room, and the room is your evidence to produce.

Rehearse it. Run a tabletop with facilities, the Oracle account team and your incident commander before the region carries production, and write the notice periods you commit to into the agreement.

What should a buyer do next?

1. Write down the residency, latency or regulatory rule in one sentence, with the source you would show a regulator. If you cannot, stop here.
2. Bring facilities in before heads of terms. Test the candidate room against clearance, raised floor depth, floor loading, tile CFM and dual power feeds.
3. Check that a commercial OCI region in the same jurisdiction does not already satisfy the rule, and record the answer.
4. Build a deliberately conservative year one consumption forecast, separate from the business case forecast.
5. Count your owned Oracle licenses and decide the BYOL position before the footprint is sized.
6. Negotiate a ramped floor, with each step tied to named workloads and dates rather than calendar years.
7. Compare total contract value across the whole term, not the annual floor, against the same workloads in a commercial region.
8. Get exit, hardware refresh, service catalog parity and access notice periods written into the contract before signature.
9. Rehearse a joint outage with facilities and Oracle before production lands.

Related reading on this decision

• Cloud at Customer against a Dedicated Region. Which problem each platform actually solves.
• DRCC pricing and licensing. Commitment mechanics, drawdown and what is included.
• Oracle cloud negotiations. The ramp, benchmark and exit levers.
• Oracle practice. Independent buyer side advisory, no reselling.

Frequently asked questions

What is an Oracle Cloud Dedicated Region?

It is a complete, self contained OCI region that Oracle installs, owns and operates inside your own data center. Oracle's product page describes an expandable footprint starting as small as three racks and scaling beyond 450, carrying more than 200 OCI services behind your perimeter.

How many racks does a Dedicated Region need?

Three, at the published entry point. Oracle announced the Dedicated Region25 configuration in September 2024 starting at only three racks with a 75 percent smaller launch footprint, and the same product page states the ceiling is more than 450 racks as demand grows.

What does the customer have to provide?

Floor space, racks, data center power and cooling, and data center personnel, in Oracle's own words. In practice that means clearance of 1219 mm at the front and 914 mm at the rear, a raised floor at least 46 cm deep, perforated tiles rated 400 CFM or greater, dual power feeds and a UPS.

How long is the Dedicated Region commitment?

Oracle's FAQ describes a five year consumption based commitment. At launch in July 2020 the published shape was 500,000 dollars per month over three years, and in June 2022 Oracle stated around 1 million dollars a year for a typical customer. Compare total contract value, not the annual figure.

Is a Dedicated Region cheaper than public OCI?

No, and it is not sold as such. Oracle states the pricing is the same as its commercial public cloud regions, so you pay comparable rates and add a committed floor plus the internal cost of hosting. Choose it for sovereignty, latency or regulation, never for unit cost.

Does a Dedicated Region connect to Oracle's public cloud?

Not by default. Oracle's FAQ states the region is managed through its own console and is not connected to the commercial public cloud regions. Private connectivity is achieved through FastConnect, which means circuits and carrier lead times you procure and pay for yourself.

Who is responsible if the data center loses cooling?

You are. Oracle places data center uptime, physical facility compliance and maintaining temperature and humidity within agreed levels on the customer. Oracle retains hardware maintenance, patching and secure media handling. Rehearse a joint incident before production workloads land.

How long does deployment take?

Oracle's FAQ says a region can be available within months of the data center being ready, and its Dedicated Region25 announcement claims deployment within weeks. The variable is almost never Oracle. It is how long your facility, network circuits and access approvals take to reach ready.