Oracle Cloud at Customer promises public cloud services in your data centre — but the licensing model, sizing methodology, and cost dynamics are more complex than Oracle suggests. This guide covers BYOL vs Licence Included economics, sizing pitfalls, implementation considerations, and cost optimisation strategies for C@C deployments.
BYOL vs Licence Included analysis, 6 sizing pitfalls, 6 implementation traps, full cost modelling framework, and 8 essential contract protections for Cloud at Customer.
This is not a product brochure. It’s an independent licensing and cost guide that gives IT, infrastructure, and procurement leaders the BYOL analysis, sizing validation, and contract protections needed to negotiate Cloud at Customer on your terms — not Oracle’s.
Side-by-side comparison across 7 dimensions: per-OCPU cost, licence requirements, support obligations, conversion ratios, exit implications, and which model wins for your specific scenario.
Full-rack minimums, peak vs average sizing, DR double-counting, storage over-provisioning, Autonomous Database premiums, and hidden network costs. Each pitfall with mitigation strategy.
C@C (BYOL) vs C@C (LI) vs Public OCI vs On-Premises Refresh. Every cost component mapped: compute, licences, support, data centre, connectivity, and exit costs. 5-year TCO methodology.
Data centre readiness delays, network provisioning, migration complexity, billing start date gaps, shared responsibility friction, and operational team readiness. Based on real C@C deployments.
Billing alignment, annual right-sizing, price caps, DR discounts, BYOL portability, exit assistance, SLA remedies, and hardware refresh guarantees. Every protection with must-have terms.
100% independent. No Oracle Cloud partnership. Based on 30+ C@C evaluations. We have no incentive to recommend C@C over alternatives. Every recommendation in your commercial interest.
In 42% of BYOL proposals reviewed by Redress, the projected savings did not materialise once support obligations, conversion ratios, and sizing were accurately modelled. Independent validation of Oracle’s C@C proposal typically identifies 20–35% cost reduction opportunities.
REDRESS COMPLIANCE — ORACLE PRACTICE