Oracle Cloud at Customer puts OCI hardware inside your data center and bills it like cloud. The licensing model is metered, not perpetual, and it carries audit exposure most buyers miss.
Oracle Cloud at Customer delivers OCI inside your data center on Oracle owned hardware, metered by OCPU. This guide covers the billing model, the BYOL versus License Included choice, the audit exposure, and the moves that cut the renewal.
Oracle Cloud at Customer places OCI infrastructure on Oracle owned hardware inside your data center, and bills it as a cloud service. You do not buy the rack. You consume capacity and Oracle meters it.
The commercial model is Oracle Universal Credits. You commit to a spend over a term, then draw it down by the hour as workloads run. This is the same model as public OCI, brought on premises.
The billing unit is the OCPU, an Oracle compute measure that maps to one physical core with hyperthreading. Database services bill per OCPU per hour, with a separate rate for storage and networking.
The choice between BYOL and License Included is the single largest cost lever on the platform. It depends on what you already own and how long you intend to run the workload.
BYOL wins when you hold unused or partially used Database licenses with active support. License Included wins when you have no owned entitlement and want a single clean meter. Oracle publishes the conversion rules in its cloud licensing policy, and the OCPU conversion ratio is where most buyer assumptions break.
BYOL versus License Included on Cloud at Customer
| Dimension | BYOL | License Included |
|---|---|---|
| Up front entitlement | Owned license required | None required |
| Hourly OCPU rate | Lower, infrastructure only | Higher, license bundled |
| Support cost | Existing support continues | Folded into the meter |
| Best fit | License rich estates | Net new workloads |
Audit risk does not disappear when you move to a metered platform. It moves. The two exposures are BYOL eligibility and the connected on premises estate.
Soft partitioning that Oracle disallows on premises is treated differently in cloud, but the moment BYOL licenses span both your owned servers and the platform, the partitioning policy and your contract terms collide. Auditors test whether the same license is counted twice.
The standard Oracle account team pitch is that Cloud at Customer removes licensing complexity because everything becomes a meter. We disagree. In the deals we reviewed, the meter added a second compliance surface on top of the licenses buyers still held, and the BYOL conversion math hid real exposure rather than removing it. The buyer side move is to treat Cloud at Customer as a licensing event, not just an infrastructure refresh. Baseline the owned estate, map every BYOL license to a single home, and lock the OCPU commitment to measured demand before signing. That is not how the platform is usually sold.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
A metered platform inside your own data center is still a contract you can negotiate. The OCPU commitment is the number that matters, not the rack.
White Paper ยท Oracle
The Oracle Buyer Side Framework
The moves we use across Oracle Database, Java and ULA estates. Read it free.
Four moves recur in every Cloud at Customer deal we have advised. They target the commitment, not the unit rate.
The committed drawdown pool and term set the floor on your spend. Push for a shorter initial term and a ramp that matches the migration schedule, not a flat commitment from day one.
Build a contractual off ramp and benchmark the OCPU rate against public OCI list pricing in the Cloud at Customer service description. A meter you cannot leave is a meter Oracle prices freely.
It is metered, not licensed perpetually. You consume OCPU capacity through Oracle Universal Credits, committing to a drawdown over a term. The hardware stays Oracle owned inside your data center.
An OCPU is Oracle's compute billing unit, equal to one physical core with hyperthreading enabled. Database services bill per OCPU per hour, with separate rates for storage and networking.
Yes. Bring Your Own License lets you carry an owned Oracle Database license onto the platform and pay a reduced infrastructure only OCPU rate. The owned license must stay on active support to remain eligible.
The on premises partitioning policy does not govern cloud metering, but BYOL licenses that span owned servers and the platform must still satisfy your contract terms. Auditors test for the same license counted in two places.
Audit risk moves from raw deployment counting to BYOL eligibility and the connected on premises estate. The common findings are double counted licenses, lapsed support, and edition mismatches between owned and consumed options.
The Universal Credit commitment and term, not the unit rate. Oracle typically sizes the initial OCPU commitment above steady state demand, so sizing to measured consumption is the largest saving.
It depends on utilization and what you already own. License rich estates running steady workloads often favor BYOL on the platform, while spiky or net new workloads can favor License Included or public OCI.
Only if you negotiated an exit. Without a contractual off ramp and a benchmark clause, renewal pricing sits entirely with Oracle. Build both before the first signature.
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.
Engage independent buyer side Oracle licensing experts. We do not resell. We do not implement. We sit on your side of the table.
See engagement scope, comparison vs Big4 and resellers, and the buyer side framework.
Visit page →Cloud at Customer is still a meter. The buyer side job is to know what the meter counts, who controls it, and what happens to your existing licenses when you move on top of it.
