When the workload cannot leave the data center, Cloud at Customer is the destination Oracle quietly prefers. The licensing arithmetic, the BYOL economics, and the four scenarios where Cloud at Customer is the right answer.
Oracle Cloud at Customer is the on premises rack delivered, owned, and operated by Oracle that runs the same OCI control plane as Oracle's public cloud regions. It is the only commercial framework where Oracle accepts BYOL into a fully managed cloud while keeping the underlying hardware on the customer's data center floor. For most enterprises Cloud at Customer is one of three or four cloud destinations on the menu, alongside OCI public regions, AWS RDS for Oracle, and Azure for Oracle.
The publisher's commercial discipline positions Cloud at Customer as the natural destination for regulated workloads, ULA exits, and Exadata refresh cycles. The buyer side discipline tests that position against the actual workload economics, the existing license base, and the renewal calendar. Cloud at Customer is the right answer in roughly thirty percent of the engagements where Oracle proposes it. The other seventy percent close at a different destination, usually because the support arithmetic, the BYOL conversion, or the latency assumption does not survive the buyer side review.
Cloud at Customer is delivered as one of three rack profiles. The base rack runs Exadata Cloud at Customer, sized at quarter, half, or full rack with eight to ninety two compute cores and a matched storage tier. The second rack profile is OCI Compute Cloud at Customer, which runs the broader OCI compute portfolio against the same control plane. The third profile is Dedicated Region, which delivers a full OCI region inside a customer data center at the largest scale tier.
The hardware is owned and operated by Oracle. The data center floor space, power, and network are provided by the customer. The control plane is the same OCI control plane that runs in Oracle's public regions. From the workload perspective, Cloud at Customer is OCI. From the licensing perspective, it is a hybrid commercial framework that interacts with the underlying entitlement base in non obvious ways.
Cloud at Customer is sold as a subscription, billed monthly or annually, with a minimum term that ranges between three and five years. The subscription includes the hardware, the OCI control plane, the patching, and the support. The subscription does not include the database licenses. Database licenses are either entitled under an existing contract, drawn from a Universal Cloud Credit pool, or charged at a metered cloud rate per OCPU hour.
The commercial choice is the BYOL versus PAYG decision, applied to each workload. Most large enterprises arrive at Cloud at Customer with an existing entitlement base that funds at least a portion of the workload at zero incremental license cost. The remainder is funded by Universal Cloud Credit or metered cloud rates. The right blend depends on the existing license base, the renewal calendar, and the projected workload growth across the contract term.
Bring Your Own License on Cloud at Customer applies the same processor metric mapping as on premise Oracle Database. Two OCPU equals one Oracle processor license. A workload running on Cloud at Customer at sixteen OCPU consumes eight processor licenses from the entitlement base. The licenses must remain in a supported state, with the support cap honored, for the duration of the deployment.
The arithmetic interacts with three other commercial frameworks. First, the Oracle support cap limits the rate at which support can be reduced when licenses are repurposed onto Cloud at Customer. Second, the cloud option packs (RAC, Multitenant, Active Data Guard) follow the license onto Cloud at Customer, which can change the deployment economics versus a pure cloud subscription. Third, the Exadata Cloud at Customer rack carries Exadata software entitlements that the on premise Exadata estate does not carry, which can shift the negotiation when an Exadata refresh is on the table. For the broader Exadata mechanics, see our Exadata licensing strategy.
Cloud at Customer support is bundled into the subscription line and runs at a comparable rate to the twenty two percent on premise support cap. There are three differences that change the renewal calculus. First, support is metered, not flat. The cost varies with the OCPU consumption rather than the license inventory. Second, patching is managed by Oracle. The customer does not run the patching cycle. Third, third party support is not available. The Rimini Street and Spinnaker exit option is closed for the duration of the Cloud at Customer subscription.
For most enterprises the closure of the third party support exit option is the single most material commercial consequence of the Cloud at Customer decision. The third party support savings line, which runs at fifty percent of the support cost, is unavailable for the duration of the Cloud at Customer subscription. The decision is reversible at the end of the subscription term, but the reversal carries its own arithmetic. For the third party support framework, see our third party support guide.
Cloud at Customer is one of the four ULA exit destinations Oracle accepts at certification. The publisher's commercial preference is to position OCI public cloud as the natural ULA exit destination. The buyer side discipline tests that position against the actual workload requirements. Cloud at Customer is the right ULA exit destination when the workload cannot leave the data center, the certification arithmetic is large, and the post certification renewal calendar is long.
The certification arithmetic counts deployed processors at the certification date. Cloud at Customer deployments are eligible if the deployment is in flight and Oracle inventory rules are met. The mechanics need careful drafting. For the full certification framework, see our ULA certification advisory and the ULA decision framework.
Cloud at Customer is the right destination in four scenarios. Data residency. The workload cannot leave the data center because of regulatory, contractual, or sovereign cloud requirements. Latency. The workload is too latency sensitive for public cloud, typically transactional databases that integrate with on premise systems at sub millisecond response times. ULA exit destination. The certification arithmetic is large and the in flight deployment qualifies under Oracle's inventory rules. Regulated private cloud. The customer needs a private cloud framework that Oracle, not the customer, manages, typically driven by compliance, audit, or staffing constraints.
Outside those four scenarios the commercial economics rarely support Cloud at Customer over the alternatives. For the migration mechanics where Cloud at Customer is the destination, see our ten step migration guide.
The buyer side discipline tests Cloud at Customer against three alternatives in every engagement. OCI public regions for workloads that are not constrained by data residency or latency. AWS RDS for Oracle and Azure for Oracle for the workload subset that integrates with the broader hyperscaler estate. On premise Oracle Database for the workload subset that benefits from the third party support exit option and does not need the OCI control plane.
The right answer is rarely a single destination. The right answer is a portfolio mix that balances the data residency requirements, the workload economics, the existing license base, and the renewal calendar. For the full Oracle commercial discipline, see our Oracle CIO Playbook and the Oracle services overview.
Most Cloud at Customer engagements run in one of three shapes. Project work tied to a single Cloud at Customer subscription, ULA exit, or Exadata refresh, typically eight to sixteen weeks in duration. Subscription cover under Vendor Shield, where any Oracle commercial event is handled by our team within forty eight hours and the Cloud at Customer destination is reviewed annually. Embedded retainer where a partner sits inside your software asset management or procurement function for the duration of a major program.
For onboarding, see our contact page. For market intelligence between engagements, subscribe to the monthly newsletter.
The four ULA exit options, the certification arithmetic in plain language, and the worked example from a Fortune 500 retailer that certified out at seventy two million dollars of compliance value. Cloud at Customer is one of the four exit destinations covered.
Sixty four pages. PDF. Used in more than seventy live ULA engagements since 2018.
Oracle proposed Cloud at Customer as the natural ULA exit. We tested the position. The right answer was a hybrid mix of Cloud at Customer and AWS RDS, not the single destination Oracle preferred.
No. Cloud at Customer can run under BYOL using existing Oracle entitlements, under PAYG cloud subscriptions, or under a hybrid model. The right answer depends on the existing license base, the workload profile, and the renewal calendar.
Yes, in most cases. The certification arithmetic counts deployed processors at the certification date. Cloud at Customer deployments are eligible if the deployment is in flight and Oracle inventory rules are met. The mechanics need careful drafting and our ULA decision framework walks through the four certification options.
Cloud at Customer support is bundled into the subscription line and runs at a comparable rate to the twenty two percent on premise support cap, with three differences. Support is metered, not flat. Patching is managed by Oracle. And third party support is not available.
Four scenarios. Data residency requires the workload to stay on premises. The workload is too latency sensitive for public cloud. The ULA exit needs an inventory destination. Or the regulated workload demands a private cloud framework that Oracle, not the customer, manages.
The subscription can be renewed at the same scale, expanded, reduced, or exited. The exit returns the workload either to on premise Oracle, to a different cloud destination, or to a different platform entirely. The reversal carries its own arithmetic and is best planned at least twelve months before the contract expiration date.
Tell us where Oracle has positioned Cloud at Customer in your roadmap. We will run the four scenario test, the BYOL arithmetic, and the alternatives analysis. Thirty minute scoping call. No obligation.
ULA precedents, Cloud at Customer commercial movements, EA discount benchmarks, and third party support market signals.
