Oracle Cloud at Customer Assessment: A Structured Framework for Evaluating OCC Before You Commit
Oracle Cloud at Customer is a multi-year commitment that starts at $8,000 per month and is almost impossible to unwind once signed. This paper provides the assessment framework enterprises should complete before engaging Oracle commercially — covering workload suitability, five-year TCO, BYOL eligibility, contract red flags, and competitive alternatives.
Executive Summary
Oracle Cloud at Customer (OCC) — marketed primarily as Exadata Cloud@Customer — occupies a specific and genuinely useful niche in enterprise infrastructure: Oracle-managed hardware, billed as a cloud subscription, deployed inside your own data centre. For the right workloads, in the right commercial circumstances, it can represent a legitimate step forward from traditional on-premises Oracle infrastructure.
The challenge is that OCC is one of Oracle's most commercially aggressive products. The contract structure, hardware refresh obligations, minimum term commitments, and BYOL decision point create a framework in which poorly prepared buyers routinely commit to costs that are 40–60% higher than necessary and structures that prevent meaningful exit for four or more years.
This paper provides the assessment methodology that Redress Compliance applies before any client engages Oracle on OCC terms. It is structured as a sequential assessment: workload suitability first, then financial modelling, then BYOL eligibility, then contract review, then competitive context. Completing the full assessment typically takes four to six weeks. The commercial implications of skipping it can persist for the entire contract term.
Across 45+ Oracle Cloud at Customer and Exadata Cloud@Customer engagements, Redress Compliance has found that 60% of organisations would have been better served by an alternative infrastructure approach — including OCI public cloud, AWS Outposts, or Azure Arc — had they completed a structured pre-engagement assessment before signing.
The assessment framework in this paper is designed to be completed independently, before Oracle's account team is involved in shaping the commercial framing. The earlier you establish your own analysis, the stronger your negotiating position.
What is Oracle Cloud at Customer?
Oracle Cloud at Customer is a family of Oracle-managed infrastructure products deployed within your own physical data centre. The core products under the OCC umbrella are Exadata Cloud@Customer (database infrastructure), Roving Edge Infrastructure (edge computing for distributed deployments), and Oracle Dedicated Region Cloud@Customer (a full OCI region deployed on-premises for large-scale deployments).
In practical terms, the proposition is straightforward: Oracle ships hardware to your data centre, manages it, and charges you a subscription fee. You retain data sovereignty and can meet latency or regulatory requirements that make public OCI unsuitable, while accessing Oracle's cloud management tooling and OCPU-based licensing model.
The Commercial Model
Exadata Cloud@Customer, which represents the majority of OCC deployments, uses a two-component cost structure. First, an infrastructure subscription covers the hardware itself — starting at approximately $8,000 per month for a Base System (the smallest available configuration, an Exadata X10M Quarter Rack) and scaling to approximately $43,200 per month for a Full Rack configuration. These are infrastructure costs alone, before any Oracle Database or application licensing is factored in.
Second, compute costs cover the OCPU-hours actually consumed running Oracle Database and other workloads on the infrastructure. These are charged either at Licence-Included rates (Oracle bundles the software licence into the OCPU price) or at BYOL rates (you supply existing on-premises Oracle Database licences and pay only for infrastructure compute). The BYOL rate is approximately 75–80% lower than the Licence-Included rate at list prices — a difference that, across a full rack over four years, can easily exceed $5 million.
What OCC Is Not
Understanding what OCC does not provide is as important as understanding what it does. OCC does not eliminate Oracle support costs for existing on-premises licences — unless you actively decommission that infrastructure, Oracle support charges continue. OCC does not provide a cost reduction path for organisations without existing Oracle Database licences; for new deployments without BYOL eligibility, public OCI is almost always cheaper. And OCC does not provide the same flexibility as public cloud — adding and removing capacity is constrained by the hardware configuration you subscribe to.
The OCC Decision Framework
The fundamental question your assessment must answer is whether OCC genuinely solves a problem that no better or cheaper alternative can address. Oracle's account teams are skilled at framing OCC as the natural evolution for organisations with significant on-premises Oracle Database investments. This framing is commercially motivated — OCC generates significantly more long-term revenue than a straightforward OCI migration or a true-up followed by an on-premises refresh.
The decision framework consists of four sequential gates. Failing any gate before the fourth means OCC is not the right answer for your current situation, and the assessment should redirect to alternative approaches.
| Gate | Question | Proceed if… | Redirect if… |
|---|---|---|---|
| Gate 1 | Is public OCI available? | Data residency, latency, or regulation requires on-premises | Public OCI meets your requirements — evaluate OCI first |
| Gate 2 | Are workloads Oracle-specific? | Oracle Database, Exadata-optimised workloads dominate | Workloads are non-Oracle or cloud-agnostic — evaluate AWS/Azure |
| Gate 3 | Are you BYOL eligible? | Sufficient on-premises Oracle Database licences with active support | No BYOL eligibility — licence-included rates make OCI or alternatives cheaper |
| Gate 4 | Is the TCO competitive? | Five-year OCC TCO is less than or equal to the best alternative | Alternatives deliver lower five-year TCO — negotiate harder or redirect |
Many organisations engage Oracle's OCC proposal process before completing Gate 1 and Gate 2. Once Oracle's account team has invested time building an OCC proposal and internal stakeholders have been briefed on it, the political cost of redirecting to a different approach increases significantly. Complete the gates independently first.
Workload Assessment Criteria
Not every Oracle workload belongs on OCC. The assessment should categorise your Oracle Database estate into three buckets: strong fit, marginal fit, and poor fit for Cloud@Customer. This classification drives both the sizing decision (which configuration to subscribe to) and the overall business case.
Strong Fit Workloads
The clearest OCC candidates are large, steady-state Oracle Database workloads where one or more of the following conditions apply. Data sovereignty requirements — typically in financial services, healthcare, defence, or government — make public cloud deployment legally or regulatorily impossible. Latency is a genuine, documented constraint, such as real-time trading systems, high-frequency manufacturing MES integration, or real-time analytics against operational data. The organisation has a substantial existing Oracle Database Enterprise Edition licence estate under active support that can be leveraged under BYOL, making the OCPU cost at BYOL rates genuinely competitive. And the workload scale justifies the base subscription — a meaningful step above the minimum $8,000 per month threshold is required to make the economics work on a per-OCPU basis.
Marginal Fit Workloads
Oracle Database workloads that are growing but currently undersized for the minimum OCC configuration sit in marginal territory. Development and test environments almost never justify OCC infrastructure costs — Oracle's Developer Cloud Free Tier or standard OCI compute is typically 80–90% cheaper for non-production workloads. ERP and application tier databases that are Oracle-backed but not particularly performance-sensitive benefit less from Exadata-specific optimisation than OLTP or analytics workloads do.
Poor Fit Workloads
- New Oracle Database deployments without BYOL eligibility — at licence-included rates, public OCI or competitive alternatives are almost always cheaper
- Workloads scheduled for re-platforming — committing to a four-year OCC contract for workloads planned for migration to a different platform within that period destroys value
- Highly variable or bursty workloads — OCC's fixed infrastructure subscription is incompatible with the elasticity advantages that make public cloud economically compelling for workloads that cycle significantly
- Non-Oracle database workloads — organisations seeking general-purpose cloud infrastructure at the edge have better alternatives through AWS Outposts, Azure Arc, and Google Distributed Cloud
Five-Year TCO Assessment Framework
A credible TCO model must capture all cost components over a minimum five-year period, including costs that Oracle does not proactively include in its proposal. The following framework identifies all material cost categories and the common modelling errors that inflate estimates in Oracle's favour.
Infrastructure Subscription Costs
Model the monthly infrastructure fee for your required configuration, escalated by Oracle's contractual right to increase fees at hardware refresh. Standard contracts allow Oracle to reprice at the point of mandatory hardware replacement, which typically occurs three to four years into the initial term. For a Quarter Rack starting at $8,000 per month, a 15–25% reprice at Year 4 adds $14,400–$24,000 to the five-year total.
Compute Costs (BYOL vs Licence-Included)
At list prices, the BYOL OCPU rate on Exadata Cloud@Customer is approximately $0.1613 per OCPU-hour with a committed annual Universal Credit, compared to approximately $0.672 per OCPU-hour for licence-included. At 1,000 OCPU-hours per month, this represents an annual difference of $6,120 at committed rates — or $30,600 over five years per 1,000 OCPU-hours. Scaling this to typical enterprise workloads makes BYOL eligibility the single largest financial variable in the OCC assessment.
| Configuration | Infrastructure/Month | 5yr Infrastructure | BYOL Compute Est. | Licence-Included Est. |
|---|---|---|---|---|
| Quarter Rack X10M | ~$8,000 | ~$504,000 | ~$220,000 | ~$880,000 |
| Half Rack X10M | ~$17,600 | ~$1,109,000 | ~$440,000 | ~$1,760,000 |
| Full Rack X10M | ~$43,200 | ~$2,722,000 | ~$1,100,000 | ~$4,400,000 |
Figures are indicative estimates based on published Oracle list pricing. Actual costs depend on OCPU consumption, committed discount tier, and negotiated rates. All figures in USD.
Ongoing Oracle Support Costs
Unless you decommission on-premises Oracle Database infrastructure when migrating workloads to OCC, Oracle support costs (typically 22% of net licence fees per year) continue in full. Model these explicitly. A $2 million Oracle Database Enterprise Edition licence estate carries approximately $440,000 per year in support fees regardless of whether those workloads move to OCC.
Oracle's OCC proposals frequently show a "total cost of Oracle" view that nets out on-premises support costs as though they disappear on OCC migration. They do not disappear unless licences are decommissioned. A correct model shows both OCC subscription costs and any continuing on-premises support obligations running in parallel during the transition period.
BYOL Eligibility Assessment
BYOL eligibility on Exadata Cloud@Customer requires Oracle Database licences that meet specific criteria. The assessment should confirm eligibility before any commercial discussions proceed, because the commercial outcome of OCC with and without BYOL eligibility can differ by several million dollars over a contract term.
Eligibility Requirements
To use existing Oracle Database licences under BYOL on OCC, your licences must be Oracle Database Enterprise Edition (Standard Edition 2 is not eligible for BYOL on Exadata). They must have active Oracle Software Update Licence and Support (SULS) — lapsed support disqualifies licences. They must be processor-based or Named User Plus licences meeting Oracle's conversion factors for OCPU mapping. And they must be owned by the legal entity subscribing to OCC — licences belonging to subsidiaries or affiliates require explicit Oracle approval to use under BYOL.
The BYOL Audit Risk
Oracle reserves the right to audit BYOL consumption on OCC. The audit mechanism differs from traditional on-premises audits (which use Oracle LMS) — on OCC, Oracle's management layer has direct visibility into OCPU usage. Organisations that undercount BYOL-eligible licences or consume more OCPUs than their licence estate supports face retroactive licence shortfall charges, which Oracle can assess at full Licence-Included rates for the period of non-compliance.
The BYOL Eligibility Checklist
- Confirm all Oracle Database licences earmarked for BYOL are Enterprise Edition
- Verify active SULS coverage on each licence (check Oracle Support portal)
- Map processor-based licences to OCPU conversion factors (1 processor licence = 2 OCPUs for Intel/AMD; verify the current conversion table with Oracle)
- Confirm licences are held by the subscribing legal entity
- Model maximum OCPU consumption at peak load against BYOL-eligible licence count
- Add a 15–20% headroom buffer above modelled peak consumption
- Document the BYOL licence mapping in your contract schedule
Contract Assessment: Six Red Flags
Oracle's standard Exadata Cloud@Customer agreement contains several provisions that are either non-standard by cloud infrastructure norms or commercially disadvantageous in ways that are not immediately apparent. The following six red flags should be reviewed by your legal and commercial teams before signature.
Oracle requires hardware replacement every three to four years and reserves the right to reprice the infrastructure subscription at each refresh. Unlike a typical cloud subscription where pricing is locked for the committed term, OCC pricing can increase at refresh. Negotiate a cap on infrastructure fee increases at hardware refresh — typically 10–15% above the initial subscription rate is an achievable position with leverage.
Standard OCC contracts do not include early termination provisions at commercially reasonable rates. Exit before end of term typically requires payment of all remaining subscription fees in full. For a $43,200/month Full Rack contract with 36 months remaining, that represents a $1.56 million exit cost. Negotiate an early termination fee schedule — graduating from 80% of remaining fees at the start of the term to 20% in the final year — as an alternative to no-exit provisions.
The contract specifies the data centre location for OCC hardware. Moving infrastructure to a different facility — even within the same organisation — requires Oracle's prior written consent and may require a contract amendment. Confirm that the specified location is stable for the full contract term before signing.
OCC SLAs are typically structured to provide service credits rather than cash compensation for downtime. Credit caps (often 10–15% of the monthly subscription fee) significantly limit Oracle's financial exposure for sustained outages. Negotiate an escalating credit structure for outages exceeding 24 and 72 hours, and confirm that credits are applied to the following invoice rather than requiring a formal claim process.
The contract should specify Oracle's obligations to assist with data export at the end of the subscription term, including the period during which data remains accessible after termination. Standard terms vary — negotiate a minimum 60-day post-termination data access window with Oracle's active assistance for export.
Oracle reserves the right to modify the support model for OCC hardware during the subscription term as part of its normal cloud service management. Negotiate explicit language requiring Oracle to maintain support response times and feature parity with the specification at contract execution throughout the initial term.
Competitive Assessment: OCC vs Alternatives
Your OCC assessment is incomplete without a documented competitive comparison. Oracle's account teams use two tactics to minimise competitive pressure: framing OCC as uniquely capable of running Oracle Database at enterprise performance levels, and controlling the timeline so that competitive evaluation seems logistically impractical. Both tactics are commercially motivated and should be resisted.
AWS Outposts
AWS Outposts delivers AWS-managed infrastructure to your data centre with native AWS services, including RDS for Oracle Database via BYOL. For organisations with Oracle Database workloads that do not require Exadata-specific optimisation (Smart Scan, HCC compression, Database In-Memory offload), AWS Outposts often delivers a lower total cost with significantly greater flexibility — including genuine pay-per-use scaling, a broader set of AWS-native services, and multi-year pricing that is negotiable with a competitive context established. The primary limitation is that Outposts does not provide the Exadata-specific performance enhancements that make OCC genuinely superior for very large, I/O-intensive Oracle Database workloads.
Azure Arc and Azure Hybrid Benefit
For organisations with significant Microsoft enterprise agreements, Azure Arc with Azure Hybrid Benefit for Oracle Database workloads provides a compelling alternative. Azure Arc enables Azure management tooling across on-premises infrastructure, and Oracle Database on Azure via BYOL is supported. This approach is particularly relevant for organisations that are already consolidating toward Microsoft cloud services and can leverage existing EA commercial relationships to negotiate competitive Oracle Database infrastructure pricing.
On-Premises Exadata Refresh
A frequently overlooked alternative is simply refreshing on-premises Exadata infrastructure on Oracle's standard Engineered Systems purchasing model. For organisations with established Oracle relationships, a negotiated Exadata refresh with multi-year support pricing can provide comparable performance to OCC with lower long-term costs and no subscription lock-in. The trade-off is capital expenditure and the operational burden of managing infrastructure — but for organisations with mature Oracle DBA teams, this cost is already incurred.
| Alternative | Best For | Key Limitation | Relative Cost vs OCC (BYOL) |
|---|---|---|---|
| AWS Outposts | Mixed workloads, AWS-native services | No Exadata performance optimisation | 10–25% lower for non-Exadata workloads |
| Azure Arc + Hybrid Benefit | Microsoft EA holders, mixed cloud | Limited Oracle-specific tooling | 15–30% lower with strong EA leverage |
| OCI Public Cloud (BYOL) | No data residency requirements | Data must leave your data centre | 20–35% lower at equivalent scale |
| On-Prem Exadata Refresh | Exadata-dependent workloads, capex | Capital cost, operational overhead | Comparable or better (5yr view) |
Negotiation Readiness Assessment
If your assessment concludes that OCC is the right commercial decision, the quality of your negotiation preparation directly determines the commercial outcome. Oracle's account teams operate within a system that rewards urgency, and standard OCC proposals are structured to compress the evaluation timeline. The following readiness assessment identifies whether you are prepared to negotiate effectively.
Readiness Factors
Competitive alternatives documented: You have a written quote or estimate from at least one credible alternative (AWS Outposts, Azure Arc, or on-premises refresh). Oracle's willingness to negotiate infrastructure subscription pricing increases meaningfully when a credible alternative is on the table — typical first-offer discounts of 10–15% on infrastructure fees can increase to 20–30% with documented competitive pressure.
BYOL position confirmed: Your BYOL-eligible licence count and OCPU headroom calculation are documented and have been independently verified. Do not rely on Oracle's BYOL calculator without independent verification — Oracle's tool sometimes overestimates OCPU consumption to create an apparent licence shortfall that drives licence purchases.
Internal approval secured for alternatives: Your evaluation of AWS Outposts, Azure Arc, or on-premises refresh has been completed to a level where those alternatives are genuine options in your decision process. Oracle's account teams are experienced at identifying when a "competitive" process is nominal rather than genuine, and price accordingly.
Legal review initiated: The contract red flags identified in Section 07 have been reviewed by legal counsel before the commercial term sheet is presented. Attempting to renegotiate contract terms after agreeing commercial pricing is significantly harder.
Multi-year commitment model completed: You have a five-year TCO model that includes hardware refresh repricing risk, ongoing support costs, and an exit cost scenario. This model should be reviewed internally before any commercial terms are accepted.
Pre-Signature Checklist
The following checklist summarises the assessment gates that should be completed before signing any Oracle Cloud at Customer agreement. Each item represents a documented finding — not an assumption — from your internal assessment process.
- Gate 1 confirmed: public OCI is not available due to a documented data residency, latency, or regulatory requirement
- Gate 2 confirmed: primary workloads are Oracle Database Enterprise Edition and benefit from Exadata-specific performance capabilities
- Gate 3 confirmed: BYOL eligibility is established, licence count and OCPU headroom independently verified
- Gate 4 confirmed: five-year TCO at negotiated (not list) OCC pricing is lower than or equal to the best-documented alternative
- Competitive alternative documented: at least one credible written estimate from AWS Outposts, Azure Arc, or on-premises Exadata refresh
- Infrastructure sizing validated: configuration matches modelled OCPU consumption plus 20–25% headroom; not over-sized to Oracle's standard configuration options
- Contract red flags reviewed: mandatory hardware refresh repricing, no-exit provisions, and SLA credit caps assessed by legal counsel
- Hardware refresh reprice cap negotiated: contractual limit on infrastructure fee increase at hardware replacement
- Early termination fee schedule negotiated: graduating exit cost provision rather than full remaining fees
- Post-termination data access window confirmed: minimum 60-day post-expiry data export period with Oracle assistance
- Ongoing support cost model completed: on-premises Oracle support fee continuation (for licences not decommissioned) modelled in full
- Development and test workloads excluded: non-production Oracle workloads confirmed to be on standard OCI rather than OCC infrastructure
About Redress Compliance
Redress Compliance is an independent, 100% buyer-side enterprise software licensing advisory firm. We have no commercial relationships with Oracle Corporation or any other software vendor. Our only client is the enterprise buyer.
Our Oracle advisory practice has completed 350+ Oracle engagements across EMEA and North America, covering Oracle Database licensing, ULA structuring, cloud migration assessment, Exadata Cloud@Customer negotiations, and Oracle LMS audit defence. We are recognised by Gartner as a specialist provider in the enterprise software advisory category.
For Oracle Cloud at Customer specifically, we engage at three points: pre-assessment (before Oracle's account team shapes the commercial framing), negotiation support (competitive modelling, contract red flag review, and commercial term negotiation), and post-signature optimisation (BYOL compliance review, OCPU consumption governance, and renewal preparation).
Oracle Licensing Knowledge Hub · Exadata Cloud@Customer Complete Guide · All White Papers