Oracle Cloud at Customer Licensing Guide:
Implementation, BYOL vs Licence Included & Cost Optimisation
Oracle Cloud at Customer (C@C) promises public cloud services in your data centre — but the licensing model, sizing methodology, and cost dynamics are significantly more complex than Oracle’s marketing suggests. This guide provides a complete analysis of BYOL vs Licence Included economics, sizing pitfalls, implementation considerations, and cost optimisation strategies.
Executive Summary
Oracle Cloud at Customer (C@C) — previously known as Oracle Cloud Machine — places Oracle Cloud Infrastructure (OCI) hardware and software inside your data centre, operated by Oracle but consumed as a cloud service. It targets organisations with data sovereignty, latency, or regulatory requirements that prevent public cloud adoption. The commercial model, however, is where most organisations encounter surprises.
Key Findings
What Is Oracle Cloud at Customer
Oracle Cloud at Customer delivers OCI services — including Exadata Cloud Service, Autonomous Database, and OCI compute — on dedicated hardware installed in the customer’s data centre or a colocation facility. Oracle owns, manages, and maintains the hardware; the customer consumes cloud services on a subscription basis.
How it works. Oracle ships a pre-configured infrastructure rack (typically Exadata or OCI Compute) to your data centre. Oracle connects the rack to its cloud control plane via a secure network link, enabling Oracle to manage firmware, patching, scaling, and monitoring remotely. You consume OCI services — compute, storage, database — through the standard OCI console and APIs, identical to public OCI.
Why organisations choose C@C. The primary drivers are data sovereignty (data must remain in a specific jurisdiction or facility), ultra-low latency (workloads that cannot tolerate public cloud network latency), regulatory requirements (financial services, healthcare, government), and air-gapped environments (defence, intelligence). For organisations without these requirements, public OCI is typically more cost-effective.
| Dimension | Public OCI | Cloud at Customer | On-Premises |
|---|---|---|---|
| Location | Oracle’s data centres | Your data centre, Oracle-managed | Your data centre, self-managed |
| Management | Fully Oracle-managed | Fully Oracle-managed | Self-managed or SI-managed |
| Licensing | BYOL or Licence Included | BYOL or Licence Included | Traditional on-premises licences |
| Minimum Commitment | Pay-as-you-go available | Full rack minimum (typically) | Licence + support minimums |
| Data Sovereignty | Limited to available regions | Full control — your facility | Full control |
| Scaling | Elastic, on-demand | Within provisioned capacity | Manual, hardware-dependent |
| Exit Complexity | Moderate | High | N/A (already on-prem) |
Oracle’s sales teams position C@C as “the same as public OCI, just in your data centre.” This is technically accurate from a service perspective but misleading from a commercial perspective. The minimum commitment structure, sizing methodology, and exit dynamics are fundamentally different from public OCI’s pay-as-you-go model.
BYOL vs Licence Included: The Real Economics
The choice between Bring Your Own Licence (BYOL) and Licence Included (LI) is the single most consequential commercial decision in a C@C deployment. Oracle presents both options, but the economics are heavily situation-dependent.
| Dimension | BYOL | Licence Included |
|---|---|---|
| How It Works | You apply existing on-premises Oracle licences to the C@C environment. You pay only for infrastructure (compute, storage) on C@C. | Oracle bundles the software licence into the C@C subscription. You pay a single per-OCPU rate that includes both infrastructure and licence. |
| Per-OCPU Cost | Infrastructure only — lower per-OCPU rate | Infrastructure + licence — 2–3x higher per-OCPU rate |
| Existing Licence Requirement | Yes — you must own qualifying on-premises licences with active support | No — no existing licence required |
| Support on Existing Licences | Must maintain Oracle support on the licences applied to BYOL | Not applicable — support is included in subscription |
| Licence Conversion Ratio | 1 Processor licence = 2 OCPUs (Database); varies by product | N/A |
| Best For | Organisations with existing, underutilised Oracle licences and active support | Organisations without existing licences or looking to avoid capital licence expenditure |
| Exit Implications | Licences revert to on-premises use if C@C is terminated | No licence entitlement remains after subscription ends |
Oracle’s BYOL model requires that existing licences maintain active support throughout the C@C subscription term. If you planned to reduce Oracle support costs by moving to C@C, BYOL does not achieve this — you pay the C@C infrastructure subscription plus ongoing support on the underlying licences. The net cost is C@C subscription + continued support, not C@C subscription instead of support.
BYOL vs Licence Included — Redress Cost Analysis Data
deliver projected savings
vs BYOL per OCPU
via independent validation
commitment (mid-market)
Sizing & Architecture Pitfalls
C@C sizing determines your minimum commitment for the contract term. Over-sizing at the proposal stage is the most common and most expensive mistake in C@C deployments.
The Full-Rack Minimum
C@C typically requires a minimum commitment of one full rack (e.g., Exadata X9M quarter rack or equivalent). If your workload only requires a fraction of the rack, you pay for the full minimum regardless. Oracle’s sizing guidance rarely recommends below the minimum — because there is no commercial incentive to do so.
Peak vs Average Sizing
Oracle sizes C@C for peak workload capacity, not average utilisation. An organisation that peaks at 80 OCPUs for two hours daily but averages 25 OCPUs will be sized for 80+ OCPUs. On public OCI, you would pay for actual consumption. On C@C, you pay for provisioned capacity.
The DR Capacity Double-Count
If you deploy disaster recovery on C@C, Oracle sizes (and charges for) a second rack or partition at the DR site. The DR capacity sits idle 99%+ of the time but is billed at the same rate as production capacity. Negotiate reduced DR pricing — it is available but rarely offered proactively.
Storage Over-Provisioning
Oracle’s storage sizing for C@C typically includes generous growth buffers (50–100% over current usage). While storage is relatively inexpensive per unit, the cumulative cost of over-provisioned storage across a multi-year term adds up. Right-size storage to actual growth projections, not Oracle’s defaults.
The Autonomous Database Premium
Running Autonomous Database on C@C carries a premium over standard Database Cloud Service. If your workloads do not require Autonomous’s self-tuning and self-patching capabilities, standard Database Cloud Service on C@C may deliver the same outcome at 30–40% lower cost.
Network & Connectivity Costs
C@C requires a dedicated network link to Oracle’s cloud control plane. The cost of this connectivity — including redundant links for resilience — is often excluded from Oracle’s initial C@C proposals but adds $15–50K annually depending on bandwidth and redundancy requirements.
Cost Modelling: C@C vs Alternatives
A complete C@C cost model must account for infrastructure subscription, BYOL support obligations, sizing assumptions, connectivity, data centre hosting, and exit costs. Compare against public OCI, on-premises refresh, and multi-cloud alternatives.
| Cost Component | C@C (BYOL) | C@C (Licence Included) | Public OCI | On-Premises Refresh |
|---|---|---|---|---|
| Compute & Storage | C@C subscription (infrastructure only) | C@C subscription (infra + licence) | Pay-as-you-go or committed | Hardware CapEx + maintenance |
| Software Licences | Existing licences (already owned) | Included in subscription | BYOL or LI | Existing or new procurement |
| Oracle Support | 22% of licence value (ongoing) | Included | Included (LI) or ongoing (BYOL) | 22% of licence value |
| Data Centre Costs | Power, cooling, space for rack(s) | Power, cooling, space for rack(s) | None | Full data centre costs |
| Connectivity | Dedicated link to Oracle ($15–50K/yr) | Dedicated link to Oracle ($15–50K/yr) | Internet / FastConnect | N/A |
| Exit Costs | Data migration; licences revert | Data migration + licence procurement | Data migration | N/A |
If you deploy workloads on C@C using Licence Included pricing and later decide to move those workloads to on-premises or another cloud, you will need to procure Oracle licences for those workloads from scratch — at current list price. The Licence Included subscription does not generate any perpetual licence entitlement. This exit cost can represent 40–60% of the original C@C contract value and is rarely modelled at the proposal stage.
Implementation Pitfalls
C@C implementations involve physical infrastructure installation, network provisioning, application migration, and operational handover. These are the most common pitfalls encountered in Redress-advised deployments.
Data Centre Readiness Delays
C@C racks require specific power, cooling, weight-bearing, and physical security specifications. Many data centres require modifications to accommodate Oracle’s hardware. Lead time for data centre preparation is frequently underestimated by 4–8 weeks.
Network Link Provisioning
The dedicated network connection to Oracle’s control plane must be provisioned, tested, and security-approved before C@C can operate. Telecom provisioning alone can take 6–12 weeks. This dependency is often on the critical path but poorly managed in project plans.
Application Migration Complexity
Moving on-premises Oracle workloads to C@C is not a lift-and-shift. Database versions, character sets, storage layouts, and network configurations may differ. Migration testing and cutover planning require the same rigour as any cloud migration.
Billing Start Date vs Go-Live Date
Oracle typically begins C@C billing when the rack is installed and connected — not when your workloads are migrated. If migration takes 3–6 months after rack installation, you pay for infrastructure you are not yet using. Negotiate billing start date alignment with workload go-live.
Shared Responsibility Gaps
Oracle manages the infrastructure; you manage the applications, data, and user access. The boundary between Oracle’s and your responsibilities is defined in Oracle’s Shared Responsibility Model — but grey areas around security patching timelines, backup management, and incident escalation frequently cause operational friction.
Operational Team Readiness
Your IT operations team must learn OCI tools, consoles, and processes to manage C@C workloads effectively. Without OCI-specific training, teams default to on-premises operational practices that undermine the cloud operating model and create efficiency losses.
Contract Protections
Eight contractual protections to negotiate into every Oracle Cloud at Customer agreement.
1. Billing Start Date Alignment
Negotiate billing commencement tied to workload go-live, not rack installation. Oracle’s standard terms begin billing at installation. The gap can represent 3–6 months of wasted subscription fees during migration.
2. Annual Right-Sizing
Negotiate the right to scale down C@C capacity at annual anniversaries. Oracle’s standard terms commit you to the initial sizing for the full term. If your workloads decrease or migrate, you should be able to reduce capacity and cost accordingly.
3. Price Escalation Cap
Lock in maximum annual price increases at 0–3%. Oracle’s standard C@C pricing can escalate at renewal. Without caps, your Year 4+ costs may significantly exceed initial projections.
4. DR Pricing Discount
Negotiate reduced pricing for disaster recovery capacity that sits idle. DR partitions should not be priced at the same rate as production. Target 50–70% discount on DR capacity or pay-per-activation pricing.
5. BYOL Licence Portability
Confirm in writing that BYOL licences revert to on-premises use immediately upon C@C termination. Oracle’s standard terms are clear on this, but ensure there are no supplemental terms that restrict portability.
6. Exit Assistance & Data Migration
Negotiate Oracle’s obligation to assist with data export and workload migration at term end. Include defined timelines, data formats, and Oracle’s commitment to maintain service during the transition period.
7. SLA with Financial Remedies
C@C SLAs should match public OCI SLAs. Negotiate automatic service credits for downtime, not Oracle’s standard credit-request process. Include the right to terminate without penalty for chronic SLA failures.
8. Hardware Refresh Guarantee
C@C hardware has a finite lifespan. Negotiate Oracle’s obligation to refresh hardware during multi-year terms without cost impact to you. Without this protection, Oracle may charge for hardware refresh as a scope change.
Recommendations
Seven priority actions for organisations evaluating or negotiating Oracle Cloud at Customer.
Validate the Business Case for C@C vs Public OCI
C@C is only cost-justified when data sovereignty, latency, or regulatory requirements genuinely preclude public OCI. If those requirements can be met by OCI’s expanding regional footprint, public OCI will be more cost-effective and operationally simpler.
Model BYOL vs Licence Included with Full Cost Transparency
Do not accept Oracle’s BYOL savings projections at face value. Model both options with actual licence portfolio data, support costs, conversion ratios, and the exit cost implications of Licence Included. The cheaper option depends entirely on your specific circumstances.
Commission Independent Sizing Validation
Oracle’s sizing recommendations are commercial proposals, not engineering assessments. Engage an independent party to validate workload requirements, peak vs average utilisation, growth projections, and DR sizing. Independent validation typically identifies 20–35% sizing reductions.
Negotiate All Eight Contract Protections
The protections in Section 07 are not optional. Billing start date alignment, right-sizing rights, DR discounts, and exit assistance can collectively save 15–25% of total contract value. Oracle will push back — that pushback tells you which protections matter most.
Plan Data Centre Readiness Early
Data centre preparation is the most commonly underestimated dependency in C@C projects. Assess power, cooling, physical space, weight capacity, and security requirements at least 12 weeks before planned rack delivery.
Model Exit Costs from Day One
Include exit costs in your initial TCO analysis. If you are on Licence Included, model the cost of procuring Oracle licences at term end. If you are on BYOL, confirm licence reversion terms. Your 5-year TCO must include Year 6.
Engage Independent Advisory
C@C combines Oracle licensing complexity with cloud infrastructure commercial dynamics. Most organisations encounter C@C once. Independent advisory brings comparative benchmarking, sizing validation, and contract negotiation expertise that materially improves outcomes.
How Redress Compliance Can Help
Redress Compliance has advised on 30+ Oracle Cloud at Customer evaluations and negotiations. Our Oracle Practice provides independent, vendor-agnostic advisory on C@C sizing, BYOL analysis, cost modelling, and contract negotiation.
Cloud at Customer Advisory Services
- BYOL vs Licence Included cost analysis
- Independent sizing validation
- 5-year TCO modelling (C@C vs alternatives)
- Licence portfolio assessment for BYOL eligibility
- Contract negotiation & protection
- Exit cost modelling & planning
- Implementation oversight & readiness assessment
- Oracle proposal review & challenge
Get In Touch
Evaluating Cloud at Customer?
Contact us for a confidential sizing review and BYOL/LI cost comparison — before you sign Oracle’s proposal.
Book a Meeting
Evaluating or negotiating Cloud at Customer? Request a confidential call with our Oracle Practice team.
Request a Meeting
Fill in your details and suggest times. We’ll confirm within 24 hours.
Meeting Request Sent
Thank you. Our Oracle Practice team will confirm within 24 hours.
What to Expect
30-minute NDA-protected call. We’ll review your workloads, Oracle licence portfolio, and C@C requirements.
We’ll assess your BYOL eligibility, model both options against your actual licence portfolio, and identify the optimal path.
You’ll leave with a preliminary cost comparison, sizing observations, and recommended next steps — no obligation.
100% Independent. We have no commercial relationship with Oracle Cloud. Our advisory is vendor-agnostic and in your interest.
No Obligation. If C@C is right for you, we’ll help you negotiate. If public OCI or on-premises is better, we’ll tell you that directly.
This document has been prepared by Redress Compliance for informational purposes. Redress Compliance is a fully independent software licensing advisory firm with zero vendor affiliations — including zero Oracle partnership. Benchmark data is based on 30+ anonymised Oracle Cloud at Customer advisory engagements. Past results are not a guarantee of future outcomes.
© 2026 Redress Compliance. All rights reserved.