Cloud at Customer puts Oracle managed cloud hardware inside your own data center. It solves a data residency problem and creates a commercial one. The subscription, not the rack, is where the cost lives.
Oracle Cloud at Customer delivers Oracle's public cloud services on hardware Oracle installs and runs inside your data center, which moves the licensing question from ownership to subscription terms.
Cloud at Customer is Oracle's public cloud delivered on Oracle owned hardware installed in your data center. Oracle manages the rack remotely, and you consume the same services you would in Oracle's regions. The offering is described at Oracle Cloud at Customer.
The point is location. Regulated data stays inside your walls and under your jurisdiction, while Oracle still operates the platform. You get cloud operations without the data leaving the building.
You subscribe to the cloud services, you do not buy perpetual licenses for them. Bring your own license can apply where you already own Oracle entitlement, with counting rules from the Oracle licensing policy for authorized cloud environments. The rest is consumption against committed capacity.
Ownership and cost model
| Element | Who owns it | How you pay |
|---|---|---|
| Hardware | Oracle | Inside the subscription |
| Platform operations | Oracle | Inside the subscription |
| Database services | Subscription or BYOL | Committed capacity or BYOL rate |
| Data and workloads | You | Your responsibility |
If you hold clean Oracle Database entitlement, bring your own license can lower the rate on Cloud at Customer. The Oracle Database Licensing Information governs what those licenses permit, so confirm the position before relying on the discount.
The traps are commercial, not technical. Committed capacity, term length, and undefined exit terms are where buyers lose flexibility they assumed they had.
Committed capacity bills on the installed footprint, not on usage. Idle capacity is paid in full every month, which is why sizing to real demand beats sizing to peak projections.
At the largest scale, Dedicated Region Cloud at Customer delivers an entire cloud region on premises, which deepens both the value and the lock in. The bigger the commitment, the more the exit terms matter.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
You negotiate the subscription the way you would any committed cloud deal. The Oracle Master Agreement frames it, but the capacity, term, and exit clauses are where you create room.
These three levers decide whether Cloud at Customer is a flexible hybrid platform or a fixed cost you carry for years. Fix them before the rack arrives.
The common advice is to size Cloud at Customer for growth, because the hardware is installed once and headroom avoids a disruptive expansion later. We disagree. In the hybrid deals Fredrik Filipsson advised, capacity sized to peak projections left 25 to 45 percent of the committed footprint idle, and buyers paid for it every month of a multi year term. The buyer side move is to size to realistic demand, negotiate a capacity step down, and define exit terms before installation. Headroom you pay for continuously is more expensive than a planned expansion you negotiate once, and the installed rack should never become a reason to overcommit.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The rack is installed once. The subscription is paid every month. Negotiate the subscription.
Oracle Cloud at Customer is Oracle's public cloud delivered on Oracle owned hardware installed in your data center. Oracle manages the platform remotely while your data stays on your premises.
You buy a subscription to the cloud services rather than perpetual licenses. Bring your own license can apply where you already hold clean Oracle entitlement, which lowers the rate.
The main driver is data residency. Regulated organizations keep data inside their own facility and jurisdiction while still consuming Oracle cloud services and operations.
Yes. Cloud at Customer is committed capacity, so you pay for the installed footprint whether or not workloads use it. That is why right sizing and a step down clause matter.
Dedicated Region delivers an entire Oracle cloud region on your premises rather than a smaller footprint. It deepens both the capability and the commercial lock in, so exit terms become more important.
Yes, through bring your own license, subject to Oracle's cloud counting rules. The saving only holds if the underlying on premises entitlement is clean and compliant.
That depends on the exit, egress, and decommissioning terms you negotiate. Leaving them to Oracle's standard template weakens your position, so define them before the hardware is installed.
The services are similar, but the hardware sits in your data center rather than an Oracle region. That gives you data residency and local latency at the cost of committed on premises capacity.
Oracle ULA exit moves, Java audit defense posture, certification framework, and the buyer side moves across the Oracle Database, Java, and EBS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
Headroom you pay for every month is more expensive than an expansion you negotiate once.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
Short, buyer side notes on Oracle hybrid cloud, contracts, and renewals. No vendor spin.
