The opening section deconstructs the Oracle Cloud@Customer commercial model. We document the Exadata Cloud@Customer platform, the Compute Cloud@Customer offering, the Oracle Dedicated Region for full OCI region deployments, the hardware footprint commitment, the OCI consumption commitment, the Universal Credits program economics, and the BYOL versus License Included decision. The section closes with a Cloud@Customer cost model template that lets the buyer pressure test the Oracle proposal against the existing Exadata or on premises Database baseline.
The second section addresses BYOL versus License Included economics. The decision to bring the existing Oracle Database entitlement into Cloud@Customer under BYOL or to consume the platform under License Included is the most consequential single commercial choice inside the proposal, and the buyer side approach documents the conversion rate, the multi year envelope comparison, the contractual exit positions on the BYOL entitlement, and the negotiated language we have used inside live Cloud@Customer agreements. This is the same BYOL discipline we apply across the wider Oracle advisory practice.
The third section covers Universal Credits sizing. The OCI consumption commitment that runs alongside the Cloud@Customer hardware footprint is priced on the Universal Credits program, and the buyer side approach documents the credit sizing procedure, the breakage assumption, the credit substitution rights across OCI services, and the contract clauses that protect the customer against an over commitment on credits the deployment cannot use. The framework pairs with the Oracle Cost Optimization Playbook.
The fourth section addresses Exadata Cloud@Customer specifically. The Exadata Cloud@Customer platform bundles RAC, Active Data Guard, Partitioning, Advanced Compression, and Multitenant inside the platform, but the customer should not assume the bundling produces a discount against the on premises Exadata entitlement. The buyer side approach documents the platform licensing posture, the OCPU model, the Autonomous Database on Cloud@Customer integration, and the contract grandfather positions.
The fifth section covers support transfer and the customer experience. The transition from Oracle Premier Support to the Cloud@Customer support framework introduces complexity around the customer experience, the support level definitions, and the regional support footprint. The buyer side approach documents the support transfer mechanics, the support level mapping, and the contract clauses that preserve the customer support posture through the transition.
The closing section documents the Oracle Cloud@Customer renewal contract clauses Redress Compliance routinely negotiates: the BYOL preservation clause, the Universal Credits ceiling, the hardware footprint substitution rights, the Exadata bundle grandfather, the support transfer language, the data residency posture, the audit cooperation framework, and the executive escalation path. Each clause is paired with negotiated language we have already placed inside live Oracle Cloud@Customer contracts.
